AMAZON WEB SERVICES FOR MANAGERS

I’m asked frequently about the ins and outs of Amazon Web Services by C-levels, directors and supervisors. They are not looking for nitty gritty nuances of Proxy with all the API of the Elastic Compute Cloud, they are just considering the general summary of how the’cloud’ functions.
When describing AWS for the very first time to supervisors (or anyone, for that matter) it is ideal to talk in concepts instead of in real terms. I’ve also noticed it is beneficial to try to tangiblize the dialogue with familiar terms.

Hierarchical Organization


In a very large level, you can think about EC2 as a global computing environment. Within EC2 are geographical regions which can be considered as data centers.
- EC2 (think: cloud)
—— Regions (believe: data center)
————- Availability Zones (believe: pc cluster)

Virtual Machines


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 snapshot of machine which you can load and run inside the cloud at an Availability Zone. Every time you take an AMI and start it, it is known as an instance of the AMI. You can choose an AMI and begin it several times, every time creates a new case.
Instances are virtual machines which are running, and I really mean they’re virtual. If precautions aren’t taken, these digital machines may wink out of existence and also cause a lot of consternation. So you don’t really want to think of an Instance as a tool that’s strong and persistent. It is only a unit of computational tools.

Virtual Hard Drives


To help keep your data intact even when an Instance expires, you may use many different AWS services but among the more common ones is that the Elastic Block Store, or EBS. Think of EBS as a Hard Disk. You can make an EBS from 1GB to 1TB and’install’ it on any of your digital machine Instances. Consequently, if you have an Instance that’s running your site and you wish to make sure the database stays healthy even when the Instance disappears, you can use an EBS’hard drive’. In the vernacular of AWS, you have created an EBS volume and mounted it on an Instance.
Other Digital Storage
You can find other services that you might have employed besides EBS for holding this imaginary database of yours. For instance, the SimpleDB, or SDB, is a totally reasonable substitute and could be preferred in certain scenarios. But, AWS Cloud Practitioner is a specific service for basic database delivery, whereas EBS is a generalized storage alternative. There’s also that the Relational Database Service, or RDS that provide robust database providers outside SDB. The choice of service is often determined by the needs of this solution.

If we want to secure that data we now have on our EBS volume, we aren’t from the woods yet because even hard drives may fail. We will want to back this up into more secure storage. For this we could use the Simple Storage Solution, or S3 for short. You can think of S3 as a readily available tape backup. It allows you to have up to 100 directories of data in your cassette. Each of these directories is referred to as a bucket from the S3 entire world. Because it is a good stable storage method, you will want to backup your EBS volume(s) into S3 occasionally. And, if you have customized your Instance, you will 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 are able to pull them from your copy in S3 fairly quickly and get ready to go .

Robust Security


Well, all of this would be useless if we did not have good security to be certain our solution has been murdered. Two concepts are employed in AWS for security functions. The first is a set of keys that permits you and your programmers to access your systems. These are public/private important pairs and digital certificates necessary to log into the case. The second, referred to as a security group, can be considered as a firewall setup. You create a security set that defines how outside entities - like internet browsers, or distant backgrounds, or ftp, or email, etc. - can or cannot access your info.