AWS Direct Connect | Using Public Virtual Interfaces Flashcards
Once the Direct Connect Gateway is created, can I change or modify the Amazon side ASN?
Using Public Virtual Interfaces
AWS Direct Connect | Networking & Content Delivery
No, you cannot modify the Amazon side ASN after creation. You can delete the Direct Connect Gateway and recreate a new Direct Connect Gateway with the desired private ASN.
When creating a virtual interface to work with AWS services using public IP space, what IP prefixes will I recieve via BGP?
Using Public Virtual Interfaces
AWS Direct Connect | Networking & Content Delivery
You will receive all Amazon IP prefixes for the region that you are connecting to in supported AWS Regions, and on-net prefixes from other AWS non-regional point of presence (PoP) as available such as CloudFront you can refer to this link for more information. This includes prefixes necessary to reach AWS services, and may include prefixes for other Amazon affiliates, including those of www.amazon.com. For the current list of prefixes advertised by AWS, please download the JSON of AWS IP Address Ranges.
When customers use AWS Direct Connect, customers’ traffic will remain in AWS global network backbone, after it enters AWS global network backbone. Therefore, prefixes of services such as Route53 or certain CloudFront locations that are not on the Amazon backbone network will not be advertised through Direct Connect.
For the newly created public VIF, Direct Connect customers will receive all Amazon public IP prefixes in supported AWS regions and on-net prefixes from other AWS non-region points of presence (POP) as available such as CloudFront. Standard AWS Direct Connect data transfer out rates apply for all traffic routed through your AWS Direct Connect connection. Please see the AWS Direct Connect community forum for the additional details in the routing policy of the public virtual interface.
What IP prefixes should I advertise over BGP for virtual interfaces to public AWS services?
Using Public Virtual Interfaces
AWS Direct Connect | Networking & Content Delivery
You should advertise appropriate public IP prefixes that you own over BGP. Traffic from AWS services destined for these prefixes will be routed over your AWS Direct Connect connection.
I am going to create a new public virtual interface; do I need to do anything special to get global Amazon public IP prefixes?
Using Public Virtual Interfaces
AWS Direct Connect | Networking & Content Delivery
No, you will receive Amazon’s global IP prefixes.
Will this new capability affect my existing public virtual interfaces?
Using Public Virtual Interfaces
AWS Direct Connect | Networking & Content Delivery
No, your existing public virtual interfaces will not get affected.
How many prefixes will you advertise over my newly created public virtual interface?
Using Public Virtual Interfaces
AWS Direct Connect | Networking & Content Delivery
You should receive approximately 2,000 prefixes, and it will continue to increase.
I do not want global public IP prefixes, can I opt out?
Using Public Virtual Interfaces
AWS Direct Connect | Networking & Content Delivery
Yes, you can opt out using scoping communities. Please refer to this link to learn more about scoping communities suported by AWS Direct Connect.
