Closed colinlabs closed 3 weeks ago
Find a description:https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketPolicy.html
If you don't have GetBucketPolicy permissions, Amazon S3 returns a 403 Access Denied error. If you have the correct permissions, but you're not using an identity that belongs to the bucket owner's account, Amazon S3 returns a 405 Method Not Allowed error.
Hey @colinlabs ,
Try setting disable_bucket_update = true
in your remote_state
--> config
configurations, and share if you still experience the same error.
By default, Terragrunt will attempt to make sure all relevant backend resources available for use by checking to see if they're provisioned, etc. It can be confusing, but a lot of users configure certain authentication configurations for OpenTofu/Terraform, thinking the same authentication configurations will be used by Terragrunt, but they aren't.
If disabling bucket updates solves your issue, you can either chose to manage the backend resources manually, or investigate the issue with --terragrunt-log-level debug
.
Overall, this issue has more to do with AWS authentication than how Terragrunt functions.
@yhakbar thanks, It's work to me
Describe the bug
We created an s3 bucket in account A, and then s3 tested and granted access to a role in account B. The bucket information could be correctly read in terraform, but terragunant could not correctly obtain bucekt information at noon.
Error:
config:
s3 policy
Expected behavior
It can be similar to terraform's behavior, and can read bucekt information across aws accounts.
Versions