Getting started with AWS is very simple. Follow the walk-through (Linux | Windows) in our documentation to get a clear information regarding it.
Amazon Web Services (AWS) provides on-demand computing resources and services in the cloud, with pay-as-you-go pricing. For example, you can run a server on AWS that you can log on to, configure, secure, and run just as you would do with a server that’s sitting in front of you. In under 20 minutes, you can be up and running with Amazon Web Services (AWS) using your platform of choice. Each of the following platforms provides sample code to get you started utilizing AWS as fast as possible.
Let us suppose you want to deploy Drupal, an open-source content management system (CMS). It’s easy to get started, and for most of the tasks we can use the AWS Management Console. In this post, we’ll walk through a series of steps to deploy your web application to AWS. There are many different ways you can go while deploying your web application. The approach that this walk-through takes, follows best practices and uses several of the core services so you can see how they work together.
Before you begin deploying Drupal using AWS, you’ll need to sign up for an AWS account and install the Auto Scaling command line tools. Signing up for AWS gives you access to all of the services; however, you are charged only for what you use.
First, you’ll find a suitable AMI that meets your hardware and software needs. You’ll use this AMI to launch an Amazon EC2 instance. When launching your Amazon EC2 instance, you’ll create a new key pair and a security group. The security group sets the rules for who can access the Amazon EC2 instance, and the key pair is necessary for connecting to your Amazon EC2 instance.
With your instance running and secured, you will finish installing the required software and then configure the Drupal application. To simplify launching new Amazon EC2 instances that are already configured, you’ll create a custom AMI that will become your new baseline.
You’ll then create an Elastic Load Balancer to distribute the traffic load across multiple instances and then update your security group to allow HTTP traffic from only your load balancer instead of from everyone. You create your elastic load Balancer before you launch your instances, so that you can associate your Auto Scaling group with your Elastic Load Balancer. That way, your load balancer can automatically stop routing traffic to any terminated instances, and it can start routing traffic to any newly launched instances.
At this point, you’ll use Auto Scaling to launch your Amazon EC2 instances. You’ll create an Auto Scaling policy that tells Auto Scaling about when to increment or decrement the number of instances in your group.
Finally, you’ll create a CloudWatch alarm that monitors the instances in your Auto Scaling group and tells the Auto Scaling group when to take action on that policy.
Because this is a sample deployment, you may want to terminate all the AWS resources that you have created. As soon as you terminate an AWS resource, you stop accruing charges for that resource.
|AWS Certified SysOps Administrator||AWS Certified Solutions Architect / Professional|
|AWS Certified Developer||AWS Certified DevOps Engineer|
|AWS Technical Essentials||AWS Database Migration Service|
|AWS Lambda 2016||and many more...|
Get Updates on Tech posts, Interview & Certification questions and training schedules