As a follow-up to our earlier work to provide longer IDs for a small set of essential EC2 resources, we are now doing the same for the remaining EC2 resources, with a migration deadline of July 2018. You can opt-in on a per-user, per-region, per-type basis and verify that your code, regular expressions, database schemas, and database queries work as expected
If you have code that recognizes, processes, or stores IDs for any type of EC2 resources, please read this post with care! Here’s what you need to know:
Migration Deadline – You have until July 2018 to make sure that your code and your schemas can process and store the new, longer IDs. After that, longer IDs will be assigned by default for all newly created resources. IDs for existing resources will remain as-is and will continue to work.
More Resource Types – Longer IDs are now supported for all types of EC2 resources, and you can opt-in as desired:
I would like to encourage you to opt-in, starting with your test accounts, as soon as possible. This will give you time to thoroughly test your code and to make any necessary changes before promoting the code to production.
More Regions – The longer IDs are now available in the AWS China (Beijing) and AWS China (Ningxia) Regions.
Test AMIs – We have published AMIs with longer IDs that you can use for testing (search for testlongids to find them in the Public images):
For More Information
To learn more, read the EC2 FAQ and the EC2 documentation.
— Jeff;