Assigning prefixes to Amazon EC2 network interfaces

[ewbankkit]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Amazon Virtual Private Cloud (VPC) now allows you to assign IPv4 and IPv6 prefixes to your EC2 instances, enabling you to scale and simplify the management of your container and networking applications that require multiple IP addresses on an instance.

New or Affected Resource(s)

• aws_network_interface

Potential Terraform Configuration

resource "aws_network_interface" "example" {
  ipv4_prefix_count = 1
}

References

• Announcement
• User Guide

Requires AWS SDK v1.40.6:

• build(deps): bump github.com/aws/aws-sdk-go from 1.40.5 to 1.40.6 #20281

[github-actions]

This functionality has been released in v3.64.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

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.