$ aws ssm start-session --target i-XXXXYYYYZZZZ An error occurred (TargetNotConnected) when calling the StartSession operation: i-XXXXYYYYZZZZ is not connected.
After adding the region, the command runs successfully
Issue number:
Closes #
Description of changes:
Testing done:
Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.
Thanks! Let me test this behavior. I think you are correct: it's hard to imagine that the command could work without the region. I appreciate receiving this as a pull request.
Without region, it throws the below error:
$ aws ssm start-session --target i-XXXXYYYYZZZZ An error occurred (TargetNotConnected) when calling the StartSession operation: i-XXXXYYYYZZZZ is not connected.
After adding the region, the command runs successfully
Issue number:
Closes #
Description of changes:
Testing done:
Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.