aws_s3_access_point not changing VPC when 'edited in place'

[andrewp-sf]

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

Terraform CLI and Terraform AWS Provider Version

Affected Resource(s)

• aws_s3_access_point

Terraform Configuration Files

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

resource "aws_s3_access_point" "example" {
  bucket = aws_s3control_bucket.example.arn
  name   = "example"
  vpc_configuration {
    vpc_id = aws_vpc.example.id
  }
}

Expected Behavior

Access point is re-created with new VPC configuration (this parameter can't be edited in place).

Actual Behavior

Access point is changed with success according to terraform, however VPC id remains from old version.

Steps to Reproduce

1. terraform apply

Important Factoids

References

• #0000

[ewbankkit]

terraform-provider-aws/aws/resource_aws_s3_access_point.go

Lines 103 to 117 in 16061dd

	"vpc_configuration": {
	Type: schema.TypeList,
	Optional: true,
	ForceNew: true,
	MinItems: 0,
	MaxItems: 1,
	Elem: &schema.Resource{
	Schema: map[string]*schema.Schema{
	"vpc_id": {
	Type: schema.TypeString,
	Required: true,
	},
	},
	},
	},

vpc_id needs ForceNew: true,.

[github-actions]

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