aws_vpc support new attribute Ipv6CidrBlockNetworkBorderGroup

[pingwin]

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

1. Support the Ipv6CidrBlockNetworkBorderGroup attribute to provide IPv6 addresses to LocalZones and Wavelength Zones.

New or Affected Resource(s)

• aws_vpc

Potential Terraform Configuration

ipv6_cidr_block_network_border_group = The name of the location from which we advertise the IPV6 CIDR block. Use this parameter to limit the address to this location. 

References

• https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateVpc.html

[efog]

Hi,

I would be interested in working on this as I could need this. Is it necessary for the AWS SDK to be updated with the new properties (ec2/api.go) to start working on this?

ÉB

[ewbankkit]

For full functionality we will also need to add an aws_vpc_ipv6_cidr_block_association resource (and update the aws_vpc data source) as a VPC that includes Local (or Wavelength, if IPv6 is supported) Zone subnets can have multiple IPv6 CIDR blocks (one per network border group).

Relates: #14518.

Will also have to deal with assumptions that a VPC has only a single associated IPv6 CIDR block:

terraform-provider-aws/aws/resource_aws_vpc.go

Lines 271 to 277 in b454050

	for _, a := range vpc.Ipv6CidrBlockAssociationSet {
	if aws.StringValue(a.Ipv6CidrBlockState.State) == ec2.VpcCidrBlockStateCodeAssociated { //we can only ever have 1 IPv6 block associated at once
	d.Set("assign_generated_ipv6_cidr_block", true)
	d.Set("ipv6_association_id", a.AssociationId)
	d.Set("ipv6_cidr_block", a.Ipv6CidrBlock)
	}
	}

terraform-provider-aws/aws/data_source_aws_vpc.go

Lines 214 to 217 in b454050

	if vpc.Ipv6CidrBlockAssociationSet != nil {
	d.Set("ipv6_association_id", vpc.Ipv6CidrBlockAssociationSet[0].AssociationId)
	d.Set("ipv6_cidr_block", vpc.Ipv6CidrBlockAssociationSet[0].Ipv6CidrBlock)
	}

For backwards compatibility it seems to make sense to keep the aws_vpc resource as managing the "region" (i.e. non-Local or Wavelength Zone) network border group's IPv6 CIDR and limit the aws_vpc_ipv6_cidr_block_association to the Local and Wavelength Zone network border groups.

[FireballDWF]

Hi,

I would be interested in working on this as I could need this. Is it necessary for the AWS SDK to be updated with the new properties (ec2/api.go) to start working on this?

The SDK has been updated, so their should be no blockers to working on this.

[github-actions]

This functionality has been released in v3.72.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.