data.aws_arn: Fails to validate managed IAM policy ARN

[phyber]

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

Terraform Version

Terraform v0.12.18
+ provider.aws v2.43.0

Affected Resource(s)

• data.aws_arn

Terraform Configuration Files

data aws_arn cloudwatch_readonly_access {
  arn = "arn:aws:iam::aws:policy/CloudWatchReadOnlyAccess"
}

Debug Output

N/A

Panic Output

N/A

Expected Behavior

I should have been able to use a managed IAM policy ARN in the aws_arn data type.

Actual Behavior

The following errors occurs

Error: "arn" doesn't look like a valid ARN ("^arn:[\\w-]+:([a-zA-Z0-9\\-])+:([a-z]{2}-(gov-)?[a-z]+-\\d{1})?:(\\d{12})?:(.*)$"): "arn:aws:iam::aws:policy/CloudWatchReadOnlyAccess"

Steps to Reproduce

1. Create some Terraform including the above data source
2. terraform plan

Important Factoids

N/A

References

N/A

Other

I'll have a PR shortly to fix this issue.

[phyber]

I have submitted a pull request to solve this issue. (Just leaving this comment since the community note says to do so, PR already linked against issue).

[bflad]

The fix for this (including the aws_arn data source and other places where use validateArn for attribute validation) has been merged and will release with version 2.44.0 of the Terraform AWS Provider, next Thursday. Thanks @phyber for the implementation. 👍

[ghost]

This has been released in version 2.44.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 for triage. Thanks!

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!