July 2018 ยท 4 minute read

I am asked often about the intricacies of Amazon Web Services by C-levels, directors and supervisors. They aren’t searching for nitty gritty nuances of Proxy with all the API of the Elastic Compute Cloud, they are just considering the general summary of the way the’cloud’ functions.
When explaining AWS for the first time to supervisors (or anyone, for that matter) it is best to speak in theories instead of in concrete terms. I’ve also noticed it is helpful to try to tangiblize the dialogue with recognizable terms. With terms such as”Elastic IP” gets quizical looks, but calling it a publicly accessible IP address helps individuals to get a better overall grasp of theories before using the AWS conditions for things.

Hierarchical Organization

At a very high degree, you can think of EC2 as a global computing environment. Within EC2 are geographic areas that may be considered as data centers. Inside of these data centers are computer clusters which in AWS parlance are called Availability Zones:
- EC2 (think: cloud)
—— Regions (believe: info center)
————- Availability Zones (think: computer 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 that you can load and operate within the cloud at an Availability Zone. Each time you choose an AMI and begin it, it is known as an Instance of the AMI. You can take an AMI and start it many times, each time creates a new Instance.
Instances are virtual machines which are running, and I truly mean they’re virtual. If precautions are not taken, these virtual machines may wink out of existence and lead to a lot of consternation. So you don’t really wish to think about an Instance as something that is robust and persistent. It’s only a unit of computational tools.

Virtual Hard Drives

To keep your data intact even when an Instance expires, you can use several different AWS services but among the more common ones would be that the Elastic Block Store, or EBS. Consider EBS as a Hard Disk. So, in case you experience an Instance that’s running your website and you wish to be certain that the database remains healthy even if the Instance disappears, then you can use an EBS’hard drive’. In the event of AWS, you’ve generated an EBS quantity and mounted it in an case.
Other Virtual Storage
You can find other services you might have employed besides EBS for holding this imaginary database of yours. By way of instance, the SimpleDB, or SDB, is a totally reasonable substitute and could be preferred in certain scenarios. However, SDB is a specific service for fundamental database shipping, whereas EBS is a generalized storage alternative. There is also the Relational Database Service, or RDS that offer robust database providers outside SDB. The choice of service is often dependent upon the requirements of this solution.

If we want to secure that data we now have on our EBS volume, we are not from the woods yet since even hard drives can fail. We will want to back up this into more secure storage. For this we can use the Simple Storage Solution, or S3 for brief. It’s possible to think about S3 as a readily available tape backup. Every one of those directories is called a bucket in the S3 world. Because it’s a good stable storage system, you’ll want to backup your EBS quantity (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. In this manner, 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 .

Robust Security

Well, all this would be worthless if we did not have great security to be certain our solution was hacked. Two theories 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 important pairs and digital certificates necessary to securely log in the case. Google Cloud , called a security group, can be thought of as a firewall setup. You create a security group that defines how external entities - such as web browsers, or remote desktops, or ftp, or email, etc. - can or cannot access your Instance.