AWS Resources that are in suspended accounts failing plan/apply stages - Can we ignore or bypass these accounts?

[MaxMoon771]

We have recently suspended a few aws accounts, but we did not delete or remove any resources before the process... I am having issues with iambic unable to update a PermissionSet AWSPowerUserAccess due to what I believe is the suspended account. Updating and running iambic plan for the resource is resulting with this error. I have commented out the suspended accounts in iambic_config to avoid scanning that account. I have done through and removed all references to this account.

Curious if anyone has ran into issues with suspended accounts and issues with modifying resources?

[
  {
    "resource_id": "AWSPowerUserAccess",
    "resource_type": "aws:identity_center:permission_set",
    "template_path": "resources/aws/identity_center/permission_set/awspoweruseraccess.yaml",
    "proposed_changes": [],
    "exceptions_seen": [
      {
        "account": "gafg-master - (851158803636)",
        "resource_id": "AWSPowerUserAccess",
        "proposed_changes": [],
        "exceptions_seen": [
          {
            "change_type": "Unknown",
            "account": "gafg-master - (851158803636)",
            "resource_id": "AWSPowerUserAccess",
            "resource_type": "aws:identity_center:permission_set",
            "exceptions_seen": [
              "'020619688306'"
            ]
          }
        ]
      }
    ]
  }
]

Expected behavior
Hoping iambic can do a health check and see accounts/resources in suspended state and allow the plan/apply to proceed

Community Engagement
Your vote counts! Please support this bug report by adding a 👍 reaction to the original issue, which will aid the community and maintainers in addressing this problem.

Please refrain from adding "+1" or "me too" comments, as these create unnecessary noise for issue followers and do not help in prioritizing the issue. If you wish to contribute to solving this issue or have submitted a pull request, please leave a comment.

[MaxMoon771]

Found a document via Merge in Aug 2023.
Tried marking the accounts in iambic_config = disabled
Re-ran the import process to update those resources as disabled.
Same error