Tonight I want to connect to an EC2 instance that resides in a private subnet. I currently don’t have a bastion host I can use as an intermediary to jump to this instance. Well, as you might have guessed from this post’s title, the AWS Session Manager is something that might be helpful in this case. So, join me in this journey to configure and set up the Session Manager, using AWS CLI only....
I kept forgetting about the AWS CLI which is quite handy to quickly check if SSM is working on an EC2 instance. So here it is again for my future-self. Use get-connection-status to return the connection status of the specified managed instance. $ aws ssm get-connection-status --target i-092af3b3c1234567 { "Status": "connected", "Target": "i-092af3b3c1234567" } Reference: get-connection-status
Debian publishes their releases of Amazon Machine Image (AMI) for bookworm at Debian bookworm on Amazon EC2 [1]. There, you can find the AMIs for various regions and two architecture amd64 and arm64. Another way to search for AMI for Debian 12 (bookworm) is to use AWS CLI with describe-images. Here is an example on how to list the 3 most recent AMIs of Debian 12 (amd64 architecture), sorted by most recent to the oldest:...