Amazon Web Services For Managers

July 19, 2018

I am asked frequently about the ins and outs of Amazon Web Services by C-levels, directors and managers. They are not searching for nitty gritty nuances of Proxy with all the API of their Elastic Compute Cloudthey are just interested in the general summary of how the’cloud’ works.
When describing AWS for the first time to managers (or anyone, for that matter) it is ideal to talk in theories instead of in real terms. I’ve also noticed it is helpful to attempt to tangiblize the discussion with recognizable terms.

Hierarchical Organization

At a really high degree, you can think about EC2 as a global computing environment. Within EC2 are geographic areas which may be considered as information centers. Inside of those data centers are computer clusters which in AWS parlance are called Availability Zones:
- EC2 (believe: cloud)
—— Regions (think: info centre )
————- Availability Zones (think: pc cluster)

Virtual Machines

Within an Availability Zone, we have can create virtual machines from custom or predefined Amazon Machine Images, or AMIs. An AMI can be considered as a snapshot of machine that you may load and run inside the cloud at an Availability Zone. Each time you choose an AMI and begin it, it’s known as an instance of the AMI. You can choose an AMI and start it many times, every time creates a new case.
Instances are virtual machines that are running, and I really mean they are virtual. If precautions aren’t taken, these virtual machines may wink out of existence and also cause a great deal of consternation. So that you do not really wish to think of an Instance as a tool that’s robust and persistent. It is merely a component of computational resources.

Virtual Hard Drives

To help keep your information intact even when an Instance dies, you may use many different AWS providers but among the very common ones would be that the Elastic Block Store, or EBS. Consider EBS as a hard drive. You can earn an EBS from 1GB to 1TB and’install’ it on some of your virtual machine Instances. So, in case you experience an Instance that is running your website and you wish to make certain that the database remains healthy even if the Instance disappears, you can use an EBS’hard drive’. At the event of AWS , you’ve created an EBS quantity and mounted it in an case.
Other Digital Storage
There are other services you could have used besides EBS for carrying this imaginary database of yours. For example, the SimpleDB, or SDB, is a totally reasonable substitute and would be preferred in certain situations. However, SDB is a particular support for basic database delivery, whereas EBS is a generalized storage solution. There’s also that the Relational Database Service, or RDS that offer robust database providers outside SDB. The choice of service is frequently dependent upon the requirements of the solution.

Virtual Backup

If we want to secure that data we now have on our EBS volume, we aren’t out of the woods yet since even hard drives may fail. We will want to back up this into more stable storage. For this we can use the very simple Storage Solution, or S3 for brief. You can think of S3 as a readily available tape backup. Each of those directories is called a bucket from the S3 world. As it’s a good stable storage method, you’ll want to backup your EBS volume(s) to S3 occasionally. And, if you have customized your Instance, you will want to save a new picture of it in S3 also. In this manner, if your carefully customized Instance or EBS volume crashes for any reason, you can pull them out of your copy in S3 fairly quickly and get ready to go again.

Robust Security

Well, all of this would be worthless if we did not have good security to be certain that our solution was hacked. Two concepts are used in AWS for safety functions. The first is a set of keys which allows you and your programmers to access your systems. These are public/private key pairs and digital certificates necessary to log in the case. The second, referred to as a security set, can be considered as a firewall setup. You create a security set that defines how external entities - like internet browsers, or distant backgrounds, or ftp, or email, etc. - can or cannot access your info.