Does Amazon Web Services (Sydney/Melbourne + Bedrock) keep data in Australia?

As a customer, you choose the AWS Region(s) in which your customer content is stored, allowing you to deploy AWS services in the location(s) of your choice, in accordance with your specific geographic requirements. For example, if an AWS customer in Australia wants to store their data only in Australia, they can choose to deploy their AWS services exclusively in the Asia Pacific (Sydney) AWS Region.

Note: Same page (and the Data Privacy FAQ) say AWS will not move or replicate content outside the chosen Region(s) without agreement, except as required by law or a binding order. Melbourne (ap-southeast-4) is also an Australian Region. Not every AWS service is available in every Region; customer must check Regional Services.

In-Region: Your requests never leave the AWS Region you specify. Use this when regulations require strict single-Region data processing. Geographic (Geo): Bedrock routes your request to a Region within a defined geography (US, Canada, EU, Asia Pacific, Japan, Australia, or India), keeping data within that geography. ... Global: Bedrock routes your request to a supported commercial Region worldwide.

Note: For regional AWS services deployed only in Sydney/Melbourne, processing stays in those Regions subject to each service's docs. For Bedrock, residency depends on the inference profile: direct model IDs are in-Region; au. geographic profiles keep routing among Australian Regions; apac. can leave Australia; global. has no geographic restriction. Model availability differs by option.

The vendor does not publish a statement on this.

Note: AWS states support personnel who assist with support requests do not have access to customer data, and many core systems are designed with zero operator access. The pages opened do not publish an Australia-only support personnel location. Operator access, when needed for troubleshooting, is described as least-privilege and logged, without a country restriction on this page.

For example, if an AWS customer in Australia wants to store their data only in Australia, they can choose to deploy their AWS services exclusively in the Asia Pacific (Sydney) AWS Region.

Note: Choosing Sydney or Melbourne is part of ordinary AWS Region selection, not a separate paid residency add-on. Some Bedrock geographic/global profiles change routing and pricing; in-Region inference is the strictest single-Region option where the model supports it.

Some Regions belong to more than one geography: from Asia Pacific (Sydney), for example, you can use either the au prefix, which routes only among Australian Regions, or the apac prefix, which can route to any supported Asia Pacific Region, so choose the prefix that matches your data residency requirement.

Note: Services or features not available in Sydney/Melbourne, global services, and Bedrock global or apac inference profiles take data outside Australia. Amazon Bedrock Marketplace is excluded from the IRAP in-scope list. Customer content copied by the customer to another Region is outside this page's AU scope.

The IRAP assessment covers in-scope services in the AWS Sydney and Melbourne Regions. The covered AWS services that are in scope for the IRAP assessment can be found on the AWS Services in Scope by Compliance Program webpage.

Note: Services-in-scope page (updated 2 July 2026 on the page fetched) marks Amazon Bedrock [excludes Amazon Bedrock Marketplace], Amazon S3, EC2 and many other services as IRAP PROTECTED. Reports are in AWS Artifact (not read). IRAP is an assessment, not an agency authorisation.