Providing IPV4 address to EC2 instances under Auto-Scaling-Groups in AWS

[balapraneethreddy98]

Is your request related to a new offering from AWS?

Is this functionality available in the AWS provider for Terraform? See CHANGELOG.md, too.

• No 🛑: please wait to file a request until the functionality is available in the AWS provider
• Yes ✅: please list the AWS provider version which introduced this functionality

Is your request related to a problem? Please describe.

Yes, While deploying EC2 instances using auto scaling groups in terraform, the EC2 instances does not have an IPV4 Address associated with the EC2 instances. This is not available in the latest version i.e (v6.10.0), but the same functionality of assigning/enabling an IPV4 address is available as an input variable in the version (v2.5.0).

Input Variable Name - "associate_public_ip_address"

• ASG Terraform Docs (v6.10.0) - https://registry.terraform.io/modules/terraform-aws-modules/autoscaling/aws/6.10.0

• ASG Terraform Docs (v2.5.0) - https://registry.terraform.io/modules/terraform-aws-modules/autoscaling/aws/2.5.0?tab=inputs

Use Case Scenario: Assuming, an application is deployed with Auto Scaling Groups in an EC2 instance, considering the EC2 instance needs to communicate with Internet (Assume it is placed in a public subnet) then in this case since the latest version doesn't have the option to enable the IPV4 address, the EC2 cannot communicate with the internet.

Describe the solution you'd like.

A potential solution would be to enable the input variable in the latest versions that associates an IPV4 address to the EC2 instance which is deployed in a public subnet and that would allow the EC2 instance to communicate with the internet and transfer data as needed.

Describe alternatives you've considered.

An alternative approach for this EC2 instance to communicate with the Internet would be to deploy the EC2 in the private subnet since that has an Private IPV4 address associated with it, so therefore the traffic can be forwarded to a NAT Gateway -> Application Load Balancer -> Out to the Internet gateway configured.

Additional context

• The below screenshot displays the EC2 not having an IPV4 address, when deployed in private subnet using ASG terraform module.

[github-actions[bot]]

This issue has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this issue will be closed in 10 days

[github-actions[bot]]

This issue was automatically closed because of stale in 10 days

[github-actions[bot]]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.