AWS GovCloud Resource Scoping

Customers using AWS GovCloud can now define an explicit compliance boundary when setting up their connection in Drata.

Why It Matters

• Defense, federal, and regulated-government customers can now scope Drata's evaluation to their exact audit boundary.

• Prevents out-of-scope resources from being evaluated, reducing noise, false positives, and unnecessary remediation toil.

• Removes a previous blocker for AWS GovCloud deals where resource scoping was unavailable.

What's New

• Introduces resource-level scoping for AWS GovCloud connections using inclusion and exclusion rules, configured during the create-connection wizard.

• Adds a dedicated Scope step to the AWS GovCloud connection setup flow.

• Supports draft AWS GovCloud connections with wizard state persistence, plus Resume and Delete actions for drafts in the connections list.

• Scoping rules can be viewed and edited from the AWS GovCloud connection overview page after setup.

Notes

• AWS GovCloud connections are single-account by design, so only resource-level scoping is supported (account-level scoping is not applicable).

Learn more: AWS GovCloud Integration Guide