This is a small set of commands that I made to help me work with AWS more productively. Feel free to submit your own pull requests and add to it!
Right now, the main functionality is to start and stop aws instances quickly via the command line while you're developing. I know sometimes I want a dev machine that's more powerful than my current computer, so but I only want it for a bit. These commands allow you to easily start and stop large instances.
When setting up, bear in mind that when working with AWS, the region matters, and you might not see the right information if the AWS console is using a different region. The links provided should take you to your default region, but that may not be right.
- Install the AWS CLI
- Install jq
- Create an EC2 instance if you don't already have one
- Save your SSH Key as key.pem in the
aws-tools/directory - Run
chmod 600 key.pem - Register your instance-id in
instances.json - Create a user via AWS's IAM and configure AWS CLI with
aws configure
One file of interest is instances.json, which is to be put in the same directory as the rest of these tools.
instances.json is a simple key/value dictionary where you should have "nickname": "instance-id".
You make the nickname and use it in the various commands.
See instances.json.example.
By running awscron, you'll add an entry to your cronfile that will automatically shut down the server after 1 hour of no use.
It checks every minute, so if you don't log in immediately, it is likely that your instance will shut down before you can log in.
See #1 for details.
The most useful command is sshaws to be used like follows sshaws myt2large.
It will automatically look up the ip address of your instance and connect to it.
awsdns is also an interesting command. You run it like awsdns myt2large.
Right now, I have it set to modify my personal DNS server.
I do this because once I have the DNS set, I can access it via ec2-user@myt2large.aws.benthayer.com and use VSCode to remote edit the files without having to change the settings every time.
To use this command, you'll need a .dns_env file in your home directory.
awsdns has only been tested with my personal mail-in-a-box server.
If you'd like to update it, look at issue #2
I'd appreciate any contributions. I made this because it was useful for me. Hopefully, it can be useful for more people!