Plugin crashes on apply in version >= 3.64.0 - SEGV in github.com/hashicorp/terraform-provider-aws/internal/service/s3.flattenBucketReplicationConfiguration

[Limess]

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

Terraform: 0.12.1
Terraform AWS Provider 3.64.2

Tested with 3.64.0, 3.64.2, 3.65.0, 3.66.0

The issue does not occur in 3.63.0

Debug Output

https://gist.github.com/Limess/2cca9be66c365558803a959aa5da29fd

Expected Behavior

The apply should not fail

Actual Behavior

The apply fails with:

2021-11-23T09:27:11.689Z [DEBUG] plugin.terraform-provider-aws_v3.64.2_x5: panic: runtime error: invalid memory address or nil pointer dereference
2021-11-23T09:27:11.689Z [DEBUG] plugin.terraform-provider-aws_v3.64.2_x5: [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x670df6f]
2021-11-23T09:27:11.689Z [DEBUG] plugin.terraform-provider-aws_v3.64.2_x5: 
2021-11-23T09:27:11.689Z [DEBUG] plugin.terraform-provider-aws_v3.64.2_x5: goroutine 5767 [running]:
2021-11-23T09:27:11.689Z [DEBUG] plugin.terraform-provider-aws_v3.64.2_x5: github.com/hashicorp/terraform-provider-aws/internal/service/s3.flattenBucketReplicationConfiguration(0xc002325a20, 0x0, 0x0, 0xe7058b0)

Steps to Reproduce

1. terraform apply

Important Factoids

This version works for most of our modules, the module in question is pretty large so it's very hard to work out exactly what is failing, although the stacktrace suggests something in S3 replication.

[Limess]

I found this is a duplicate of #21698, will close this issue.

[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.