Amazon Web Services For Managers

July 19, 2018

I’m asked frequently about the ins and outs of Amazon Web Services by C-levels, directors and managers. They are not looking for nitty gritty nuances of scripting with all the API of their Elastic Compute Cloud, they are only considering the general summary of the way the’cloud’ works.
When explaining AWS for the first time to supervisors (or anyone, for that matter) it is best to talk in concepts instead of in concrete terms. I’ve also noticed it is beneficial to try to tangiblize the dialogue with familiar terms. With phrases such as”Elastic IP” gets quizical looks, but calling it a publicly accessible IP address helps individuals to get a better overall grasp of concepts before using the AWS conditions for things.

Hierarchical Organization


At a really large degree, you can think of EC2 as a global computing environment. Within EC2 are geographical regions that may be considered as information centers.
- EC2 (believe: cloud)
—— Regions (think: info centre )
————- Availability Zones (believe: pc cluster)

Within an Availability Zonewe have can make virtual machines from custom or predefined Amazon Machine Images, or AMIs. An AMI can be thought of as a snapshot of machine which you may load and run inside the cloud at an Availability Zone. Each time you take an AMI and begin it, it is called an instance of the AMI. You are able to take an AMI and start it several times, each time creates a new Instance.
Instances are virtual machines that are running, and I truly mean they are virtual. If precautions aren’t taken, these digital machines may wink out of existence and cause a lot of consternation. So that you do not really wish to think of an Instance as a tool that is robust and persistent. It is merely a unit of computational tools.

Virtual Hard Drives


To keep your data intact even when an Instance expires, you may use many different AWS providers but one of the very common ones is the Elastic Block Store, or EBS. Consider EBS as a Hard Disk. Consequently, in case you experience an Instance that’s running your site and you want to be certain the database remains healthy even when the Instance disappears, then you can use an EBS’hard drive’. At the event of AWS, you have created an EBS volume and mounted it on an Instance.
Other Digital Storage
There are other services you could have used besides EBS for carrying this fantastic database of yours. For instance, the SimpleDB, or SDB, is a perfectly reasonable substitute and would be favored in certain scenarios. However, SDB is a particular service for basic database shipping, whereas EBS is a generalized storage solution. There’s also that the Relational Database Service, or RDS that provide robust database services beyond SDB. The choice of service is frequently dependent upon the requirements of this solution.

Virtual Backup


If we would like to secure that data we have on our EBS volume, we are not from the woods yet because 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 Option, or S3 for brief. It’s possible to think of S3 as a readily accessible tape backup. It permits you to have up to 100 directories of information in your cassette. Every one of these directories is called a bucket in the S3 world. As it’s a good stable storage method, you’ll want to backup your EBS quantity (s) to S3 occasionally. And, if you’ve personalized 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 out of your backup in S3 rather quickly and get up and running again.

Robust Security


Well, all of this would be useless if we did not have good security to be certain that our solution has been hacked. Two theories are used in AWS for security functions. The first is a set of keys which permits you and your developers to gain access to your systems. Microsoft Azure are public/private key pairs and digital certificates required to securely log into 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 web browsers, or remote desktops, or ftp, or email, etc. - can or cannot access your Instance.