 Hi, buddy, we're back. This is Dave Vellante with theCUBE. We're here talking storage at Amazon in Boston. Asa Kalevada is here. She's the general manager for hybrid and data transfer services. Let me give you a perspective of how these services come together. We have data sync, storage gateway, and transfer as a set of hybrid and data transfer services. So the problem that we are trying to address for customers is how to connect their on-premises infrastructure to the cloud. And we have customers at different stages of their journey to the cloud. Some are just starting out to use the cloud. Some are migrating and others have migrated, but they still need access to the cloud from on-prem. So the broad charter for these services is to enable customers to use AWS storage from on-premises. So for example, a storage gateway today is used by customers to get unlimited access to cloud storage from on-premises. And they can do that with low-latencies so they can run their on-prem workloads but still leverage storage in the cloud. In addition to that, we have data sync which we launched at Reinvent last year in 2018. And data sync essentially is designed to help customers move a lot of their on-premises storage to the cloud and back and forth for workloads that involve replication, migration, or ongoing data transfers. So together, gateway and data sync help solve the access and transfer problem for customers. Okay, let's double down on the benefits because you started this segment just describing the problem that you're solving, connecting on-prem to cloud, sort of helping create these hybrid environments. And so that's really the other benefit for customers, really simplifying that sort of hybrid approach, giving them high performance confidence that it actually worked. Right, exactly. Maybe talk a little bit more about that. Yeah, so with data sync, we see two broad use cases. There is a class of customers that have adopted data sync for migration. So we have customers like Autodesk who've migrated hundreds of terabytes from their on-premises storage to AWS. And that has allowed them to shut down their data center or retire their existing storage because they're in their journey to the cloud. The other class of use cases is customers that have ongoing data that they need to move to the cloud for a workload. So it could be data from video cameras or gene sequencers that they need to move to a data pipeline in the cloud and they can do further processing there. And in some cases, bring the results back. So that's the second continuous data transfer use case that data sync allows customers to address. Right. Okay, you're also talking today about storage gateway, high availability version of storage gateway, what's behind that? So, storage gateway today is used by customers to get access to data in the cloud from on-premises. So if we continue this migration story that I mentioned with data sync, now you have a customer that has moved a large amount of data to the cloud. They can now access that same data from on-premises for latency reasons or if they need to distribute data across organizations and so on. So that's where the gateway comes into play. So today we have tens of thousands of customers that are using gateway to do their backups, do archiving or in some cases use it as a target to replace their on-premises storage with cloud-back storage. So a lot of these customers are running business critical applications today. But then some of our customers have told us they want to do additional workloads that are uninterruptible. So they cannot tolerate downtime. So with that requirement in mind, we are launching this new capability around high availability. And we're quite excited because that's solving yet, allowing customers to do even more workloads on the gateway. And this announcement will allow customers to have a highly available gateway in a VMware environment. And with that, their workloads can continue running even if one of the gateways goes down if they have a hardware failure or networking event or software errors such as the file shares becoming unavailable, the gateway automatically restarts. So the workloads remain uninterrupted. So talk a little bit more about how it works just in terms of are there anything customers have to do, any prerequisites they have? How does it all fit? So customers essentially can use this in their VMware HA environment today. So they would deploy their gateway much like they do today. They can download the gateway from the AWS console. If they have an existing gateway, the software gets updated so they can take advantage of the high availability feature as well. And the gateway integrates into the VMware HA environment. It builds up a number of health checks. So we keep monitoring for the application uptime, network uptime, and so on. And if there is an event, the health check gets communicated back to VMware and the gateway gets restarted within in most typical cases under 60 seconds. So customers that are VMware customers can take advantage of this and to them it's very non-disruptive, it sounds like. That's right. That's one of the benefits. But maybe we talk about some of the other benefits. Yeah, so we saw that a large number of our on-premises customers, especially in enterprise environments, use VMware today. And they're using VMware HA for a number of their other applications. So we wanted to plug into that environment so the gateway is as well highly available. So all their applications just work in that same framework. And then along with high availability, we are also introducing two additional capabilities. One is real-time reports and visibility into the gateway's resource consumption. So customers can now see embedded cloud watch graphs on how is their storage being consumed? What's their cash utilization? What's the network utilization? And then the administrators can use that to in fairly real-time adapt the resources that they've allocated to the gateway. So with that, as their workloads change, they can continue to adapt their gateway resources so they're getting the maximum performance out of the gateway. So if they see a performance problem and it's a high priority, they can put more resources on it. They can put more storage, attach more storage to it or move it to a higher resource VM and they can continue to get the performance they need. So previously they could still do that but they had to have manual checks. Now this is all automated. We can get this in a single pane of control and they can use the AWS console today like they do for their in-cloud workloads. They can use that to look at performance of their on-premises gateways as well. So it's one pane of control. They can get cloud watch health reports on their infrastructure on-prem. And of course it's cloud, so I consume this as a service. I pay for it when I use it. I don't have to install any infrastructure, right? Yeah, so the gateway is again, consumption-based, much like all AWS services. You download the gateway, it doesn't cost you anything. And we charge one cent per gigabyte of data transferred through the gateway and it's capped at $125 a month. And you just pay for whatever storage is consumed by the gateway. Well, it's of course, when you talk to senior execs like Andy Jassy, he always says, well, we focus on the customers and sometimes people roll their eyes, but it's true. This is a hybrid world. Years ago, you didn't hear really much talk about hybrid. You talk to your customers and say, hey, we want to connect our on-prem to the public cloud. You're bringing services to do that. Asis, thanks so much for coming on theCUBE. Appreciate it. Thank you, thanks for your time. You're welcome. And thank you for watching everybody. This is Dave Vellante with theCUBE. Back right after this short break.