Boto: Support for upcoming resource id length increase?
Does boto2 currently support the new, long resource ids mentioned here: https://aws.amazon.com/blogs/aws/theyre-here-longer-ec2-resource-ids-now-available/ ? If so, what version added support? If not, are there plans to or is boto3 the only way forward?
Philippe23
All 6 comments
I was reviewing release notes, and wasn't able to find anything about this.
For boto3 the AWS FAQ states that 1.2.1+ have support, but can't find anything about it at the boto3 release notes, so it's possible boto2 have support as well.
Did anyone try to work with instances/EBS volumes with long IDs?
juliogonzalez
on 1 Jun 2016
I too am eager to know, we have a large stack of boto2 tools and I'm trying to determine if we need to refactor all of them prior to this change on AWS :-(
jbz
on 18 Jul 2016
@jamesls any idea?
jamesongithub
on 9 Sep 2016
Boto uses strings for resource IDs so I think I should be safe. Anyone able to confirm?
fdavis
on 9 Sep 2016
UPDATE: we moved our AWS account to long form IDs using boto2 in our tooling, and we're OK. We're using latest 2.x.
jbz
on 9 Sep 2016
If you're using boto to create Autos Scaling Groups, the long resource ID's need to be enabled for the root account.
axelabs
on 12 Oct 2016
Related issues
yuvadm
路
9Comments
sbneto
路
6Comments
levivm
路
3Comments
aoerliang
路
6Comments
jun66j5
路
3Comments
Most helpful comment
UPDATE: we moved our AWS account to long form IDs using boto2 in our tooling, and we're OK. We're using latest 2.x.