1 Answer
- Newest
- Most votes
- Most comments
0
Unfortunately, this documentation does not yet allow the use of RDS.
So, as an alternative, how about starting an RDS at "ap-southeast-1" and going there to access it?
The "ap-southeast-1" region should be closer than other regions, so communication latency can be reduced somewhat.
https://aws.amazon.com/about-aws/global-infrastructure/localzones/features/?nc1=h_ls
The following document says that VPCs can be extended to local zones, so it may be possible to connect to ap-southeast-1 RDS from the local zone using this feature.
https://docs.aws.amazon.com/vpc/latest/userguide/Extend_VPCs.html
Relevant content
- asked 8 months ago
- asked 3 months ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 2 years ago
Thank you very much for the suggestion. Currently, my application is deployed in the "ap-southeast-1" region, and I want to minimize the latency as much as possible.
It is better to run RDS in the same region where the application is located. Also, consider CloudFront or other means if available to reduce application communication latency.