Introduction to VMware Cloud on AWS

Rick Crisci
A free video tutorial from Rick Crisci
VMware Certified Instructor, Virtualization Consultant
4.5 instructor rating • 33 courses • 130,527 students

Learn more from the full course

Introduction to VMware Cloud on AWS

Learn VMware Cloud on AWS! No AWS knowledge necessary to get started!

04:42:18 of on-demand video • Updated July 2019

  • Understand VMware Cloud on AWS
  • Create a Software Defined Datacenter in VMware Cloud on AWS
  • Understand Network and Storage concepts
  • Create an AWS Account and set up a VPC
English [Auto] In this video I'll provide an introduction to V.M. where cloud on AWOS. So let's start with this concept of public private and a hybrid deployment. So many of you are probably familiar with the traditional on premise data center. This is an environment in which you've got your own physical servers you've got your own storage systems and networking systems and everything is physically located on premise and your own data center. And then of course we've got the cloud model as well. Here we see the AWOS cloud and this is a partner environment where you have a service provider such as AWOS that is providing all of the physical servers all of the storage capacity all of the networking between those components and in a variety of other functions. Right. Physical security electricity they're providing all of that stuff has that cloud solution. And then we've got the hybrid data center model and that is one that via VMWare cloud on AWOS is particularly well suited for a hybrid environment is when we're going to maintain our on premise data center. That's not going away so we're still going to have things like ESX I hosted and a V Center instance running in this on premise data center. Those things still need to work and they need to be able to communicate with our resources that are in the AWOS cloud. So we can set up a VPN we can use a W-S direct connect. We've got a few different options of how we can make this work. But this is really a great way to support that hybrid cloud solution is to use VM more cloud on a W-S. It's also a great way to eventually transition to more native resources on AWOS because the AWOS environment and the Villamor cloud on the environment are very tightly integrated. So we have a lot of great options there. But those are three terms that you really need to understand right. Private cloud that's our on premise data center that is virtualizing public cloud is a service provided by a third party such as AWOS and hybrid is when we have a little bit of each. OK so what is the on where a cloud on a W-S. Well it's a it's a way that you can run your familiar VM Ware infrastructure inside of the AWOS cloud. You can use the HVM L5 client to access the center and modify your VM where inventory the way that you're accustomed to doing. So you really get the best of both worlds where you get all the VM Ware tools and architectures that you already know. You get everything from VM or Cloud Foundation sand and assets and VSD for but on top of that you get access to many AWOS services and you also get tight integration with another AWOS account if you want a traditional and obvious account so that you can launch services within AWOS and again tightly integrate those services with the things running on your VM more cloud on NWS and even your on premise services as well. So the VMware cloud and AWOS is powered by Cloud Foundation. We have the sphere. We have assets we have VCM we have vse and all of the familiar VM Ware tools and functionalities that we've grown accustomed to and that provide so many awesome services high availability and depress those features are all supported in the VM or cloud on AWOS. So one of the first steps towards creating a VM more cloud on AWOS deployment is to set up VM or cloud software defined datacenter. Camp Now this account is specifically V.M. where only right here via our cloud on AWOS deployment is going to be strictly managed by only the network as a VM Ware account. And this is where you'll set up the software defined datacenter resources for a single customer. You will also need an AWOS customer account. This is just a regular old AWOS account. It can be connected to your VM or cloud privately. And it offers the full catalog of AWOS services which is an exhaustive catalog of services and many many services available. From a purchasing and billing perspective you can contact VMO to sign up at the moment the moment being October 1st 2017. They're actually not accepting any new clients because there are so much demand for the VM caught on AWOS. But I expect that to change very soon as they continue spinning up this service in New regions. You will get a single bill for the VM ware software and the AWOS resources required to run it. Now this is a bill for your via VMWare cloud on a W-S account. You can still have an AWOS account with AWOS native resources and features. That's a completely separate account. So the armoires going to bill you for as all of their software running on top of the AWOS physical resources. But if you're running things like are yes or easy two instances or S-3 or stuff like that that's going to be a separate account separate from that that will be from AWOS. Now one of the things that I've heard there's a lot of confusion about is how do we actually go about purchasing them our current. Well you've got some options that are going to be actually pretty familiar to you if you've worked with AWOS in the past. So you can purchase hourly On-Demand resources which basically means you're going to choose the number of hosts that you want in your cluster and you're going to pay for them per hour and you only pay for the hours that you're actually running those resources. Now of course this is the most expensive option right because you're not really guaranteeing VM where any continuous revenue you can turn it on and off whenever you want they're going to charge you the most per hour. If you know hey I'm going to need for houses all year long or I'm going to need six hosts all year long you can enter into a reserved model of purchasing over the course of a year or up to three years. And by committing to that long term purchase of resources they'll actually charge you up to 50 percent less so significant savings if you know you can commit the long term purchase of these resources. And you can select from anywhere between 4 and 16 total hosts provided in your Villamor cloud on a W-S software defined datacenter. Okay. Another way to make this purchase a little bit more economically friendly let's say is something called the hybrid loyalty program. So when you look at the pricing you may think hey this is pretty expensive especially if you've already invested in on premise licenses. Well the good news is you can bring those licenses into VM more cloud on NWS and get up to a 25 percent discount for the lifetime of that account and you can also bring all of your existing Windows licenses in as well. So if this is something that interests you or that you think may help you make this a little bit more affordable you can actually see all of the pricing details for this program at and w w w dot trainer tests dot com slash cloud. I've included links to all the pricing information in. So there is a different pricing model for VM where cloud on AWOS than there is for a native AWOS and at a glance it may seem as though native AWOS is a lot less expensive. But they've intentionally structure the pricing so that you can achieve basically the equivalent price whether using native AWOS or VM or cloud and AWOS. So the VM software allows us to over subscribe which means we're going to be able to get more virtual machines running on the same hardware than we would with native AWOS and that's going to produce some cost savings. And because we can enable via more features like Diyar press that'll help us to ensure that we're always getting the performance that we need. The current price for a VM were Klon on a W-S is $8 and thirty seven cents per host per hour of on demand access. And if you break this down over the course of a year you're going to pay you know 8000 37 cents per hour for the entire year. So that can be pretty expensive that can add up quickly. So over the course of a year running one single ESX I host and VM are cloud on AWOS is going to cost you somewhere over $73000 about seventy three thousand three hundred dollars. So that's a lot of money for one host if we go with a one year reserve to model like we see here on the screen the price gets reduced to $5 and 93 cents per house per hour. So now that single host is down to about fifty one thousand dollars per year very significant cost savings. If we go to the three year reserved model the price gets reduced even further. And so over the course of three years we're going to spend about one hundred nine thousand dollars which makes it about 36000 per year per host. That still sounds kind of expensive when you think about how much in ESX host costs but what you add in VSX I host plus software licensing plus support plus you have to have the storage solution. And then you have to have the support for that as well. Plus you have to have all the networking equipment and the support for those as well. Right. You have to think about it that way because VM work hard on AWOS is providing you not only with the hosts but aspirating you've had for storage and OS X for networking. And so if you think about all of those solutions and how much it would cost you per year to maintain all of those solutions in an on premise data center 36000 per year starts to look pretty darn good. And so we have to think about it in those terms right at a glance seems expensive when you really think about it though what you're actually getting is you're replacing a lot of storage networking and compute costs at the same time. That's what makes this so attractive and you're transitioning to all flash storage. Right so you're probably moving to a faster storage technology than you currently are using. So good stuff. And then you have to also consider the operational expenses that this eliminates. So you don't have to update the XIV center in NSX. All of those upgrades are handled by V.M. when you have to have an on premise data center that is at least for 6.5 or later right. That's a requirement if you're going to do a hybrid linked boat meaning if you're going to be able to manage your cloud and your on premise through the same center server we have to be a these first 6.5 D or later that gives us the ability to cold migrate workloads to the VM or cloud cool stuff. So what this means is essentially you're not going to have to do any updates and be center on ESX. And in this ex-manager the NSX controller on the edge gateways for NSX all of those pieces are handled by via VMWare. That's no work for you. You don't have to think about any of that. You can also very easily integrate with native AWOS resources. So VM are cloud on AWOS runs on dedicated bare metal hardware inside of an Amazon datacenter. You can establish a very high bandwidth very low latency connection to resources in the AWOS cloud which can allow you to use things like Lamda ask us can Nice's it's easy to all of these resources that AWOS provides. And it's a lot of resources. You can utilize those and have that high bandwidth connection. So just think about it this way. Let's say that you have a database that you want to keep on your own sequel server and run it as a VM or you want to spin up simple web servers in an auto scaling group on AWOS. Well now we can do that. We have that level of integration. So it's really powerful. It gives you the ability to really leverage the full set of features from both VM Ware and AWOS. And when you put those features together you have a ton of capabilities.