- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Question--1 -> Currently, we have AWS resources deployed in US-East-1 and US-West-2 regions on AWS . With this, does the above setup meet the SLA requirement from connectivity perspective ? (I know some other things like Enterprise Support and others but my focus on this question is on connectivity).
Answer:
In addition to what you have mentioned you also need to check the below point to meet the Multi-Site Redundant minimum SLA requirement, mentioned in the table here
Each Connection is on a unique AWS device, as indicated by the AWS Device ID visible in the AWS Direct Connect Console
You can check the AWS Device-ID like this, mentioned in the DX FAQ
Q: How do I check to see if my connections are terminated on different AWS devices?
After your connections are approved, you can validate the setup by going to “Connections”, selecting the desired connections, and looking at the “General configuration”, “AWS logical device”. Different device IDs indicate different AWS devices.
Question--2 -> if we add new region say EU-WEST-1 in future and access the EU-WEST-1 AWS resources through Direct connect Gateway from the same connectivity setup as above. Will i still cover under direct connect Multi-Site Redundant SLA ?
Answer: No, its not matching the below criteria, none of the PoPs are associated with EU-WEST-1 region
At least one of those Direct Connect locations is associated with the same AWS Region (described here) in which the Endpoint is hosted
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 2 Jahren- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
For Question-2 Answer, adding more clarification. i will be accessing EU-West-1 resources in addition to US-EAST-1 and US-WEST-2 resources. Still it does not cover in SLA ?
In the scenario you describe the SLA would be applicable for connectivity to endpoints in US-East-1 and US-West-2 regions not for connectivity to EU-West-1 regions.