A data center transfers several terabytes to AWS every day over a stable, predictable bandwidth.
The workload must continue after a single circuit failure, and VPN over the public internet is not sufficient.
Which connectivity design is most appropriate?
Use multiple AWS Direct Connect connections on separated facilities or paths and size the links for the required bandwidth.
Detailed explanation
Direct Connect provides dedicated connectivity, and independent connections reduce the effect of a single circuit or facility failure.
Direct Connect provides dedicated connectivity, and independent connections reduce the effect of a single circuit or facility failure.
CloudFront distributes content to users and does not provide a dedicated on-premises circuit.
CloudFront distributes content to users and does not provide a dedicated on-premises circuit.
DNS distribution does not create physical connectivity or combine circuit capacity.
DNS distribution does not create physical connectivity or combine circuit capacity.
A single low-bandwidth path does not meet the continuous transfer and redundancy requirements.
A single low-bandwidth path does not meet the continuous transfer and redundancy requirements.
Check official documentation
Compare the following points with the official documentation.
AWS Direct Connect resilient connectivity and link aggregationの公式説明を確認する。
What to confirm
VPN、Direct Connect、DNS、CDNの役割と帯域・冗長性の違いを説明できる。
Key points
- AWS Direct Connect
- Dedicated connection
- Bandwidth redundancy
Notes
- Environment:
- Confirm current behavior in the official SAA-C03 guide and AWS service documentation.
Foundation review
Bandwidth planning
Consider peak volume and acceptable delay, not only daily averages.
Path separation
Putting connections on independent facilities reduces shared failure domains.