AWS Man

If you’ve been to any cloud conference, browsed around ‘cloud twitter’ a bit or are in the process of starting your cloud journey, it’s a sure guarantee you’ve heard about serverless by now. Is it just a buzzword, or is serverless something you can really start to get your hands dirty with and benefit from?  Accessing compute power became much easier when “the cloud” entered the market. Now, rather than waiting for bare metal servers to arrive, installing them into racks, and cabling during installation, you can set up your servers with only a few clicks on the web console. Yet although provisioning today’s servers takes only minutes, you still need to prepare and maintain them by patching, installing necessary packages, and setting up environment variables. This takes time. So how do you remove this overhead? You go  serverless! In the first article of this three-part series, we discuss the serverless basics: what it is, where it came from, why you would want to use it and how to

EC2 is a wildly popular AWS service and is bound to be one you either have a lot of experience with or will at some point. One of the most basic tasks you can perform in EC2 is provisioning new instances. Deploying EC2 instances is fairly straightforward if using the management console. The management console walks you through all of the dependencies that an EC2 instance requires. However, all of those dependencies are up to you to set up and define yourself if you’re setting up some automation script. In that case, you need to become familiar with not only setting up the EC2 instance itself but also all of the other resources that an EC2 instance depends on like a VPC, optional internet gateway, a route table, route, AMI image, route table, and a few more. By understanding now just how to deploy an EC2 instance but also understanding everything else required will allow you to create a much smarter automation script. In this article, we’re going to cover how to provision many co