ap-southeast-4: Asia Pacific (Melbourne)
ap-southeast-4 is the code for the Asia Pacific (Melbourne) region, AWS's second region in Australia. It is an opt-in region, enabled per account, and is mainly used as an in-country disaster-recovery partner for Sydney or as a primary region for users and organisations in Victoria.
Why a second Australian region matters
Australian regulators, government agencies and boards often ask for recovery plans that survive the loss of an entire region without sending data overseas. Before Melbourne, the only answer was multiple Availability Zones in Sydney. With ap-southeast-4, you can replicate between two Australian cities several hundred kilometres apart.
Melbourne also suits Victorian state-government bodies, universities and companies whose users are concentrated in the south-east and who simply want the closest region.
Turning it on
aws account get-region-opt-status --region-name ap-southeast-4
aws account enable-region --region-name ap-southeast-4
# from the Organizations management account, for a member
aws account enable-region --region-name ap-southeast-4 \
--account-id 123456789012Enable the region in every account involved in recovery: the workload accounts, the backup vault account, the logging account and the security tooling account. A DR plan that fails because the log archive can't receive CloudTrail from Melbourne is more common than you'd think.
Building Sydney to Melbourne recovery
- Check coverage. Melbourne's catalogue is smaller than Sydney's. Check each managed service and instance family before you write the runbook.
- Create regional resources. KMS keys, VPCs, security groups, Secrets Manager secrets and SSM parameters are all regional. Pre-create or replicate them.
- Replicate data. S3 replication, cross-region snapshot copies and AWS Backup copy jobs, re-encrypted under Melbourne keys.
- Raise quotas. Size them for full production load, not a pilot light.
- Rehearse. Fail over a non-critical service first and time it.
Targeting ap-southeast-4
Set --region ap-southeast-4, AWS_REGION=ap-southeast-4 or a profile region. Endpoints follow <service>.ap-southeast-4.amazonaws.com. If the credentials you use come from the global STS endpoint, their tokens are not valid in opt-in regions by default, so a DR script can fail at the first API call; switch to regional STS ahead of time.
Watch the numbering: Sydney is ap-southeast-2 and Melbourne ap-southeast-4; ap-southeast-3 in between is Jakarta.
Related regions
ap-southeast-2 (Sydney) is the primary partner. ap-southeast-6 serves New Zealand. ap-southeast-1 (Singapore) is the nearest large region outside Australia for data without residency rules.
Melbourne as a primary region
Some organisations flip the usual pattern: Melbourne for production, Sydney for recovery. That fits Victorian public bodies and businesses whose users and offices are mostly in the state, or teams that want their primary away from the busiest Australian region. The cost is a smaller service catalogue in the primary, which matters if you depend on newly launched managed services. Whichever direction you choose, keep the two regions' infrastructure defined in the same code with only the region parameter changing, so recovery doesn't drift from production over time.
Questions
Where is ap-southeast-4?
In Melbourne, Victoria, Australia.
Is ap-southeast-4 opt-in?
Yes. Enable it per account before using it.
Is Melbourne a good DR region for Sydney?
Yes, it's the in-country option. Check service availability in Melbourne for everything in your recovery plan and raise quotas in advance.
During a regional failover you want to watch Sydney and Melbourne side by side. CloudConsole, a phone app for AWS, is built to show alarms and resources across regions on your phone.
About the app → · Download on the App Store