How should the solutions architect design a highly available solution that meets the requirements and is cost-effective?
Establish AWS Direct Connect connections from the company headquarters to all AWS Regions in use. Use the company WAN to send traffic over to the headquarters and then to the respective DX connection to access the data.
Establish two AWS Direct Connect connections from the company headquarters to an AWS Region. Use the company WAN to send traffic over a DX connection. Use inter-region VPC peering to access the data in other AWS Regions.
Establish two AWS Direct Connect connections from the company headquarters to an AWS Region. Use the company WAN to send traffic over a DX connection. Use an AWS transit VPC solution to access data in other AWS Regions.
Establish two AWS Direct Connect connections from the company headquarters to an AWS Region. Use the company WAN to send traffic over a DX connection. Use Direct Connect Gateway to access data in other AWS Regions.
Explanations:
While establishing Direct Connect connections to all AWS Regions may allow access to the data, routing traffic through the headquarters introduces latency and complexity. This option does not directly utilize the WAN for efficient cross-region access and could be less cost-effective due to multiple DX connections.
Using Direct Connect to a single AWS Region and relying on inter-region VPC peering can lead to increased costs and limited redundancy. This setup may not provide the desired high availability or direct access to data in multiple regions without additional complexity.
Although a transit VPC can facilitate inter-region traffic and may reduce complexity, it still relies on a single AWS Region for Direct Connect connections. This can create a single point of failure and does not fully utilize the capabilities of AWS Direct Connect for accessing data across multiple regions efficiently.
Establishing two Direct Connect connections to an AWS Region and utilizing a Direct Connect Gateway allows for direct access to multiple AWS Regions without routing through the headquarters. This design enhances redundancy, provides efficient data access, and complies with the security requirement of not traversing the public internet, making it a cost-effective and highly available solution.
If I had to guess, I’d say the answer is:
Establish two AWS Direct Connect connections from the company headquarters to an AWS Region. Use the company WAN to send traffic over a DX connection. Use Direct Connect Gateway to access data in other AWS Regions.