# AWS - new EC2 Resource ID length - is Ansible ready? **URL:** \ **Category:** Ansible Project\ **Tags:** aws\ **Created:** [January 18, 2016, 4:40pm UTC](https://forum.ansible.com/t/aws-new-ec2-resource-id-length-is-ansible-ready/20256 "2016-01-18T16:40:09Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Adam\_Johnson](https://avatars.discourse-cdn.com/v4/letter/a/c57346/32.png) [@Adam\_Johnson](https://forum.ansible.com/u/Adam_Johnson)\ **Post date:** [January 18, 2016, 4:40pm UTC](https://forum.ansible.com/t/aws-new-ec2-resource-id-length-is-ansible-ready/20256/1 "2016-01-18T16:40:09Z")
AWS have recently announced the opt-in scheme for new Resource ID lengths for instances and reservations, which will become mandatory in December. Since Ansible uses Boto directly and probably doesn’t make any assumptions about the lengths of resource IDs, I would guess it is fine, but has any work been done to check it? A bit hesitant to just click “opt-in” on the AWS console since it’s account-wide. Adam ---
**Author:** ![Adam\_Johnson](https://avatars.discourse-cdn.com/v4/letter/a/c57346/32.png) [@Adam\_Johnson](https://forum.ansible.com/u/Adam_Johnson)\ **Post date:** [April 19, 2016, 10:24am UTC](https://forum.ansible.com/t/aws-new-ec2-resource-id-length-is-ansible-ready/20256/2 "2016-04-19T10:24:03Z")
Ok I’m now assuming that it is compatible. All new accounts since March 7 have it activated: [https://aws.amazon.com/about-aws/whats-new/2016/01/longer-format-for-ec2-resource-ids/](https://aws.amazon.com/about-aws/whats-new/2016/01/longer-format-for-ec2-resource-ids/) ---
**Author:** ![Braxton\_Beyer](https://avatars.discourse-cdn.com/v4/letter/b/ecccb3/32.png) [@Braxton\_Beyer](https://forum.ansible.com/u/Braxton_Beyer)\ **Post date:** [September 13, 2016, 6:13pm UTC](https://forum.ansible.com/t/aws-new-ec2-resource-id-length-is-ansible-ready/20256/3 "2016-09-13T18:13:25Z")
What version of Ansible are you using? ---
**Author:** ![Josh\_Smift1](https://avatars.discourse-cdn.com/v4/letter/j/bcef8e/32.png) [@Josh\_Smift1](https://forum.ansible.com/u/Josh_Smift1)\ **Post date:** [September 14, 2016, 5:59pm UTC](https://forum.ansible.com/t/aws-new-ec2-resource-id-length-is-ansible-ready/20256/4 "2016-09-14T17:59:36Z")
We opted in recently; we're running Ansible 2.1.1.0, and everything seems fine. Has anyone seen any issues with it?                                       -Josh (jbs@care.com) (apologies for the automatic corporate disclaimer that follows) This email is intended for the person(s) to whom it is addressed and may contain information that is PRIVILEGED or CONFIDENTIAL. Any unauthorized use, distribution, copying, or disclosure by any person other than the addressee(s) is strictly prohibited. If you have received this email in error, please notify the sender immediately by return email and delete the message and any attachments from your system. ---
**Author:** ![Adam\_Johnson](https://avatars.discourse-cdn.com/v4/letter/a/c57346/32.png) [@Adam\_Johnson](https://forum.ansible.com/u/Adam_Johnson)\ **Post date:** [September 14, 2016, 6:30pm UTC](https://forum.ansible.com/t/aws-new-ec2-resource-id-length-is-ansible-ready/20256/5 "2016-09-14T18:30:40Z")
Since we opted in everything has been fine with all Ansible versions from 2.0.1.0 onwards