AWS CLI

I was playing around with Amazon Web Services this weekend since I caught wind that ITS Vmhosting is going to provide some sort of service that is tied to it. Also bto was interested in building some "thing" that I had sort of conceptually already started in my mind. :) Now through somewhat cryptic and barely understandable slack conversations we are ready to start putting code in version control. 

Basically the stage we are at now is building scaffolding for the ability to stand up and tear down Amazon EC2 instances without the user even knowing that that's whay they are doing. They will click "build me stuff" and the AWS CLI automation scripts (yet to be built) will handle the rest. To get to the scripting/automation stage, there is a good bit of ramping up that needs to take place. For one, there will need to be some knowlege of the suite of AWS products that will be "useable." Some examples are EC2, RDS, S3, and IAM. The model is vastly different than what we are used to in the sense that there are a plethora of ways in which to couple/bundle the services. 

For now I am getting to know the AWS command line interface and how I can use it's API to automate tasks that someone without technical skills would not want to do.

The video in this post gives a scratched surface look at what you can do with AWS CLI. Next we will begin working on a plan as to how to use this amazing toolset to further the development of the spawn project.

For AWS CLI Reference, click here.