Skip to content
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

IAM Role ARN Returned as Unique ID #22018

Closed
YakDriver opened this issue Dec 2, 2021 · 2 comments · Fixed by #22004
Closed

IAM Role ARN Returned as Unique ID #22018

YakDriver opened this issue Dec 2, 2021 · 2 comments · Fixed by #22004
Assignees
Labels
service/iam Issues and PRs that pertain to the iam service.
Milestone

Comments

@YakDriver
Copy link
Member

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

[This is a documenting issue.]

Immediately after a role is created, AWS sometimes returns a unique ID (e.g., AROAQ7SSZBKHRKPWRZUN6) in the ARN field. This can create problems with drift detection and problems like seen in #8905. The problem appears to be random and may depend on how busy AWS is currently.

The AWS provider should not ever include a unique ID in aws_iam_role.arn regardless what AWS returns.

Affected Resource(s)

  • aws_iam_role

Expected Behavior

ARN attribute should always be an actual ARN (e.g., arn:aws:iam::12345678901:role/tf-acc-test-7531775986226331375-mercedes).

Actual Behavior

Occassionally (rarely), aws_iam_role.arn is a unique ID (e.g., AROAQ7SSZBKHRKPWRZUN6).

Steps to Reproduce

  1. terraform apply
  2. Wait for planets to align
  3. Preferably try this when AWS is really busy (maybe during re:invent?)
  4. See strange occurences

References

@github-actions github-actions bot added the service/iam Issues and PRs that pertain to the iam service. label Dec 2, 2021
@YakDriver YakDriver self-assigned this Dec 2, 2021
@github-actions github-actions bot added this to the v3.69.0 milestone Dec 2, 2021
@github-actions
Copy link

This functionality has been released in v3.69.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 26, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
service/iam Issues and PRs that pertain to the iam service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant