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

important changes from Amazon #4675

Closed
opokhvalit opened this issue Jan 14, 2016 · 2 comments
Closed

important changes from Amazon #4675

opokhvalit opened this issue Jan 14, 2016 · 2 comments
Labels

Comments

@opokhvalit
Copy link

I've got a message from Amazon today. IMO AWS provider need to be reviewed and changed

Notifications x
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.*

@catsby
Copy link
Member

catsby commented Jan 14, 2016

Hey @opokhvalit thanks for opening this issue. We heard about the longer IDs a while back and did do a quick scan for any impact it may have on Terraform and came to the conclusion that it would not affect us.

Now that longer IDs are available, I took them for a spin. I first spun up some instances with the short form, and then opt-ed in. I was able to spin up more resources with the long instance id and manage them all with no noticeable difference, so I think we're good here.

If you have found a specific area you feel we should re-examine please let us know! Otherwise I'm going to close this for now, as I don't believe we're affected. Thank you!

@catsby catsby closed this as completed Jan 14, 2016
@catsby catsby added the core label Jan 14, 2016
@ghost
Copy link

ghost commented Apr 28, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants