Skip to content

Fix IMDS region resolution in Local Zones - #10843

Open
AndrewAsseily wants to merge 2 commits into
v2from
nyandrew/imds-region-local-zones
Open

AndrewAsseily wants to merge 2 commits into
v2from
nyandrew/imds-region-local-zones

Conversation

@AndrewAsseily

Copy link
Copy Markdown
Contributor

Issue #, if available: CLI-2692

Description of changes: InstanceMetadataRegionFetcher derived the region by stripping the last character from placement/availability-zone, which breaks for Local Zones (us-east-1-atl-2a became us-east-1-atl-2). Read placement/region instead, which returns the parent region directly.

Also fix a typo in scripts/new-change.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

InstanceMetadataRegionFetcher derived the region by stripping the last
character from placement/availability-zone, which breaks for Local Zones
(us-east-1-atl-2a became us-east-1-atl-2). Read placement/region instead,
which returns the parent region directly.

Also fix a typo in scripts/new-change.
@AndrewAsseily
AndrewAsseily requested a review from a team as a code owner November 3, 2026 15:09
The region fetcher now reads placement/region, so the mocked IMDS
response is a region rather than an availability zone.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant