-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: ECS execution role unable to fetch secrets in 5:65.0 #39173
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
@johnzhu-optum 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. |
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. |
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. |
Terraform Core Version
1.8.5
AWS Provider Version
5.65.0
Affected Resource(s)
data.aws_secretsmanager_secret
Expected Behavior
module.<some_name>.data.aws_secretsmanager_secret.ecs-secrets["a_key_name"]: Read complete after 1s [id=arn:aws:secretsmanager:us-east-1:㊙️]
Actual Behavior
module.<some_name>.data.aws_secretsmanager_secret.ecs-secrets["a_key_name"]: Still reading... [29m51s elapsed]
Relevant Error/Panic Output Snippet
Terraform Configuration Files
terraform {
required_version = "
> 1.8.0"> 5.0"backend "s3" {
region = "us-east-1"
}
required_providers {
aws = {
version = "
source = "hashicorp/aws"
}
}
}
Steps to Reproduce
1, create ECS task execution role
2. give permission to get/describe a secret to the role
3. create ECS task, use aws_secretsmanager_secret to fetch the secret arn by name
4. use the role for. execution_role_arn in ECS task json definition
5. apply with terraform
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: