Lab findings: New Zealand
Overview
Section titled “Overview”AWS shipped cross-Region PrivateLink
Cross-Region AWS PrivateLink for interface endpoints. Works for some Region pairs; not for ap-southeast-6 (Auckland) as of Sep 2026. Re-check before assuming coverage.
for some Region pairs in late 2024. Sydney was in that launch set; Auckland
(ap-southeast-6) was not
(What’s New, Nov 2024).
Checked again as of Sep 2026. Coverage can change, so re-run discovery before you assume Auckland is still out.
What we checked
Section titled “What we checked”| Consumer Region | Service Region | XR discovery |
|---|---|---|
ap-southeast-2 |
ap-southeast-6 |
Empty / invalid |
ap-southeast-6 |
ap-southeast-2 |
Empty / invalid |
Cross-Region PrivateLink into or out of Auckland fails both ways. You cannot privately read a Sydney S3 bucket from an Auckland VPC (or the reverse) on that path.
What to do instead
Section titled “What to do instead”Skip Syd↔Akl private S3 reads over cross-Region PrivateLink. Use regional buckets, replication, and regional gateway endpoints (what this lab builds).
Extra note (Auckland SSM)
Section titled “Extra note (Auckland SSM)”When creating the Auckland consumer,
com.amazonaws.ap-southeast-6.ec2messages returned InvalidServiceName.
Session Manager still reached Online with only ssm + ssmmessages
interface endpoints. demo.sh skips missing services and needs at least those
two.