Thanks for checking. Some of these resources and reference architecture will provide good background from a serverless standpoint
- This is a good re:Invent presentation : https://d1.awsstatic.com/events/reinvent/2019/REPEAT_1_Best_practices_for_building_multi-region,_active-active_serverless_applications_SVS337-R1.pdf
These are also some good references you can refer
Creating a Multi-Region Application with AWS Services
Security specific areas that can be referred
You have some options to implement what you are trying to.
If you want to implement the API in just one region but you have API consumers in other regions, you can use an Edge Optimized API Gateway end-point. That adds a Cloudfront distribution in front of the API Gateway, thereby ensuring that clients can get into the AWS network from the POP nearest to them, thereby reducing the latency of API calls. - https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-api-endpoint-types.html
If the Edge Optimized API Gateway does not work for you, you will need to look at implementing multi-region Regional API Gateway endpoints. You will then have to either shard your API consumers, so every region has to maintain data only for its own local consumers, or if that does not work for you, then you will have to replicate the data across all the regions. You also have to make sure that your Infrastructure as Code and CI/CD pipelines deploy your infrastructure and code in every region whenever changes are needed.
If you go with the sharding kind of approach, then every region can have its own regional end-point which is exposed to the consumers of that regional endpoint only.
If you don't want to shard consumers but want them to be able to connect to any of the regional end-points, then you can use one of two approaches - Cloudfront Origin Failover or Route53 routing policies
Cloudfront origin failover can work if you have two regions, a primary and a secondary. It however works only for GET, HEAD and OPTIONS and does not support POST or PUT requests etc. - https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/high_availability_origin_failover.html
With Route53 routing policies, you can choose Geolocation routing or Geoproximity routing or Latency routing policies - https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html
Multi Region strategy for API Gatewayasked 9 months ago
How to configure record set for a custom domain name for a multi region api gateway?asked 4 days ago
How to host an multi region api in aws?asked 10 days ago
my domain on aws api gateway is not available in my region (ap-south-1) ==> India but available in other regions(which i check through vpn) ? how to resolve this?asked a month ago
I am having an issue in API Gateway that says " No integration defined for method" when I attempt to deployasked 6 months ago
AWS SNS delivery to multi regionasked 9 months ago
Cannot create API Gateway v2 in multiple regions with Route 53 latency-based routingasked 25 days ago
Cognito: multi region supportasked 9 months ago
How do I get an API key to use Firebase Cloud Messaging in SNS now that the API has been deprecated?asked a month ago
How to associate an api key to an API Gateway websockets APIasked 3 years ago