Questions and Answers
What is the purpose of an AWS Direct Connect gateway?
To connect on-premises networks to multiple VPCs across different AWS Regions
How many Transit Gateways can be associated with an AWS Direct Connect gateway?
Three
Can VPCs and Transit Gateways owned by any AWS account be associated with an AWS Direct Connect gateway owned by any AWS account?
Yes
How does traffic to and from the desired AWS Region travel when using an AWS Direct Connect gateway?
Signup and view all the answers
Are there any charges for using an AWS Direct Connect gateway?
Signup and view all the answers
Can private virtual interfaces and AWS Direct Connect gateways owned by different AWS accounts be associated with each other?
Signup and view all the answers
Which of the following networking features work with AWS Direct Connect gateway?
Signup and view all the answers
Can a virtual private gateway (VGW) associated with a VPC be part of more than one AWS Direct Connect gateway?
Signup and view all the answers
What is the maximum number of Transit Gateways that can be associated with an AWS Direct Connect gateway?
Signup and view all the answers
Can AWS Direct Connect gateway be used to connect VPCs owned by different AWS accounts?
Signup and view all the answers
Is there any charge for using an AWS Direct Connect gateway?
Signup and view all the answers
Can a VGW associated with a VPC be part of more than one AWS Direct Connect gateway?
Signup and view all the answers
Does AWS Direct Connect gateway support AWS VPN CloudHub functionality?
Signup and view all the answers
Can provisioned private virtual interfaces be associated with an AWS Direct Connect gateway?
Signup and view all the answers
Is intra-Region VPC connectivity still available when using AWS Direct Connect gateway?
Signup and view all the answers
Can a private virtual interface and a transit virtual interface be associated with different AWS accounts?
Signup and view all the answers
Study Notes
FAQs on AWS Direct Connect Gateway
- An AWS Direct Connect gateway is necessary for connecting on-premises networks to multiple VPCs across different AWS Regions.
- Up to three Transit Gateways can be associated with an AWS Direct Connect gateway, as long as the IP CIDR blocks don't overlap.
- VPCs and Transit Gateways owned by any AWS account can be associated with an AWS Direct Connect gateway owned by any AWS account.
- Traffic to and from the desired AWS Region takes the shortest path when using an AWS Direct Connect gateway, regardless of the associated home AWS Region.
- There are no charges for using an AWS Direct Connect gateway, but applicable egress data charges and port hour charges apply.
- Private virtual interfaces and AWS Direct Connect gateways, as well as transit virtual interfaces and AWS Direct Connect gateways, must be in the same AWS account.
- Networking features like Elastic File System, Elastic Load Balancing, and Security Groups work with AWS Direct Connect gateway, but AWS VPN CloudHub functionality is not supported.
- Provisioned private virtual interfaces can be associated with an AWS Direct Connect gateway if provisioned as private in the AWS account.
- Intra-Region VPC connectivity is still available, and egress rate is charged for related geographic Regions.
- Quotas for AWS Direct Connect gateway can be found on the AWS Direct Connect quotas page.
- A virtual private gateway (VGW) associated with a VPC cannot be part of more than one AWS Direct Connect gateway, and one private virtual interface can only attach to one AWS Direct Connect gateway or one Virtual Private Gateway.
- AWS Direct Connect gateway does not break existing AWS VPN CloudHub functionality, and supported and not supported traffic patterns can be found in the AWS Direct Connect User Guide.
FAQs on AWS Direct Connect Gateway
- An AWS Direct Connect gateway is necessary for connecting on-premises networks to multiple VPCs across different AWS Regions.
- Up to three Transit Gateways can be associated with an AWS Direct Connect gateway, as long as the IP CIDR blocks don't overlap.
- VPCs and Transit Gateways owned by any AWS account can be associated with an AWS Direct Connect gateway owned by any AWS account.
- Traffic to and from the desired AWS Region takes the shortest path when using an AWS Direct Connect gateway, regardless of the associated home AWS Region.
- There are no charges for using an AWS Direct Connect gateway, but applicable egress data charges and port hour charges apply.
- Private virtual interfaces and AWS Direct Connect gateways, as well as transit virtual interfaces and AWS Direct Connect gateways, must be in the same AWS account.
- Networking features like Elastic File System, Elastic Load Balancing, and Security Groups work with AWS Direct Connect gateway, but AWS VPN CloudHub functionality is not supported.
- Provisioned private virtual interfaces can be associated with an AWS Direct Connect gateway if provisioned as private in the AWS account.
- Intra-Region VPC connectivity is still available, and egress rate is charged for related geographic Regions.
- Quotas for AWS Direct Connect gateway can be found on the AWS Direct Connect quotas page.
- A virtual private gateway (VGW) associated with a VPC cannot be part of more than one AWS Direct Connect gateway, and one private virtual interface can only attach to one AWS Direct Connect gateway or one Virtual Private Gateway.
- AWS Direct Connect gateway does not break existing AWS VPN CloudHub functionality, and supported and not supported traffic patterns can be found in the AWS Direct Connect User Guide.
Studying That Suits You
Use AI to generate personalized quizzes and flashcards to suit your learning preferences.
