How do I make an Elastic Beanstalk environment private and accessible only from within the client network?

Short description

You can launch an Elastic Beanstalk environment as either internally or externally visible. This option is available only for a load balanced environment. It's not possible to create an Elastic Beanstalk application without an Elastic IP address for a single instance environment. Elastic IP addresses are used in single instance environments for communication and single instance environments are always public. You might have an issue when you create an Elastic Beanstalk environment that has load balance visibility set to internal, but the instance still uses an Elastic IP or public IP.

Note: You can't create an Elastic Beanstalk environment without an Elastic IP for a single instance environment. It's a best practice to use a load balanced environment with visibility set as Internal. This allows your environment to be created without Elastic IPs for the instances.

Resolution

To make your Elastic Beanstalk environment private and internally visible, complete the following steps:

1. Navigate to your Elastic Beanstalk configuration details.
2. Under Networking and database settings, select Instance settings, and then deselect the Public IP address option.
3. Under Instance traffic and scaling settings, select Load balancer network settings, and then set the Visibility to Internal.

Note: You can set load balancer visibility to Internal or Public only when an Amazon Virtual Private Cloud (Amazon VPC) is selected. If you don't have an Amazon VPC selected, then the load balancer visibility is set to Public and can't be changed.

Related information

Private VPC