Logging in to a Failed Instance - AWS OpsWorks

Logging in to a Failed Instance


AWS OpsWorks Stacks is no longer accepting new customers. Existing customers will be able to use the OpsWorks console, API, CLI, and CloudFormation resources as normal until May 26, 2024, at which time they will be discontinued. To prepare for this transition, we recommend you transition your stacks to AWS Systems Manager as soon as possible. For more information, see AWS OpsWorks Stacks End of Life FAQs and Migrating your AWS OpsWorks Stacks applications to AWS Systems Manager Application Manager.

If a recipe fails, the instance will end up in the setup_failed state instead of online. Even though the instance is not online as far as AWS OpsWorks Stacks is concerned, the EC2 instance is running and it's often useful to log in to troubleshoot the issue. For example, you can check whether an application or custom cookbook is correctly installed. The AWS OpsWorks Stacks built-in support for SSH and RDP login is available only for instances in the online state. However, if you have assigned an SSH key pair to the instance, you can still log in, as follows:

  • Linux instances – Use the SSH key pair's private key to log in with a third-party SSH client, such as OpenSSH or PuTTY.

    You can use an EC2 key pair or your personal SSH key pair for this purpose.

  • Windows instances – Use the EC2 key pair's private key to retrieve the instance's Administrator password.

    Use that password to log in with your preferred RDP Client. For more information, see Logging in As Administrator. You cannot use a personal SSH key pair to retrieve an Administrator password.