Many of you may have heard about Amazon’s latest product named Lightsail. This service is designed to competed with shared hosting providers. A few years back I moved my websites from shared hosting, to self hosing, and ultimately to a dedicated server with 1&1 hostsing. For $85 a month it wasn’t a bad deal. Although the server seemed very sluggish at times and the network wasn’t very fast it was still better than shared hosting.
Over the course of the last two weeks I moved all my web assets to Amazon Lightsail and I couldn’t be happier. The Amazon network is lightening fast and the $5 per month instance is out performing the dedicated server I had from 1&1 hosting. Lightsail offers many plans starting at $5 a month all the way to $80 a month.
I’m sure you have all heard the news about the VMware and Amazon partnership. I’ve been getting loads of questions from people and it seems that their are misconceptions on what exactly this means short term. Here is some of what I have heard and some clarification as to what it really is.
The offering will be VMware’s hypervisor running nested on top of AWS. – False
The offering is actually the vSphere hypervisor running on bear metal running inside Amazon’s data center.
I want AWS features, not just vSphere in another datacenter. I don’t see any AWS value or features with this offering – False
The machines running on vSphere in the AWS datacenter can take advantage of lots of AWS offerings such as storage, database offerings, security, analytics, and from what I understand 70 other services. While it’s not the ability to use the AWS API to provision workloads this is still huge. This of projects you may have that utilize AWS services interacting with workloads running in your own physical data center and the what you have to do you secure those interactions. Now you have the ability to run the workloads inside the same data center as those services greatly reducing the complexities of securing those communications.
It’s great but what about NSX?
In the offering vSphere, NSX, and vSAN are all available. I can’t speak to how the cost and licensing works with regards to these, but they are all available.
When will this be generally available?
It is expected to be available sometime late H2 2017.
As more and more info becomes available it will become even more apparent how much value this will add to the enterprise datacenter. Most organizations today have a disconnect when it comes to their on-prem and off-prem workloads. Having a standardizes infrastructure, standardized process, and standardized integrations can only lead to less complex and more manageable infrastructure. As more information becomes available that can be shared I will certainly be focusing more on this area and once possible I will certainly be providing some insight and sneak peaks into this great new partnership.
Creating an Amazon AWS Endpoint is really just assigning the credentials you would like to use to communicate with Amazon. vCAC already knows how to communicate with Amazon, it just doesn’t know what it needs to authenticate. To create the AWS Enpoint perform the following steps:
Creating an Amazon AWS credential has a few extra steps then a general set of credentials. You will need to login to your AWS account and access your Acess Key Id as well as your Secret Access Key to be utilized in the creation. The steps below outline the process to create an Amazon AWS set of credentials.
Usually most people go straight for connecting vCAC to vCenter, but I have decided to connect to Amazon EC2 first. I’m doing this for a few reasons, but mainly because anyone reading this has access to EC2. All you really need is any computer with a Desktop Virtualization tool like VMware workstation and you can test vCAC with Amazon EC2. If you don’t have an Amazon AWWS account go to http://aws.amazon.com and sign-up.
Signing up for Amazon AWS is free and what’s even better is you can also provision “Micro.Instances” for free for an entire year as long as you stay within these guidelines. The basics are this:
750 Hours of Linux/Windows Micro Instance Usage per month. (613Mb Memory). This is enough to run a single micro instance for the whole month.
750 Hours of Elastic Load Balancing plus 15GB of data processing
30GB of Elastic Block Storage
5GB of S3 Storage with 20,000 Get requests and 2,000 Put requests
And some other goodies…..
You can run more than one micro instance at a time as long as the consecutive run time of your machines doesn’t go over 750 hours a month. Once you provision an instance it automatically counts as 15 minutes used. I don’t bother trying to calculate by the 15 minutes so the way I look at it is I can perform 750 provisioning tests per month if each test is less than an hour.