AMAZON WEB SERVICES FOR MANAGERS

July 19, 2018

AWS Certifications am asked often about the ins and outs of Amazon Web Services by C-levels, directors and managers. They aren’t looking for nitty gritty nuances of scripting with all the API of their Elastic Compute Cloud, they are just considering the general overview of the way the’cloud’ works.
When describing AWS for the first time to supervisors (or anybody, for that matter) it is ideal to talk in theories instead of in concrete terms. I’ve also noticed it’s helpful to try and tangiblize the dialogue with recognizable terms.

Hierarchical Organization


At a really high degree, you can think of EC2 as a global computing environment. Within EC2 are geographical areas that may be thought of as data centers.
- EC2 (think: cloud)
—— Regions (believe: data center)
————- Availability Zones (think: pc cluster)

Inside of an Availability Zone, we have can create virtual machines from predefined or custom Amazon Machine Images, or AMIs. An AMI can be considered as a photo of machine that you can load and run inside the cloud at an Availability Zone. Each time you choose an AMI and start it, it is called an instance of the AMI. You are able to choose an AMI and start it many times, each time creates a new case.
Instances are virtual machines which are running, and I really mean they’re virtual. If precautions are not taken, these digital machines may wink out of existence and also lead to a great deal of consternation. So you don’t really want to think of an Instance as a tool that is strong and persistent. It’s only a unit of computational resources.

To help keep your data intact even when an Instance expires, you may use several different AWS services but one of the very common ones would be the Elastic Block Store, or EBS. Consider EBS as a hard drive. It’s possible to make an EBS from 1GB to 1TB and’install’ it on any of your digital machine Instances. Consequently, in case you experience an Instance that is running your site and you want to be sure the database remains healthy even if the Instance disappears, then you can use an EBS’hard drive’. At the event of AWS, you have created an EBS quantity and mounted it in an Instance.
Other Virtual Storage
You can find other services that you might have used besides EBS for carrying this fantastic database of yours. By way of instance, the SimpleDB, or SDB, is a totally reasonable substitute and could be favored in certain scenarios. But, SDB is a specific service for basic database shipping, whereas EBS is a generalized storage solution. There’s also the Relational Database Service, or RDS that provide robust database providers outside SDB. The alternative of service is often determined by the needs of the solution.

Virtual Backup


If we want to secure that information we have on our EBS quantity, we aren’t from the woods yet because hard drives can fail. We’ll want to back up this into more secure storage. For this we could use the very simple Storage Option, or S3 for brief. You can think of S3 as a readily accessible tape backup. It permits you to have up to 100 directories of data on your tape. Each of these directories is called a bucket in the S3 entire world. Because it’s a fantastic stable storage system, you’ll want to backup your EBS volume(s) to S3 occasionally. And, when you have personalized your Instance, you are going to want to save a new picture of it in S3 also. This way, if your attentively customized Instance or EBS volume crashes for any reason, you can pull them from your backup in S3 fairly quickly and get ready to go again.

Robust Security


Well, all this would be worthless if we didn’t have good security to be certain our solution was murdered. Two concepts are used in AWS for security purposes. The first is a set of keys which allows you and your developers to access your systems. These are public/private key pairs and digital certificates necessary to log into the case. The second, referred to as a security group, can be thought of as a firewall configuration. You make a security set that defines how external entities - such as internet browsers, or distant backgrounds, or ftp, or email, etc. - can or cannot access your info.