[Bug]: IAM Roles Anywhere CreateProfileInput.RoleArns missing

[gclawes]

Terraform Core Version

1.4.6

AWS Provider Version

5.65.0

Affected Resource(s)

• aws_rolesanywhere_profile

Expected Behavior

Creating a profile with an empty list of role_arns should result in a profile being created.

According to CreateProfile API docs, roleArns is a required filed that can be an empty array: https://docs.aws.amazon.com/rolesanywhere/latest/APIReference/API_CreateProfile.html#rolesanywhere-CreateProfile-request-roleArns

Actual Behavior

Profile fails to create due to an API validation error (see below).

Relevant Error/Panic Output Snippet

│ Error: creating RolesAnywhere Profile (iam-ra-test-us-east-1): operation error RolesAnywhere: CreateProfile, 1 validation error(s) found.
│ - missing required field, CreateProfileInput.RoleArns.
│
│
│   with aws_rolesanywhere_profile.iam-ra-test-us-east-1,
│   on iam-ra-test.tf line 142, in resource "aws_rolesanywhere_profile" "iam-ra-test-us-east-1":
│  142: resource "aws_rolesanywhere_profile" "iam-ra-test-us-east-1" {

Terraform Configuration Files

Example profile:

resource "aws_rolesanywhere_profile" "iam-ra-test-us-east-1" {
  provider = aws.local

  tags = local.tags

  enabled = true
  name    = "iam-ra-test-us-east-1"

  role_arns = []
}

Steps to Reproduce

1. Attempt to deploy a simple profile (example above) with empty list role_arns = []

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• 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.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[DanielRieske]

Hi @gclawes 👋, thank you for raising this issue I can indeed reproduce this behaviour, I was working on some technical debt within this service so I will gladly solve this issue alongside it.

Will add the PR later today.

[gclawes]

Thanks. I discovered this while re-testing an established deployment procedure, so I know this used to work correctly.

[github-actions]

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.

[github-actions]

This functionality has been released in v5.66.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]

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.