[Bug]: aws_inspector2_enabler fails to update resources in regions with limited feature sets.

[saefty]

Terraform Core Version

1.9.4

AWS Provider Version

5.620

Affected Resource(s)

  # module.eu-west-3.aws_inspector2_enabler.this is tainted, so must be replaced
-/+ resource "aws_inspector2_enabler" "this" {
      ~ id             = "xxxx-EC2:ECR" -> (known after apply)
      ~ resource_types = [
          - "LAMBDA",
            # (2 unchanged elements hidden)
        ]
        # (1 unchanged attribute hidden)
    }

Expected Behavior

Scan configuration is updated in place without a destroy

Actual Behavior

│ Error: deleting AWS Inspector Enabler (REDACTEDACCOUNTID-EC2:ECR): operation error Inspector2: Disable, https response error StatusCode: 403, RequestID: [REDACTED], AccessDeniedException: Lambda code scanning is not supported in eu-west-3

Relevant Error/Panic Output Snippet

AWS Inspector in eu-west-3 does not support lambda code scanning. Somehow the provider tries to touch the config regardless of what I try: update, apply, destroy

Terraform Configuration Files

the snippet below is executed in all regions within the audit account. The audit account is the delegated admin for aws inspector

data "aws_region" "current" {}

locals {
  inspector2_enabled = [
    "EC2",
    "ECR",
    "LAMBDA",
    "LAMBDA_CODE",
  ]
  inspector2_enabled_euw_3 = [
    "EC2",
    "ECR",
    "LAMBDA",
  ] // Paris does not support Lambda Code (2024-08-13)
}

resource "aws_inspector2_enabler" "this" {
  account_ids    = [data.aws_caller_identity.current.account_id]
  resource_types = data.aws_region.current.name == "eu-west-3" ? local.inspector2_enabled_euw_3 : local.inspector2_enabled
}

Steps to Reproduce

• apply / update configuration in region with limited inspector feature set

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

No

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

[github-actions[bot]]

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

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

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.