Docker Community Forums

Share and learn in the Docker community.

Nodes state unreachable with current instance ID and Reservation ID using AWS EC2


(Nael Mohammad) #1

Using the Docker cloud from the Nodes, the webui indicates the state of the node is unreachable even though everything is working as expected and up and running, Apparently Amazon is transitioning to a longer format of the instance id and reservation ids. This makes the status unreachable. As a test, I created another node with the same config using GoDaddy, and the status is correct in “Deployed” status.

Below is the snippet:

We’re transitioning instance IDs and reservation IDs to a longer format

AWS is transitioning instance IDs and reservation 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 December 2016 to opt in to the longer format.

If you do not take any action, you will be opted in automatically in December 2016, when all new instance IDs and Reservation 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 transition to longer instance IDs and reservation IDs with Resource ID length management, and read more about the new format.

will try again with another node on AWS to see how things go.

-nael