[Bug]: Skip destroying AWS Cloud9 Environment Membership

[obouchta]

Terraform Core Version

1.3.7

AWS Provider Version

4.53.0

Affected Resource(s)

aws_cloud9_environment_membership

Expected Behavior

The resource "aws_cloud9_environment_membership" cannot be destroyed by an administrator. It has to be destroyed by an owner. It would be nice to have a skip_destroy parameter to skip destroying the resource.

Actual Behavior

Terraform try to remove the resource and AWS return an error "Forbidden Exception".

Relevant Error/Panic Output Snippet

│ Error: deleting Cloud9 EC2 Environment (xxxxxxxxxxxxxxxxxxxxxxxx#arn:aws:sts::yyyyyyyyyyyyy:assumed-role/role_name): ForbiddenException: arn:aws:sts::yyyyyyyyyyyyy:assumed-role/gitlab/cicd is not the environment owner so can't delete another member.

Terraform Configuration Files

resource "aws_cloud9_environment_ec2" "this" {
  for_each = var.users
  instance_type = var.instance_type
  name          = "${each.key}-${local.env}-env"
  automatic_stop_time_minutes = 240
  description = "cloud9 environment"
  owner_arn = "arn:aws:sts::${data.aws_caller_identity.current.account_id}:assumed-role/${each.value.role}/${each.key}"
  subnet_id = var.subnet_id
}

resource "aws_cloud9_environment_membership" "this" {
  for_each = var.users

  environment_id = aws_cloud9_environment_ec2.this[each.key].id
  permissions    = "read-write"
  user_arn       = "arn:aws:sts::${data.aws_caller_identity.current.account_id}:assumed-role/${each.value.new_role}/${each.key}"
}

Steps to Reproduce

Please, follow these steps to reproduce the issue:

• Run an Apply on multiple users
• Remove a user from the list
• Run another apply on the users

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[bot]]

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.