Skip to content

Instantly share code, notes, and snippets.

@mbarneyjr

mbarneyjr/list.md

Last active November 18, 2022 18:16
Show Gist options
  • Save mbarneyjr/a4eb1a756121445a05b6fcca87c91e3d to your computer and use it in GitHub Desktop.
Save mbarneyjr/a4eb1a756121445a05b6fcca87c91e3d to your computer and use it in GitHub Desktop.
Download ZIP
List of AWS us-east-1 differences, edge cases, specialties, etc
Raw
list.md

What makes us-east-1 special?

Account:

  • Root user login is tied to us-east-1 (during a us-east-1 outage, root user logins were broken) link

CloudFront:

  • ACM certs must exist in us-east-1 for CloudFront to use them link
  • Lambda functions used for Lambda@Edge must be deployed in us-east-1 link
  • Control plane is only available in us-east-1 link

CloudTrial:

  • For most global services, events are logged as occurring in us-east-1 link

CloudWatch:

  • CloudWatch Billing metric data is stored in the US East (N. Virginia) Region and represents worldwide charges" link

IAM:

  • Control plane is only available in us-east-1 link

Route53

  • Control plane is only available in us-east-1 link
@dfulde-trek10
Copy link

CloudWatch: "Billing metric data is stored in the US East (N. Virginia) Region and represents worldwide charges." link

Not sure how this would be impacted by an outage. If CloudWatch Metrics were not available in us-east-1, then I assume billing metrics would be inaccessible.

@mbarneyjr
Copy link
Author

Nice find, added to the list

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment