[Bug]: data.aws_secretsmanager_secret_version no longer pulls secrets

[jfgordon2]

Terraform Core Version

1.9.4

AWS Provider Version

5.65.0

Affected Resource(s)

data.aws_secretsmanager_secret_version

Expected Behavior

This data resource should successfully read a secret with a provided ARN. This was tested with a cross-account secret, and on the darwin_arm64 platform. This doesn't appear to affect the linux_amd64 version.

Actual Behavior

The output is that it will return as "Still reading..." until it times out after 20 minutes.

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

data "aws_secretsmanager_secret_version" "secret" {
secret_id = "arn:aws:secretsmanager:us-west-2:1234567890:secret:secret_path"
}

Steps to Reproduce

On an M1 mac, run terraform plan from one AWS account with the above data block on version 5.65.0. 5.64.0 doesn't appear affected.

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• 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.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[ewbankkit]

Relates:

• [Bug]: data block to fetch aws_iam_roles hangs forever #39110
• [Bug]: Dynamic Provider in Agents Broken #39115
• [Bug]: AWS STS TLS Timeouts when running terraform init #39125

[ewbankkit]

@jfgordon2 Assuming that the Go 1.22.6 downgrade with Terraform AWS Provider v5.67.0 fixed this problem, I'm going to close this issue. Discussion will continue in #39311.

[github-actions]

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

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