r/aws_iam_role - add retry for assume role policy update #12436
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since IAM is eventual consistent, new users (referenced in Principal field of assume policy) can take ~30 seconds to propagate in AWS. Similar to role creation, assume role policy update also needs to have a retry logic in case a newly created user is still invisible.
In the example below (aws provider 2.53.0), AWS API call
iam/UpdateAssumeRolePolicy
got a 400 even though userbodebug
had just been created in the sameterraform apply
.I added a retry to fix it and successfully applied the same thing above using the aws provider built locally from this PR.