Today, I was doing some experiments on EC2 instances. While doing the experiment I faced one issue: launch failure. It is like launching template failed, to debug this and to know about what is this error, I went through AWS troubleshooting documentation and in that document it was mentioned about trying out
describe-instance-type-offerings command to see what instance types are offering. I was not using my personal machine where my AWS account or credentials are configured. I was thinking what should I do now ? 🤔🤔
Then I saw a symbol on top navigation of AWS UI about launching an online AWS cloud console UI. Wow, it's superb... Now I no need worry about accessing AWS CLI even if I am not in front of my personal device. If I can access my AWS account from a browser then I can access AWS CLI.
Interesting facts about AWS CloudShell is it was launched around Dec 2020 but I got to know now. Somebody said "Problem come with solution and solution come with learning"
Let me walkthrough about AWS CloudShell. This is how its looks a like 👇🏻
- No extra credentials to manage
- No cost ( 😅😅 ) - There is no additional charge for AWS CloudShell.
- Automatically manage your credentials
- Familiar tools ( Similar like our Windows or Linux or Mac terminal 👍🏻)
- 1 GB of persistent storage ( storage enables you to store your frequently used scripts/commands and configuration files between AWS CloudShell sessions)
- Row layout
- Column layout
- Font size
- Light or Dark mode
- Enabling safe paste ( This can ask for permission before pasting command or text)
- Each CloudShell session will timeout after 20 minutes or so of inactivity, and can be reestablished by refreshing the window. You will see something like this error 👇🏻
- AWS CloudShell is available today only in the
eu-central-1Regions. Other region support on road map.
- AWS CloudShell supports Python and Node runtimes, Bash, PowerShell, jq, git, the ECS CLI, the SAM CLI, npm, and pip.
- Concurrent 10 tabs you can open in each region.
- Default output of
[cloudshell-user@ip-10-1-94-160 ~]$ pwd /home/cloudshell-user [cloudshell-user@ip-10-1-94-160 ~]$
- You can download files from the terminal or upload files to the terminal.
- CloudShell home directory ($HOME) and files, scripts, and tools saved in $HOME will persist between sessions
Thanks to AWS services for providing such good tools. Hope you like my blog about AWS CloudShell. If you like my blog please don't forget to like the article, It will encourage me to write more such AWS Cloud related articles. You can reach out to me over my twitter handle @aviboy2006