Direct connect Notes

Direct connect Notes

Creation of Dx connection

  You need Location details 
  Port speed
  
Creation of VIF:

  You dont need to create VPCs before, or no dependancy with this. You can manage with creating DxGW and later point in time you can create VGW and associate with DxGW
  ASN - This is going to be customer ASN
      - AWS side ASN will be available when you download router configuration
      - ASN can be private or public
      - From document - A public or private Border Gateway Protocol (BGP) Autonomous System Number (ASN) for your side of the BGP session. If you are using a public ASN, you must own it. If you are using a private ASN, it must be in the 64512 to 65535 range. Autonomous System (AS) prepending does not work if you use a private ASN for a public virtual interface.
  Public IPs (Peer IPs)
    - You can use your own Public IPs for your peer IP (customer peer IP) and Amazon side peer IP
    - If you are using your own IPs, you must own them
    - supports /31 oe /30 Ips
    - For example x.x.x.50/31 is your IPs, then you should assign
        - x.x.x.50/31 for your peer IP
        - x.x.x.51/31 for AWS peer IP
        - Even though you have only /31 i.e two IPs you still use /31 when assigning to each peer as they both should be on same network
        - it should not be /32 as it is signle ip each
     - If you dont own Public IPs for peers, You can raise support ticket (regular AWS support ticket) to get IPs.
     - AWS provides /31 IPs for each Dx connection
  Communities
     - You can use comminities tag to limit advertise of public prefixes that you advertise to Amazon (This is to be applied at customer level)
     - and AWS Direct Connect also applies BGP communities to its advertised routes (AWS will apply at their level, this is automatic way, no changs required)
     - Link https://docs.aws.amazon.com/directconnect/latest/UserGuide/routing-and-bgp.html
     
 Config from AWS:
 
     - Configuration required like Amazon side ASN, IPs, settings etc will be available when you download configuration from VIF
     
 LAG:
 
 I didnt consider creating LAG due to below reasons.
     - Already considered future demand for bandwidth by selecting 10 Gbps port
     - If you create with LAG with only one connection, No guarantee there will be more ports available on the same
chassis in the future if you wish to add more ports. If we do not have ports available in the same chassis you will need to order a new LAG and migrate your connections.
     - So created one connection without LAG for now, if require in future, we will create new conneciton with LAG first, complete the configuration of LAG at both AWS and customer end. then add old connection to LAG.
     - This way you will not have down time and no need to create multiple LAGs.