Avoid Using Public IPv4 in Elastic Beanstalk

Question

I am using Elastic Beanstalk to deploy my Java backend APIs. At first, I did not use load balancer but then I found that I need to call APIs using HTTPS instead of HTTP. Therefore, I added one load balancer. However, it uses two public IPv4 address which cost a lot. Is there a way to avoid it?

re:Post Agent · Answer

To address your concern about the cost associated with public IPv4 addresses in your Elastic Beanstalk environment with a load balancer, there are a few approaches you can consider:

1. Use an internal load balancer: If your application doesn't need to be directly accessible from the internet, you can configure your Elastic Beanstalk environment to use an internal load balancer. This type of load balancer uses private IP addresses instead of public ones, which would eliminate the charges for public IPv4 addresses.

2. Implement IPv6 support: You could consider migrating your load balancer to a dual-stack configuration without public IPv4. This would allow your load balancer to accept IPv6 connections while eliminating the need for public IPv4 addresses. However, this approach requires that your VPC and subnets support IPv6, and you'd need to ensure that your clients can connect via IPv6.

3. Use a CDN or proxy: If you need to maintain IPv4 support for clients while avoiding public IPv4 charges on your load balancer, you could use a content delivery network (CDN) or a separate proxy that supports both IPv4 and IPv6. This intermediary service would handle IPv4 connections and forward traffic to your IPv6-only load balancer.

4. Optimize your architecture: Review your overall architecture to see if you can consolidate resources or use alternative designs that require fewer public IP addresses.

It's important to note that completely eliminating public IPv4 addresses might not be feasible depending on your application's requirements and client needs. If you do implement changes, make sure to thoroughly test your setup to ensure your APIs remain accessible and functional.

Remember that while these strategies can help reduce costs associated with public IPv4 addresses, they may introduce additional complexity to your architecture. Carefully consider the trade-offs between cost savings and operational complexity when deciding on the best approach for your specific use case.  
**Sources**  
[How to remove IPv4 public IP address from load balancer? | AWS re:Post](https://repost.aws/questions/QUSvzSz7KySrmioHWmighY4A/how-to-remove-ipv4-public-ip-address-from-load-balancer)  
[Migrate Application Load Balancer from IPv4  to dual-stack without public IPv4 | AWS re:Post](https://repost.aws/questions/QUQGz4SogWQii-GQT93V_Tug/migrate-application-load-balancer-from-ipv4-to-dual-stack-without-public-ipv4)

Avoid Using Public IPv4 in Elastic Beanstalk

Add your answer

Relevant content