Check your region's actual authorization boundary

The prompt

If you operate in a regulated environment (GovCloud, FedRAMP, similar), verify — against current official documentation, not memory or a blog post — the actual service availability and authorization boundary for every AWS service your agent stack depends on in that region.

Why it's built that way

Regulated deployments must be built from the actual service availability and authorization boundary in the target region — network paths, identities, logging, KMS keys, data residency, egress, and evidence retention have to be designed before autonomous tool access is enabled, not discovered afterward.

What to do with the answer

Any service you can't confirm in the current official scope table gets flagged for your account team before it's relied on.