I am asked frequently about the intricacies of Amazon Web Services by C-levels, directors and supervisors. They are not searching for nitty gritty nuances of Proxy with the API of the Elastic Compute Cloud, they are only considering the general overview of how the’cloud’ works.
When describing AWS for the first time to supervisors (or anybody, for that matter) it is ideal to speak in theories rather than in real terms. I have also noticed it’s beneficial to try and tangiblize the dialogue with familiar terms. With phrases such as”Elastic IP” gets quizical looks, but calling it a publicly available IP address helps people to acquire a better overall grasp of concepts before using the AWS terms for things.

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

Inside of an Availability Zone, we have can make virtual machines from custom or predefined Amazon Machine Images, or AMIs. An AMI is considered as a snapshot of machine which you can load and operate within the cloud with an Availability Zone. Every time you take an AMI and begin 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 truly mean they’re virtual. If precautions aren’t taken, these virtual machines may wink out of existence and lead to a great deal of consternation. So that you don’t really want to think of an Instance as a tool that’s robust and persistent. It’s only a unit of computational tools.

To help keep your data intact even when an Instance expires, you can use several 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 make an EBS from 1GB to 1TB and’install’ it on some of your virtual machine Instances. So, if you experience an Instance that’s running your site and you wish to be sure that the database stays healthy even if the Instance disappears, then you may use an EBS’hard disk’. In the vernacular of AWS, you’ve created an EBS quantity and mounted it on an case.
Other Digital Storage
There are other services that you might have used 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 particular support for basic database delivery, whereas EBS is a generalized storage alternative. There is also the Relational Database Service, or RDS that provide robust database services 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 quantity, we are not from the woods yet since hard drives can fail. We’ll want to back up this into more secure storage. For this we can use the Simple Storage Option, or S3 for brief. You can think about S3 as a readily available tape backup. It permits you to have up to 100 directories of data on your tape. Each of those directories is referred to as a bucket in the S3 entire world. As it’s a fantastic stable storage method, you will want to backup your EBS quantity (s) into S3 occasionally. And, if you’ve personalized 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 from your copy in S3 fairly quickly and get ready to go again.

Robust Security

Well, all this would be useless if we did not have great security to make sure our solution was murdered. Two theories are employed in AWS for safety functions. The first is a pair of keys that permits you and your programmers to access your systems. These are public/private important pairs and digital certificates required to securely log in the Instance. The second, referred to as a security set, can be thought of as a firewall configuration. You create a security group that defines how outside entities - such as internet browsers, or distant backgrounds, or ftp, or email, etc. - can or cannot access your info.