Hi, 
On behalf of a partner asking:
----
How do AWS SaaS ISVs/Solutions manage region sovereignty demand from customers? It seems like us-east-1 is a hard dependency.
Currently, we need to always create resources for cost reporting, and visibility in us-east-1 region of customer’s account because of following limitations-

1. CUR can only be created in us-east-1 region
2. Global resources like IAM Role only publish events from us-east-1 so we need to create CloudTrail/CloudWatch rule there only
3. For getting AWS Organizations related detail also, we need to use ‘us-east-1’ region
4. BillingConductor related resources also can be created/accessed from us-east-1

Because of this, we always need access to us-east-1 region of customer’s account even if they don’t have their infra hosted in that region which creates concerns regarding GDPR compliance also.

Could you please give your insight if this is going to be as is in near future or are we expecting any update on this

All Content tagged with Digital Sovereignty

How to overcome dependency on us-east-1 region to ensure com...