Hello and welcome to today's webinar titled VMware cloud on AWS planning operations and outputs.
Our Senior instructor can Willard will host a discussion of VMware cloud on AWS, the planning and the implementation considerations and the benefits associated with the MC on AWS outpost which was announced at reinvent
This session is for you if you use AWS today and you would like to understand how the MC on AWS can help connect on premises V sphere operations to the cloud, or if you're evaluating the benefits of an AWS cloud platform and the learning clerk curve to migrate existing services.
During the webinar. Everyone's phones will be muted. So if you have a question, please enter them in the Q AMP a box or the chat window at the bottom of your screen.
If you enjoy the presentation today. And if you're interested in learning more about training anywhere with our interactive virtual platform I MVP, please visit our website or feel free to contact us.
Today's webinar is being recorded and will send a copy to each of you. By the end of the week.
And finally, stay tuned till the end of the presentation where we will release two special promo codes to save you $250 on training, plus the opportunity to receive a free exam voucher valued at $250. Alright, let's get started. Can you can take it away.
Thank you, Michelle.
Good afternoon, or good morning, depending on your time zone and where you're joining us from
As Michelle mentioned, we are going to be talking about VMware cloud on AWS solution that was actually announced this particular part of it was announced a couple of years back at VM world.
Has been generally available for about the past year maybe 14 months, something like that.
And we've had some new announcements obviously shells referencing the VMware are technically the outposts announcement that was made at reinvent so I felt like it was a good time to come back and revisit this conversation around VMware cloud native us and what the options were
One of the things we did have the polling open as everybody was getting in here this morning. I'm going to wrap that up, but it looks like
A lot of you are certainly the majority of you at this point are using VMware on premises and AWS out in the cloud as to completely independent platforms doing different things with them. I suspect
Because we had the most respondents 74% of you said that you were using it in sort of that to stage or two completely separate solutions model.
Or without of course to view about of a fifth that are actually using VMware on premises and not working with AWS yet. So maybe this will spark some ideas.
Maybe even some ideas about why that might be applicable, or if that might be applicable to your use case. And finally, we've got a slim number of participants this morning about 10% of you.
That says you're actually using, or at least have used then maybe just seeing the VMware cloud on AWS.
So just interesting to kind of see where everybody was coming in, what their background or at least maybe what their expectations were with regard to these solutions and how they might work together.
So what is VMware cloud on AWS.
Folks, I promise this will be probably the busiest text test slide that you'll see, but it really is that overall solution of VMware is CT V sphere product.
SSI for the hypervisor V center for that management platform that we're all accustomed to.
And then it builds out. If you've read about VMware cloud foundation, you know, the cloud foundation wraps in a sex and VC and with our core V sphere deployment.
Giving us that end to end virtualization of those core resources in the data center get today, most of us are thinking about doing that on premises inside either our corporate data center or inside, maybe a colocation those types of deployments.
We take that core implementation of VMware cloud Foundation. And today, you might have the software defined data center manager deployed on premises.
I don't see a lot of customers that have gone that route, even though it's a native part of the cloud foundation deployment and it's available to you, but
It's certainly something that you're going to see if you do VMware cloud on AWS, it becomes your first in primary management interface.
And then once you've defined what do you want your VMware cloud on AWS infrastructure look like in the software defined data center manager that gets deployed for you and then you come back and start using the traditional V center sort of login that you're probably accustomed to.
So wiring folks looking at the MC on AWS from a business standpoint. What is it that's driving this interest.
First of all, it helps move things very quickly. It gives you scalability in the cloud, while retaining that traditional VMware infrastructure that you know that you're comfortable with that does all of the feature sets that you want.
So we're thinking about simply just scaling dynamically or possibly modernizing our applications, making them more web aware if we have our own internally built applications, that's one approach is the acceleration of our innovation internally for it.
Obviously, in the time we talked about a cloud solution. Responding faster to change becomes a primary thing. It gives us the ability to have continuity, if something happens to our on premises operation.
Depending on the environment in the rules about where you're looking at this from your country origin.
There may be some value here in response to the data sovereignty laws that are being implemented and being able to leverage VMware in the AWS cloud to make sure that you are in compliance globally with the various data sovereignty laws that are being enacted today.
And of course cost. We all know that no it conversation is complete without a discussion around usually total cost of ownership, depending on your organizational structure. The difference between operational expense and capital expense and how they want to invest those dollars.
So from that cost optimization perspective, right. You might have a mandate to get some or all of your infrastructure to the cloud.
You might be looking to shift from that capital expense to an operational expense sort of model has a huge impact on the overall business accounting and can be very beneficial.
So those are just some of the business trends that we see organizations, looking at it when we started thinking about those specific technology reasons to look at VMware cloud on AWS.
Based on a lot of the feedback that we're seeing in initial surveys and customer usage.
The two models that were frankly seeing First are the data center extension. We've maybe got a growing environment, a growing department and we want to be able to quickly scale that up or down, as we've proved out that part of the business model.
So data center extension is what VMware sees today as probably the number one reason that folks are considering going to market with VMware cloud on AWS.
Second is disaster recovery. If you've already invested in VMware on premises. Hopefully, you probably have a conversation with somebody along the way about Site Recovery Manager.
There is a Site Recovery Manager extension for the V MC on AWS solution that lets the cloud deployment become your fail oversight.
Complete with all the testing and audit capabilities that are inherent in Site Recovery Manager. So it gives you a great way to have that capacity available.
If a true Dr event occurred. You could scale the compute and memory resource during the code. The Dr event and then shrink that back down after the primary operations have returned to your on premise data center.
And then the last two UK use cases cloud migrations and next generation apps. Those are both smaller percentages of what we're seeing as the technological reasons that folks are getting into VMware cloud on AWS.
But they are the number three and number four reason, at least today. I've also already had the chance to work with a couple of customers that were
spin offs of other organizations or in startup mode for other reasons. And they were starting from scratch with VMware cloud on AWS, they were never ever going to have any on premises operations.
But they had a huge amount of VMware skill set on the team. And so instead of starting over real learning everything from an AWS centric point of view, they were simply going to leverage the AWS cloud.
Locations, and that proven hardware using the existing VMware skills that they already had on the team.
So why VMware cloud on AWS.
Right easy escape.
We're going to talk about some of the ceiling capabilities. We start with a very traditional sense, the MC on AWS is based on V San. We start with a traditional three node cluster that we can scale out from there.
And if you've already got VMware operations on premises, we have the ability to migrate those out into the cloud without retrofit right without re architected
And that sort of leads us to the. The second big benefit here it gives you the ability to start leveraging cloud environments and that cloud scalability, as well as things like
The region ality of AWS for data sovereignty and those types of concerns without needing to rework your applications from scratch.
And then lastly application modernization. We've seen this mentioned already in a couple of the slides but starting to be able to leverage the cloud native workflows.
All of the things that folks have already been talking about with AWS and leverage and leverage them in a VMware based architecture that they're already comfortable with.
VMware cloud on AWS really gives us that best of both worlds.
The VMware infrastructure that we already know we're familiar with managing more than likely, we've already got skill set on our team.
Combined with the AWS flexibility model, the global reach the data center deployments, those types of things got a slide coming up here in a couple of slides that shows the availability today, but that is changing.
on a quarterly basis at Penn, sometimes more quickly than even on a quarterly basis.
So how does this start to come together. For those of you that are familiar with the AWS architecture. Ultimately, the foundation of EMC of AWS is a traditional Amazon virtual private cloud or VPC, as you've seen it shortly in your dashboard panels.
Within that Amazon virtual private cloud. We then stand up the VMware SBC manager getting that the software defined data center manager. If you've not worked with that before. It is an automation tool.
That sits in front of your V center and V sphere environment, and it has the ability to go out and deploy the SSI do its configuration and join it to the center as part of automated workflows that are included with the SBC manager.
So once we've got our Amazon VPC VPC, so we've got the structure of that virtual network that private virtual network, we can deploy our V sphere infrastructure.
And then the native part, the first part, we see here on the left is from the ground up. We have the ability to connect our on premises V center with the center running out in the AWS cloud.
You will be managing two different instances of the center but with the new, relatively new introduced hybrid linked mode for V center. You can't do it all from a single login perspective.
So you do have the ability, just as you've always done to log on to your on premises V center and you would then see it in the cloud, deploy the center and all of the assets deployed in AWS through those workflows that you're already accustomed to in the center.
The other big advantage that we have, particularly for those of you that said you're already using VMware on premises and AWS native out of the cloud.
When we get over to the right hand side of this, you notice we seen illustration for native AWS services.
Leveraging AWS VPC endpoints. We can assume the network has been done correctly, we can bridge our native V central resources into AWS services for resource consumption.
So for instance, one of the things I could do would be to turn up at elastic file store and mount that natively to one of my virtual machines running in VMware cloud on AWS. I'm now leveraging that native AWS service infrastructure, the flexibility of their elastic network storage.
And tie that into an existing VMware driven virtual machine.
And obviously, the nice thing about that is that that infrastructure keeps getting built out as well. That's something that we see releases again quarterly
Frequently earn in May, May cases more often than quarterly more and more of those VPC endpoints that support the native VMware virtual machine access
And if you're already working with AWS, you know, the VPC endpoints are critical because they drive dynamically change the billing driving your building costs down on a monthly basis.
So where's this an option.
Unfortunately, this is sort of growing and changing so quickly. I had a bad time getting a much more current slide out of VMware
So this is dated March the eighth of last year. And you can see at that point there was heavy availability already in the US, obviously, in India and starting to get some presence in Asia Pacific
And that's been added on consistently. I'm going to show you where to go look to see if regions that you need are already supported or where they might be on the roadmap for deployment.
But the goal was what patent yell singer stood on stage and said last year at VM world, if I remember the statement, right, was that by the end of this year. So by the end of 2020
Everywhere there is a an AWS region there will be V MC on AWS support, so they are aggressively rolling that out and trying to make sure that they can meet the demands of the market.
And then one of the other big announcements that we were talking about a little bit at the start of the meeting was the idea of AWS outposts
So AWS outposts was announced by AWS, a year ago at reinvent and then just in December of 2019 was announced as general availability for the AWS native version of AWS outposts
But with the partnership between AWS and VMware, there is also a flavor or a distribution of the outposts unit that will be based on VMware cloud infrastructure, instead of AWS native core infrastructure.
And so today, they are accepting VMware is accepting beta applications for the V MC on AWS outposts program.
So that is currently open. I haven't heard anything about when they think that beta is going to close or what the general availability might be
But if you're not familiar with the idea of the AWS outposts you the thought here is that gives you the AWS native hardware.
Running the infrastructure of your choice today, it would be AWS native infrastructure, but we've got the beta running for EMC on that native AWS hardware and it says on your premises in your data center.
So what you're getting here is all of the management benefit all of the hardware benefit, but none of the potential latency issues.
So anytime. You've got a VMware centric workload that you want to use the DMC on AWS resources for
But it's latency sensitive, you may need to transfer some large data between your local data center and the cloud deployment.
You can leverage the outposts unit to put that processing in your data center, but it is a fully managed turnkey service. And like I said, beta for that they are accepting beta applications now. So if that's something that sounds of interest, there's a shortcut and I think
At some point here before we wind up at the end of this that link is going to get popped into the chat. So if the beta for that is something you're interested in you. If you don't get that copy down off the slide, you'll be able to grab that from the chat.
So we'll look at a couple of things here.
Just show you a little bit about what the user interfaces are going to look like.
Actually, I want to start with a conversation around what's coming. When you can expect to see it. One of the things that I think is so good about the DMC on AWS solution is
If you go to their main website so cloud.vmware.com and then EMC dash AWS, obviously this is their general marketing website.
touch a little bit about the product. But the really key piece of this in my mind is right up here at the top talks about use cases, it talks about pricing.
There is a pricing estimate are out there publicly available. So if you run through this and see if it makes sense for you.
That's a possibility. But here's the big piece. If you click on the roadmap slide or the roadmap tab up here. The top of the website, it will take you into exactly what's happening in when
So if we want to look at what's everyone to see just once in preview mode today.
We've got a cloud marketplace support coming. Okay, we've got a new COI coming
We've got a new API coming. So if you're leveraging some workflow automation or you already have an automation tool that you've written internally. Looks like we've got some new support for VMware cloud on AWS tasks.
One. This was kind of a big one to me.
We currently have fixed maintenance windows around the management schedule of the VMware team.
Now there's some flexibility and you can request some exceptions to these. But today, that doesn't ensure necessarily guarantee that they'll be able to accommodate the request looks like actually scheduling a fixed maintenance window around your IT operations is coming shortly.
And so it just gives you a nice ability to take a look at what's happening when things are coming
If we shift this let's go from preview to planned it features.
And let's just take a look at regional availability.
Right so new availability coming in Osaka Hong Kong. So it's like those are the only two that they've got additionally scheduled right now that maybe aren't already deployed.
So a nice way to take a look at what is coming, so far as features and region availability for the DMC on AWS solution.
Now, one last thing I want to do is to do a little bit of a walk through here.
And just show you what some of the user interfaces might look like. What things would feel like if you were working as you can well imagine
AWS is a subscription based model. That means the MC on AWS is also subscription based, so I don't have access to a live demo environment. What we're going to do is walk through some simulators here and give you a little bit of a look at what the environment will look like.
Give that a chance to load and then take it full screen.
So hopefully that is reasonably legible for everybody.
So what we're looking at here is what you would see when you would first log into the software defined data center manager right the SBC manager. So you're looking at this point we have just logged into the new
VMware cloud on AWS account for an end user account.
And we're going to start by clicking on the Create SBC button there.
And that takes us in much like you might expect with any other Amazon related service, we can pick the region where we want to deploy.
We can pick the deployment type name our software defined data center something reasonable something that means something to our, our IT operations and then go through and customize the size of the cluster and the type of host host capacity there.
And this screenshot happens to show
This was actually built back in the day when they were trying to do some demo driven things out of a private space that VMware had called zero cloud. So obviously, the last option down here zero cloud or AWS would not be an option right you you would only be actually deploying on AWS.
So let's go through let's ship this to
US West Oregon.
Oregon. We'll give it
A reasonable name here.
During the initial startup. If you're trying to figure out one if the MC on AWS is just going to work for you. Or maybe you know what's going to work, but you're in a start up mode.
You do have the ability to change the number of hosts from 321 this what you do a couple of things.
Let's say you're already committed to AWS and the the DMC on AWS model. Fantastic. It might still make sense. During the first 30 days or so to run with a single the sex host
And let you do some things like standard basic infrastructure build the connectivity and get all the networking correct between your on premises operations and your VM MC on AWS cloud.
And do all those sorts of base infrastructure things while keeping that cost of ownership very low.
During the first 30 days just run with a single host, we can always scale that at a later time. So when you're ready to move from sort of the startup phase and that base configuration phase.
Into production operations. You will then scale to that traditional minimum three host cluster to support proper VC and operations.
What are we missing here.
downside to these simulations.
There we go.
When you first deploy, especially if you're going to do the one post deployment and use that as a startup cycle.
You can start your deployment without associating your V MC environment with an AWS account. But that's only possible
If memory serves, you can only operate that way for the first 15 days after that the relationship between VMware and AWS says that you must build
A an AWS account that you're going to use for your VMware operations and associate your software defined data center with that Amazon VPC under that account.
So, for the moment, we'll let that go with that.
And then the other thing that we have the ability to do is pass if we needed to is we could specify the management subnet that we wanted this deployed into obviously for the demo. You see, I'm getting prompted up there. We're just going to go ahead and say, deploy the VPC
So this is a simulated environment. But this is kind of exactly what you'd see right, we'd have a progress bar, it would run for a while.
And then at the end of that we would see the resulting software defined data center. In other words, our initial cluster deployment presented on the SBC manager.
Can see pretty substantial. Here we built this with a single ASX host and I've got almost 100 gig of compute power.
512 gig of memory and 10 terabytes of storage on that single host. I think these are pretty substantial pieces of hardware that scale up
And so we could click here on The View Details.
And that will take us into the configuration of the STC environment.
I can take a look at the networking is its configured so far.
As we mentioned everything in the VMware cloud on AWS is built on sex.
And so we would ultimately then configure up the intersects environment to be able to talk to most likely the public Internet
And very potentially on into either a VPC endpoint. If we're going to use VPN or
A VPN endpoint. If we're going to use software encryption between our on premise data center and the Amazon cloud.
If you're already an Amazon user and you use Amazon Direct Connect. You can also use that as your connection point between your on premises VMware operations and your AWS cloud based operations.
Right, so we initially start we showed the system diagram we can hide that if we want
Work with things in more of a traditional setting up some nets setting up firewall rules, those types of things from the the configuration.
We can look at add ons.
One of the things that's included with every VMware cloud on AWS subscription is the hybrid cloud extension.
If you've not seen any of the trade press or the write ups around it's being abbreviated as a CX it is what gives you
Native V motion capability from your on premises data center out to your Amazon based VMware operations gives you some network accelerations of wine conditioning as part of that.
And it's included with every subscription and so becomes a resource that you download and import virtual appliance on your on premises operation.
And then you can figure that to talk to the AWS based component, and it can assist with a lot of the heavy lifting of migrations.
Including doing batch migrations. If that's something that's on your roadmap, you can queue up batch migrations and the hybrid cloud extension HCM can handle that for you.
I mentioned Site Recovery Manager. If you want to use the cloud resources for your disaster recovery fail over site.
We can take a look at troubleshooting. This is an area of the product that keeps getting development attention.
So there are various types of tests. And in this case, they've selected hybrid linked mode talked about the ability to connect the on premises, the center with the cloud based V center. So that's hybrid link mode.
So run through and check those. There are some live migration capability that it can go through and check
All right. So look at this
Says, there's still that some tests remaining there.
And I know this may be a bit of an eye chart. But the other thing we've looked at is our V center information.
So as I said, you will have a dedicated V center deployment out in the cloud, which you can associate with your local the center instance
So this gives you all the details for the V center it's default account. I will be tradition, think of for most of us probably administrator and V sphere dot local
You'll see the the credentials are a little different there so administrator at VM si dot local when they're out on the cloud.
And then we can always go back and take a look at
And the ability to view your support information right there.
So just a little bit of what it looks like from the software defined data center. The other one that I thought we want through to give you an idea, we talked about the fact that this is a scalable environment on demand. So take a quick look at what
So let's try to make this full screen for everybody.
See when we're ready to add hosts get everything is done from within the SBC manager.
Like that is the management platform for
VMware cloud foundation
So sorry, trying to make sure, because this is very prescriptive. I can only do exactly what they tell me. So we started from the SD VC view and we go back into the View Details option. In this case, we're still running that single host sort of initial startup behavior.
But from here we're going to add host
And then specify the number of hosts. In this case, we're going to add three
And then say that hosts.
And so now you'll notice the add or remove host options are grayed out. Right. I cannot have any more than one management of it happening within the environment at any one time. But it tells me at the top here, it says, adding hosts to your software defined data center.
And this will process for a while, VMware and AWS say it generally takes
Somewhere between eight and 12 minutes to add a host and we're actually going out, we're finding available hardware in the
Amazon region that you've specified we're pulling that out of availability and assigning it to your software defined data center installing and doing the configuration of all the right patch levels for your ASX hosts and then adding it to your cluster.
I think the simulation is taking quite a while here.
To have the ability to click come through, but it's still making me hold
On that any longer. So we've got a question.
Yeah, actually got a great question there says it didn't look like I've got a lot of choice on the types of hosts that we would have added when we did the host add. That's true.
Even actually today. So look at the questions was just born meditation of the simulator, to some degree, yes, actually, the
Architecture of the individual hosts that Amazon and VMware, have a great two is still very prescriptive.
I think at this point we have the choice of exactly three different types of hardware configurations that you can choose from when you're doing your host bills.
So they are pretty specific about that yet and not giving you the ability to sort of dial things up and down.
One of the big things that has changed is the ability, while the underlying host architecture may not change.
With the current version of the MC on AWS release you can pick the number of processors that are going to be active on your host configuration.
They're technically not giving you the ability to completely change the underlying host, simply because of the storage and the V San architecture that that's supporting but you can change the number of CPUs and thereby change your monthly bill for the compute resource.
Alright, so I think that will wrap us with the simulation showed you a little bit about the website and how to look and see what new features are coming
Up Michelle I think you've already. We've had a few questions here in the chat. I haven't seen anything in the open Q AMP. A. So do we want to open it up a little more for anything additional
Michelle Coppens :: Webinar Producer
Yeah, I think that's a great opportunity. Now, if anybody does have any questions that you've been holding on to please feel free to enter them now in either the chat window or the Q AMP a box at the bottom of your screen.
While we're waiting for those questions to queue up. I want to talk about promos, as mentioned at the beginning of our webinar webinar so you can save $250 on your training when you use the promo code snowball and register by January 31 I'm going to link those details in the chat. Now,
You also have the opportunity to receive a free exam voucher. So these exam vouchers.
Apply to the VMware V sphere six dot seven class. If you enroll in this class. We're going to give you a free exam voucher valued at $250 you can combine this with the winter promo so that's going to give you $500 in savings and I'll link that for you in the chat window as well.
So we've got a question says, if you're running
Virtual Machines through an outpost unit is the hardware set. Can you enable, disable features there or will entire racks have to be swapped out to upgrade the units.
The Amazon outposts unit model is a completely fully managed model. So the idea is, when you would source that out, push you that whether it was for the AWS native architecture or the EMC architecture when it's available.
That will be whatever the current model is of the AWS proprietary hardware.
And then over the lifecycle of that hardware, because the output unit is a fully managed service.
If you continue to keep the service and stay on contract with that as any other cloud service if that hardware gets revved VMware would VMware AWS and VMware together would come out and swap that hardware as needed as upgrades or do for
Right. So another question. Follow up in the window. So try to make sure you understand right the management perspective.
You use the software defined data center manager to set up the cluster. The initial host count the type of hosts, all of those types of things.
And it is literally that right you are configuring the software defined data center. That's what the SD DC manager does
Once that is deployed and you have a working the center instance because nearly everybody in the VMware world.
Thinks about managing their environment through the center all of your day to day management. What happened in the center as normal.
Right, the SBC manager is only there for that initial hardware and cluster architecture configuration or obviously if you were going to grow a cluster that would be considered a hardware level change and the SBC manager would be used for that as well.
For the most part about that again with the relatively new to the product, what they call hybrid link to mode.
It lets you be able to associate the cloud based V center instance with the local on premises V center instance and only log in. Once you log into your local one and they can see everything is managing and everything that's in the cloud that needs to be managed there.
And then you would determine when you were deploying the EMS, we would decide if you wanted them deployed on premises or out in the cloud.
At the time of deployment that of course with things like depending on how you've set up your network infrastructure. If you're using something like Amazon direct connect
Or with even without direct connect, but using the hybrid cloud extension, you can then live migrate. So the motion virtual machines from on premises out to AWS or the other direction. If you needed to
So, so far, I was aware of virtual machines run, you can choose that and deployment time and then change that the future if you'd need to
Pay some good advice safe answer. Are there we go.
Down because I see that I'm getting the question, but they're not showing up, got it.
So is there any impact on the software defined data center due to system status checks on etc etc two instances.
No. Right, so it's a little different approach.
With those Yes, technically, the SX others that you see in VMware cloud on AWS are the bare metal hardware easy two instances, but they are managed independently.
So, once they're pulled in and made part of the STC management environment, they are no longer subject to sort of the traditional AWS easy to instance checks.
They would then be part of the regular V center ASX host management checks that would run under the V center management infrastructure. So did that answer the question.
Make sure I make sure I understood that I understood the question right and give you the proper answer there.
And there are some other really nice things that obviously within the scope of trying to stay under an hour that we really didn't get into
Things that are covered when we do either one of the classes that we were showing on the previous slide, but things like the ability to enable
What's called the elastic Drs. And that is that your clusters can grow and shrink based on the workloads. If you want that to happen.
Now, obviously there's financial impact to that when we add a host that changes your monthly bill, but if you are in a really dynamic environment and you want that to happen. That's something you can figure
Anytime there's a host failure of any kind. The first thing that happens is the services automatically provision a new host. Get it configured and join to your existing cluster.
Start any V San data rebuilds that would need to be in place and then retire the old host. And during that cut over
The, the primary importance is getting new host provision it online for you. You're not being charged for a to host overlap right in the event of any kind of a failure, you just simply pay for the scope of the cluster that you had configured when the failure occurred.
So very proactive and making sure that new deployments happen prior to worrying about retiring the failed hardware.
With no financial impact right no change on your bill.
Looks like the Q AMP. A in the chat have multiple quiet.
Michelle Coppens :: Webinar Producer
I'll take this opportunity now to share the links over to our VMware training page, along with those promo codes. Once again, you should find all of those hyperlinks and promo codes in your chat window.
We do have some time now. So if questions. Do come up, feel free to post it looks like we do have one more.
Yep, looks like we've got another one says, Can I had my own hardware to a an outpost unit and the answer that is no right. The outpost units are completely self contained
As a service style deployments and so you're getting the native
AWS hardware in there and you may not mix and match with other. Now what you can do is with the network. And again, one of the major drivers behind doing outposts
Is this idea that we're minimizing the latency, the traffic time. So when you think about an outpost unit getting deployed in your corporate data center right sitting right next to your other racks of hardware.
You're going to have the ability or the leverage that high speed connectivity of being right there. But you may not mix and match the hardware inside the output unit that is
Effectively, a seal unit. It's not truly seal, but it's a closed system for the VMware specific outputs unit if you are going to have the outpost unit and you need more capacity.
Like, that's a traditional ad. And so just like you would add capacity in the VMware cloud on AWS and that would automatically happen and your monthly bill would change.
You can go in and reconfigure your outposts hardware configuration to add another outpost server and the outpost team will come out and install that new server and that will then be reflected on your next monthly bill.
Then I had promised to put the link for the roadmap into the chat. So there is that.
Michelle Coppens :: Webinar Producer
Thank you so much. Ken and thank you all for attending our session today. As a reminder, we have recorded this session, and we'll send a copy to each and every one of you. I hope you all enjoy the rest of your day.