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

Salt-Cloud assesment: AWS is changing the Instance ID format, does have any impact? #30352

Closed
DanyC97 opened this issue Jan 14, 2016 · 10 comments
Labels
Question The issue is more of a question rather than a bug or a feature request RIoT Relates to integration with cloud providers, hypervisors, API-based services, etc. Salt-Cloud
Milestone

Comments

@DanyC97
Copy link

DanyC97 commented Jan 14, 2016

AWS just released a notification saying

We're transitioning instance IDs and reservation IDs to a longer format

AWS is transitioning instance IDs and reservation IDs to a longer format. 
The old format is a resource identifier followed by an 8-character string, and the new format is a resource identifier followed by a 17-character string. 
You have until December 2016 to opt in to the longer format.

If you do not take any action, you will be opted in automatically on December 2016, when all new instance IDs and Reservation IDs will be created with the longer format. 
Until the deadline, you can opt in and out of the new format as needed. 
Only newly created resources receive longer IDs; existing resources are unaffected.

Manage your transition to longer instance IDs and reservation IDs with Resource ID length management, and read more about the new format.

The new format is here

@DanyC97 DanyC97 changed the title Salt-Cloud assesment: AWS is changing the Instance ID format, does it have any impact? Salt-Cloud assesment: AWS is changing the Instance ID format, does have any impact? Jan 14, 2016
@techhat
Copy link
Contributor

techhat commented Jan 14, 2016

I was wondering when Amazon would get around to doing that.

We'll want to double-check of course, but last I checked Salt Cloud doesn't care what the IDs actually look like, so long as they're there. This should not have any impact.

@jfindlay jfindlay added Question The issue is more of a question rather than a bug or a feature request Salt-Cloud RIoT Relates to integration with cloud providers, hypervisors, API-based services, etc. labels Jan 14, 2016
@jfindlay jfindlay added this to the Blocked milestone Jan 14, 2016
@DanyC97
Copy link
Author

DanyC97 commented Jan 14, 2016

👍 @techhat
I was thinking that is the case but thought a pair of eyes won't hurt.

@rallytime
Copy link
Contributor

@DanyC97 and @techhat please see PR #30433, as it is related.

@techhat
Copy link
Contributor

techhat commented Jan 19, 2016

Thanks @rallytime. I wasn't aware of that pillar. Do you know of any other regular expressions that have to do with AWS?

@rallytime
Copy link
Contributor

I don't. I just saw that PR come in today and remembered this issue. We should look around though...

@rallytime
Copy link
Contributor

After an audit of the related aws code, and now that #30553 and #30433 have been merged, this issue has been resolved. Thanks for bringing it to our attention @DanyC97!

@DanyC97
Copy link
Author

DanyC97 commented Jan 23, 2016

Always a pleasure @rallytime 👍

@QuinnyPig
Copy link
Contributor

It would appear that salt-cloud is still provisioning instances with short IDs in environments where long IDs are supported.

@ehrhardt
Copy link

I'm unable to use salt-cloud. It's not working properly for long instance IDs and volume IDs.

@QuinnyPig
Copy link
Contributor

QuinnyPig commented Jan 26, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Question The issue is more of a question rather than a bug or a feature request RIoT Relates to integration with cloud providers, hypervisors, API-based services, etc. Salt-Cloud
Projects
None yet
Development

No branches or pull requests

6 participants