You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 7, 2022. It is now read-only.
"We're transitioning resource IDs to a longer format.
AWS is transitioning resource IDs to a longer format. The old format is a resource identifier followed by an 8-character string, and the new format is a resource identifier followed by a 17-character string. You have until July 2018 to opt in to the longer format.
If you do not take any action, you will be opted in automatically in July 2018, when all new resource IDs will be created with the longer format. Until the deadline, you can opt in and out of the new format as needed. Only newly created resources receive longer IDs; existing resources are unaffected.
Manage your individual longer ID settings per region in the Advanced Resource ID Management section."
The text was updated successfully, but these errors were encountered:
I think we are using names instead of IDs in tests using 24/7 running instances like cu24x7 and so on. Also when we are creating instances for testing then we use the id that was in returned response.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
"We're transitioning resource IDs to a longer format.
AWS is transitioning resource IDs to a longer format. The old format is a resource identifier followed by an 8-character string, and the new format is a resource identifier followed by a 17-character string. You have until July 2018 to opt in to the longer format.
If you do not take any action, you will be opted in automatically in July 2018, when all new resource IDs will be created with the longer format. Until the deadline, you can opt in and out of the new format as needed. Only newly created resources receive longer IDs; existing resources are unaffected.
Manage your individual longer ID settings per region in the Advanced Resource ID Management section."
The text was updated successfully, but these errors were encountered: