AWS adds Aurora DSQL to FedRAMP Moderate scope

AWS has moved Amazon Aurora DSQL into [FedRAMP Moderate](https://www.deepfathom.ai/glossary#fedramp-moderate) scope for three commercial regions: US East (Ohio), US East (N. Virginia), and US West (Oregon). For teams building federal applications on AWS, that widens the database menu without forcing an immediate retreat to a less suitable service just because the authorization boundary lagged the architecture.

The useful part is narrow and practical. Aurora DSQL can now be considered for applications and workloads subject to FedRAMP Moderate requirements, according to AWS. That matters for procurement packages, authority-to-operate discussions, and architects who want a serverless distributed SQL option with active-active availability and multi-Region strong consistency.

The less fun part is the same as always: a service being in FedRAMP scope is not the same thing as the application being compliant. AWS’s own services-in-scope page puts the customer-side analysis back on the organization, including the nature of the data and whether the service processes or stores customer data: https://aws.amazon.com/compliance/services-in-scope/FedRAMP/. So Monday’s task is not to paste “FedRAMP Moderate” into the design review and move on. It is to update the service eligibility matrix, check the region selection, and make sure the system boundary and control implementation still say what the architecture actually does.