- Newest
- Most votes
- Most comments
Unfortunately, it is not possible to directly assign an IP address from the ap-east-1 region to a Beanstalk environment or EC2 instance set up in ap-southeast-1. AWS resources, including Elastic Beanstalk environments and EC2 instances, are region-specific and can only use IP addresses from within their own region.
The configuration options you've seen in the network/VPC settings are limited to the region where your Beanstalk environment is deployed (ap-southeast-1 in this case), which is why you don't see options for other regions.
However, if your goal is to have end users establish connections only to the ap-east-1 region while your application runs in ap-southeast-1, you might consider alternative solutions:
-
Use Amazon Route 53 with latency-based routing or geolocation routing to direct users to the appropriate endpoint.
-
Implement a reverse proxy or load balancer in ap-east-1 that forwards requests to your Beanstalk environment in ap-southeast-1.
-
Consider using AWS Global Accelerator, which provides static IP addresses that serve as fixed entry points to your application endpoints in AWS Regions.
These solutions would allow you to present an entry point in ap-east-1 to your users while still running your Beanstalk application in ap-southeast-1. However, they would introduce additional complexity and potentially impact latency. The best approach depends on your specific requirements and constraints.
Sources
AWS Elastic Beanstalk announces VPC Public IP support
Configuring an Application Load Balancer - AWS Elastic Beanstalk
Thank your for the reply.
I would like to further know if there is support plans provided by AWS directly to add the proxy based on my current infrastructure?
Implement a reverse proxy or load balancer in ap-east-1 that forwards requests to your Beanstalk environment in ap-southeast-1. Where could I find them and quote directly?
Thank you.
Relevant content
- AWS OFFICIALUpdated 5 months ago