[Bug]: sporadic errors in aws_eks_access_policy_association

[pdeva]

Terraform Core Version

1.7.3

AWS Provider Version

5.36.0

Affected Resource(s)

• aws_eks_access_policy_association

Expected Behavior

I am associating AWS SSO created IAM roles to eks access entries using code given below. if this code is going to fail due to principal_arn not being found, it should fail during the planning phase itself. it should never be the case that principal_arn is found during planning and i get an error of it not being found during application phase, especially if no other changes to aws is made during this time.

Actual Behavior

Here is a screenshot of this full terraform run. you can see all the policyArn this fails on was indeed inferred correctly in the data sources.

on just re-running terraform, without making any changes, the errors go away and apply finishes. its unclear what causes the code to fail in the first place and why it suddenly works next time

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

terraform {
  required_version = ">= 1.0"
  cloud {
    workspaces {
      name = "staging"
    }
  }

  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 5.0"
    }
 
  }
}

Steps to Reproduce

data "aws_iam_roles" "roles" {
  name_regex  = "AWSReservedSSO_${var.sso_permset_name}_.*"
  path_prefix = "/aws-reserved/sso.amazonaws.com/"
}

locals {
  principal_arn = one(data.aws_iam_roles.roles.arns)
}

resource "aws_eks_access_entry" "this" {
  cluster_name      = var.eks_cluster_name
  principal_arn     = local.principal_arn
  kubernetes_groups = var.kubernetes_groups
}

resource "aws_eks_access_policy_association" "this" {
  count         = length(var.policy_arn) > 0 ? 1 : 0
  cluster_name  = var.eks_cluster_name
  principal_arn = local.principal_arn
  policy_arn    = var.policy_arn
  access_scope {
    type = "cluster"
  }
}

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.

[ewbankkit]

Relates #35535.

[pdeva]

so in the runs mentioned above, the roles in question were not updated at all. thats why a data source is used for the role instead of a resource

[github-actions]

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