solved AWS new longer EC2 Resource IDs...action required?

Hi, I got an email today from AmazonAWS concerning this. It read in part:

"Dear Amazon EC2 Customer,
In November, we announced that EC2 and EBS will have longer identifiers for instances, volumes, reservations, and snapshots to support the ongoing growth of Amazon Web Services. Starting today, you can opt into using longer EC2 instance and reservation IDs using APIs or the AWS Management Console. Note: Longer EBS volume and snapshot IDs will be available in April 2016.
From now until early December 2016, you can test your systems with the longer format and opt in when you are ready. From December, all new instances, reservations, volumes, and snapshots will be created with longer IDs. We strongly recommend testing your systems and opting in to the longer ID format across all of your accounts before December 2016. All AWS accounts created after March 7, 2016, will automatically default to longer instance and reservation IDs, with the option to request the original, shorter 8-character format if necessary."

Does this effect my Jamroom AWS S3 bucket backups? On my AWS dashboard, never see EC2 and EBS being used- only S3.

Do I need to go through the process as outlined on this page?:
https://aws.amazon.com/blogs/aws/theyre-here-longer-ec2-resource-ids-now-available/
At the end of that page, it says:
"This blog post applies to all AWS regions and accounts. AWS accounts created on or after March 7, 2016 will default to longer instance and reservation IDs, and can be opted out if necessary.
After you have performed your testing and are satisfied that your tools, code, and applications work to your satisfaction, we recommend that you opt in for all of your AWS accounts before December 2016. This will give you confidence that no surprises will arise when the new identifiers become mandatory." There is more info here: https://aws.amazon.com/ec2/faqs/#longer-ids

It appears on my AWS dashboard that under EC2, I am using only a "default VPC security group" (in Oregon)- I have no idea what that is, and I wasn't even aware that I was "an EC2 customer" as I was called in the email. All I ever access is my JR site Bucket, via my S3 area. I feel clueless... =8-*

Do I need to do anything? Thanks!


--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015
updated by @strumelia: 04/23/16 12:58:23AM

Thanks for the email, as of right now, don't do anything. Reading the email it states that the new id system will start from March 7, 2016, its only Jan 2016 now and we have until Dec 2016 to get it implemented.

If anything needs to be changed, we'll get it changed in the module. I suspect that its just amazon giving you notification because there is no individual signup just for S3, so "just in case" you're using one of the other services that were given as extras when you signed up, they are notifying you.

For now ignore it and if you need to do anything later, we'll let you know.

Thank you!


--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015

This doesn't impact JR in any way - you can ignore it


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net

Great to know- thanks Brian!


--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015