Support Attaching and Detaching IAM Roles to RDS Clusters

[dnedev]

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

Description

Since #8038 Terraform supports attaching IAM roles to RDS instances. However, for an S3 integration with Aurora clusters, the roles should be attached to the cluster and rather than an individual instance.

New or Affected Resource(s)

• aws_rds_cluster
• aws_db_instance_role_association (existing resource with reciprocal function for DB instances)
• aws_rds_cluster_role_association (new)

Potential Terraform Configuration

resource "aws_rds_cluster_role_association" "example" {
  cluster_identifier = "${aws_rds_cluster.example.id}"
  feature_name = "s3Import"
  role_arn = "${aws_iam_role.example.arn}"
}

Note: AFAIK, the attached role (${aws_iam_role.example.arn}) should also be added to the iam_roles list for the aws_rds_cluster.

References

• Support Attaching and Detaching IAM Roles to RDS Database Instances (e.g. Oracle S3 Integration) #8038
• https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.LoadFromS3.html

[nickmasster]

Probably a duplicate for #9552.

[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.