Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

providers/aws: expose instance availability-zone-id as AWS_AVAILABILITY_ZONE_ID #748

Merged
merged 1 commit into from
May 10, 2022

Conversation

abhinavdahiya
Copy link
Contributor

ec2 instance metadata exposes the physical id for availability zone. Physical zone ids are useful
because they are same across AWS accounts and helpful when trying to decide if instances are actually
in the same zone when reconciling that between instances in different accounts.

See doc:

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instancedata-data-categories.html

placement/availability-zone-id	The static Availability Zone ID in which the instance is launched. The Availability Zone ID is consistent across accounts. However, it might be different from the Availability Zone, which can vary by account.	2020-08-24

This is available in api versions starting 2020-08-24, and afterbun already uses 2021-01-03 1.

…TY_ZONE_ID

ec2 instance metadata exposes the physical id for availability zone. Physical zone ids are useful
because they are same across AWS accounts and helpful when trying to decide if instances are actually
in the same zone when reconciling that between instances in different accounts.

See doc:
> https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instancedata-data-categories.html

```
placement/availability-zone-id	The static Availability Zone ID in which the instance is launched. The Availability Zone ID is consistent across accounts. However, it might be different from the Availability Zone, which can vary by account.	2020-08-24
```

This is available in api versions starting 2020-08-24, and afterbun already uses 2021-01-03 [1].

[1]: https://github.com/coreos/afterburn/blob/640ce9790c4f2d56aa75d1e3ad63f8011bec4255/src/providers/aws/mod.rs#L83
Copy link
Contributor

@bgilbert bgilbert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

@bgilbert
Copy link
Contributor

Known test failure. Merging.

@bgilbert bgilbert merged commit 2d0b53f into coreos:main May 10, 2022
@abhinavdahiya abhinavdahiya deleted the az_id branch May 10, 2022 17:23
@abhinavdahiya
Copy link
Contributor Author

@bgilbert any idea when this rolls out to FCOS ?

@bgilbert
Copy link
Contributor

bgilbert commented Jun 2, 2022

No Afterburn release is currently scheduled. Is something blocking on this change?

@sohankunkerkar
Copy link
Member

sohankunkerkar commented Jun 14, 2022

@abhinavdahiya it should be available in the next testing release

https://koji.fedoraproject.org/koji/buildinfo?buildID=1983824

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.

None yet

3 participants