Amazon Web Services For Managers
I am asked often 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 just considering the general overview of how the'cloud' works.
When describing AWS for the first time to managers (or anybody, for that matter) it is best to speak in theories instead of in concrete terms. I have also noticed it is beneficial to try and tangiblize the discussion with recognizable terms.
In a very large level, you can think of EC2 as a global computing environment. Within EC2 are geographic areas that may be considered as data 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 (believe: computer cluster)
Within an Availability Zonewe have can make virtual machines from predefined or custom Amazon Machine Images, or AMIs. An AMI is thought of as a photo of machine which you may load and run inside the cloud at an Availability Zone. Every time you choose an AMI and begin it, it's called an Instance of the AMI. You can choose an AMI and begin it many times, every time creates a new case.
Instances are virtual machines that are running, and I truly mean they're virtual. If precautions are not taken, these virtual machines can wink out of existence and also cause a great deal of consternation. So you do not really wish 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 keep your data intact even if an Instance expires, you may use many different AWS services but among the very common ones would be the Elastic Block Store, or EBS. Consider EBS as a Hard Disk. It's possible to earn an EBS from 1GB to 1TB and'install' it on any of your digital machine Instances. So, if you have an Instance that is running your site and you want to be sure the database stays healthy even when the Instance disappears, then you may use an EBS'hard drive'. At the vernacular of AWS, you've generated an EBS volume and mounted it in an Instance.
AWS Advanced Networking can find other services that you could have employed besides EBS for carrying this fantastic database of yours. By way of example, the SimpleDB, or SDB, is a totally reasonable substitute and would be favored in certain scenarios. But, 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 provide robust database providers outside SDB. The choice of service is frequently dependent upon the needs of this solution.
If we would like to secure that information we have on our EBS quantity, we are not out of the woods yet because hard drives may fail. We will want to back this up into more stable storage. For this we can use the very simple Storage Solution, or S3 for brief. You can think about S3 as a readily accessible tape backup. It allows you to have up to 100 directories of data on your cassette. Each of those directories is called a bucket in the S3 world. As it's a fantastic stable storage method, you will want to backup your EBS quantity (s) into S3 periodically. And, if you've customized your Instance, you will want to save a new image of it in S3 also. In this manner, if your attentively customized Instance or EBS volume crashes for any reason, you can pull them out of your copy in S3 rather quickly and get up and running .
Well, all of this would be useless if we didn't have great security to be certain our solution was murdered. Two theories are employed in AWS for security functions. The first is a pair of keys which permits you and your developers to gain access to your systems. These are public/private key pairs and digital certificates required to log into the case. The second, referred to as a security group, can be thought of as a firewall setup. You make a security set that defines how external entities - such as internet browsers, or remote desktops, or ftp, or email, etc. - can or cannot access your Instance.
When describing AWS for the first time to managers (or anybody, for that matter) it is best to speak in theories instead of in concrete terms. I have also noticed it is beneficial to try and tangiblize the discussion with recognizable terms.
In a very large level, you can think of EC2 as a global computing environment. Within EC2 are geographic areas that may be considered as data 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 (believe: computer cluster)
Within an Availability Zonewe have can make virtual machines from predefined or custom Amazon Machine Images, or AMIs. An AMI is thought of as a photo of machine which you may load and run inside the cloud at an Availability Zone. Every time you choose an AMI and begin it, it's called an Instance of the AMI. You can choose an AMI and begin it many times, every time creates a new case.
Instances are virtual machines that are running, and I truly mean they're virtual. If precautions are not taken, these virtual machines can wink out of existence and also cause a great deal of consternation. So you do not really wish 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 keep your data intact even if an Instance expires, you may use many different AWS services but among the very common ones would be the Elastic Block Store, or EBS. Consider EBS as a Hard Disk. It's possible to earn an EBS from 1GB to 1TB and'install' it on any of your digital machine Instances. So, if you have an Instance that is running your site and you want to be sure the database stays healthy even when the Instance disappears, then you may use an EBS'hard drive'. At the vernacular of AWS, you've generated an EBS volume and mounted it in an Instance.
AWS Advanced Networking can find other services that you could have employed besides EBS for carrying this fantastic database of yours. By way of example, the SimpleDB, or SDB, is a totally reasonable substitute and would be favored in certain scenarios. But, 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 provide robust database providers outside SDB. The choice of service is frequently dependent upon the needs of this solution.
If we would like to secure that information we have on our EBS quantity, we are not out of the woods yet because hard drives may fail. We will want to back this up into more stable storage. For this we can use the very simple Storage Solution, or S3 for brief. You can think about S3 as a readily accessible tape backup. It allows you to have up to 100 directories of data on your cassette. Each of those directories is called a bucket in the S3 world. As it's a fantastic stable storage method, you will want to backup your EBS quantity (s) into S3 periodically. And, if you've customized your Instance, you will want to save a new image of it in S3 also. In this manner, if your attentively customized Instance or EBS volume crashes for any reason, you can pull them out of your copy in S3 rather quickly and get up and running .
Well, all of this would be useless if we didn't have great security to be certain our solution was murdered. Two theories are employed in AWS for security functions. The first is a pair of keys which permits you and your developers to gain access to your systems. These are public/private key pairs and digital certificates required to log into the case. The second, referred to as a security group, can be thought of as a firewall setup. You make a security set that defines how external entities - such as internet browsers, or remote desktops, or ftp, or email, etc. - can or cannot access your Instance.
Replies