AWS Long Resource IDs – They’re Here!

Last November Amazon Web Services told us they would begin rolling out longer Resource IDs for their EC2 and EBS products.  This is just the start as AWS will be rolling out long resource ids to all their products.  This new capability will give AWS  the ability to continue to scale their platforms as demand increases for public & hybrid cloud solutions.

Starting March 7th 2016 this feature is being rolled out to all new customers.  What is this all about you may be asking yourself? In short this changes increases the resource id for EC2 and EBS from 8 characters to 17 characters.  EC2 instances IDs and EBS IDs will look something like i-1234567890abcdef0 from now on.

Any new VPC customer will automatically be opted in, however if you are an existing client you have several options.  You can enable this capability on a region-by-region, user-by-user, type-by-type basis.  Once you opt in for a given region or user new resources with receive the longer IDs.

If you build libraries, tools, or applications that make AWS API calls you need to start your testing and ensure they’re not broken.  If you store the IDs in memory or in a database make sure your data structures can handle it.  If you use the AWS-CLI, Boto, AWS Tools for Powershell tools have all been updated and can be downloaded at

Here’s what to expect for the following year:

1/13/2016 : Longer EC2 Instance and Reservation IDs become available; opt in via APIs or console
3/07/2016 : New accounts default to longer EC2 IDs with option to opt out and receive shorter IDs
4/2016 : Longer ESB Volume and Snapshot IDs become available; opt in via APIs or Console
6/2016 : New accounts default to longer EBS and EC2 IDs with option to opt out
12/2016 : Deadline to add support for Longer IDs.  All new resources will only receive longer IDs