(upbeat music) >> Hi everybody this is Dave Vellante with "theCUBE", and I'm very excited to be here at Amazon in Boston at Storage Day. And when you go back to 2006 and you think about the launch of Amazon Web Services, S3 was the first storage service. You know very simple, object store, and it became very, very popular, and I remember when Amazon announced EBS. I said okay, was at re:Invent and it was an exciting time. Well today, we are going to cover the innovations that Amazon has in its expanding storage portfolio. We've got experts from Amazon that are going to help us drill in to actually what's being announced, how these announcements work for the customer and what the business impact is going to be. Now, if you think about the history of cloud generally, but AWS specifically, which got cloud started, you know, it really started this, okay, I can now put data into the cloud. I can spin up, compute and storage, and not have to do all heavy lifting. And that was really when infrastructure as a service was born. And you had, CFOs loved it because they could shift CAPEX to OPEX, developers loved it 'cause they could treat infrastructure as code, and it really has become the new model. But what happened initially was people either did a lot of development in the cloud, or they would take applications and workloads running on Prim, put them in the cloud, and get benefits: lower cost, better agility, much simpler management. And they would be able to sort of retrain people, or shift people to more strategic workloads and activities. This became critical starting at around the 2015-16 time frame with all the talk around digital transformation. But in and of itself, what customers tell us is what they really want to do with the cloud is change their operating model. So you think about new programming models, you think about agile programming, new methodologies, DevOps really comes into the fore. The whole big data meme involved into data and digital transformation, you're seeing people take advantage of data lakes, and then of course, you've got all this data, what's the next level of innovation? It's to take machine learning and put it on top of all that data. So the innovation engine is no longer Moore's Law, it's now a cocktail of data, plus machine intelligence, or AI, and then the cloud gives you scale. Global scale, which is very important. We're going to drill down today and talk about Amazon's philosophy on regions and availability zones, and really try to poke at how that's maybe different from some of the other cloud providers. But really the most important thing here I want you to think about is business impact. If you can change the operating model, you can get more out of your IT infrastructure and your infrastructure as a service than just lower cost or even better agility, you can actually transform your business, create new types of business models. Now, underneath all this is storage. You got to have sets of storage services that can support these new emerging workloads. So we started out with S3 which is object, EBS was file and supported database, and you've seen Amazon's database business explode, it's a multi-billion dollar business. And now, we're really digging into file, as an opportunity for customers, and of course, for AWS. So "theCube" is thrilled to be covering this. Stay with us, we got a full day of programming. Keep it right there. (upbeat music)

>>This is >>Dave Volante, and welcome to Storage Day. We're here at Amazon and Boston and you're watching the Cube. Wayne do so is here. He's the general manager of a lot of stuff. File hybrid edge transfer and data protection Service is at Amazon. Web service is good to see you, Wayne. Thanks. >>Good to see you. >>So let's talk about that. That's a pretty vast portfolio that you have explained that to our audience. >>Sure thinks so. The portfolio that I'm responsible for covers a vast swath of our stories portfolio on AWS. So in that we cover all of our files. Service's s Oh, that's E f s and FSX. Our data transport service is which includes data sync, transfer for sftp and our snowball or snow service's. And then also hybrid edge, which includes our snowball, compute and our stories, Gateway Service's and then data protection, which includes a W s back up. >>Wow. Okay, great. Congratulations on that portfolio. And, you know, I said I said earlier on it started with s3, and it's just exploded. Now all the service is this is part of what we sometimes call tongue and cheek cloud to 0.0, there's more work loads, more capabilities, more granularity. But talk about some of the big picture macro trends that you guys see in the marketplace. Specific Thio Sort of your area. >>Yes. So, uh, actually, it's so many, uh, think you said things are expanding. Things are accelerating in our space. One of things I like thio talk about with respect to our portfolio is we have storage service is dated. Transport service is to match the needs of your workloads and your applications. So all of these service is a purpose built for the type of storage that you need, the programming model that you need for your applications and workloads. So whether it's object storage with s3 and glacier or block storage with BBS or most recently, file service with F s and F S X file service is so you have the tools at your disposal. It'll that you need based on your on your application. Workloads. >>Talk more about the programming model. What? How do you envision that? What do you What do you mean? What's your mental model of the different >>process? You're so forever. People have been programming based on, you know, whether it's performance or or some scale of some sort. Um, you know, uh, databases traditionally used block storage because they don't need a lot of logic between them and the storage medium itself. File storage is been used for 50 years and has a very specific program model that exist in every operating system in every programming language. You know, whether it's an open, ah, read right, see close. It's a common paradigm that is used all over the place and that capability in the performance that you need to satisfy those applications and workloads very specific. And so for for aws, we provide those final systems for for Lennox, if you would with F House Windows, which is ever sex for Windows and for very high performance computing on luster. We've had an amazing storage platform, which is s3 and S three forms the basis for a lot of our customers data lakes on and basically storage data repositories, for which there are many integrations. With that, there are other >>sword service's. I often joke that, you know, if your expertise is is unpacking boxes plugging in setting up storage arrays, managing London's you, you might want to think about updating. You know your skill sets right, But so that's another big mega trend that we certainly see is people just don't see a lot of value in planning and managing and migrating over six month periods. Storage a raise. It's It's something that really doesn't have a lot of value to the business. So you guys have announced all these service is over the years and you've got some new announcements as well, that kind of play into some of the trends that we've been talking about. Talk about the news. >>Yes, that the news is pretty rich. Uh, for this season, let's let's start off with FSX eso FSX is our service for bringing fully manage third party or open source file systems, um, to our customers. And so Fsx Windows, as example, was launched last year, reinvent and has been rolling out the whole Siri's of features throughout the year, and we have a nice set of features coming out this year. So, as example today, effort, Sex Windows is a single ese service. We are rolling out multi easy capability, >>okay? And you you Sometimes you guys make the point that the beauty is there's no change required in APS, and we talked earlier about the program. We'll talk a little bit more about that. Why is that important to customers, >>you know and all index on FXX windows for another minute. A lot of abs been written to use the semantics of a particular file system in case of Windows will say NT f s and their written for that specific file system. We've provided customers with the capability of bringing those applications to AWS without any wary of compatibility. It's a pure lift and shift model. S O makes it really easy for them to bring their workloads. They should bring their workload so they don't have to deal with some of things you brought up early around provisioning buying systems, having to worry about saying that, planning for all of that. We take all of that work away from them and they get full compatibility based on what they need today and with some of the additional capabilities we're bringing to bear with the integrations in the ecosystem and heat up US ecosystem, they'll be able to appreciate those as well. >>Let's talk a little bit about more about that because you're basically, I'm inferring you're saying, Hey, this compelling reasons why you should move into the cloud. For instance, File Service's into the cloud. What's the difference between my on Prem? Isn't just on Prem Nass stuffing it into the cloud? Or is it more than you touched on integration? So convince me, why should I move? >>It's so much more than that. So if we if we look at the basic infrastructure once you literally click three or four buttons, Thio started files and creative file system, you no longer have to worry about it ever again. So the things that you have done on Prem, you no longer have to worry about having a sword administrator or having to provision in by storage and maintain it. We take care of all that would take care of all the security elements. I'm so important to your data to make sure that's in a in a secure environment. Security. It's job number one for us. So all of these capabilities and the ability to stand it up to never have to manage it never adorable security. We take care of all the capabilities like you should really be bringing those workloads onto a platform like this so that you can spend your time on added value. Um, service is our applications for your >>business, while in the integration is also a key piece of it. I mean, you know, for years, customers and customers still sometimes want to roll their own. You know, they like to have the you know, the knobs and turn them. But but many customers that we talked or saying Listen, it's too expensive. I don't want to be a systems integrator anymore in the cloud. How can they take advantage of those? Like sometimes they call it the flywheel effect. But the other innovations that you're bringing, whether it's machine learning or other service, is that you guys are bringing in. Is that how tight is that? Integration. >>So those integrations are ongoing, and they're there forever. It goes back to what I said a minute around over a three year period. All of these capabilities gonna be delivered to them, if you would at this at the same cost as the basic service. So let's talk about what happened this year. Um ah, lot of our customers are using sage maker for their M. L A I capabilities and sage maker is deeply integrated with both fsx luster and uh, E F s so that customers again don't have to worry about stories. They're not the way about sharing that are scaling. It's all there for them. >>You mentioned. Also you responsible for the snow product convention an edge. I was what it was to me. It was your first move, so the hybrid, I'll call it. But I always joke that, but it's true. The fastest way to get data from Point A to point B is a Chevy truck, and so, but you're referring to a sort of an edge play. You talk a little bit more about that, help us understand it. >>Sure, so Snowball, a service launched about five years ago. We initially launched a service as a bulk data migration service, and it's it's been that service for roughly four years. About a year ago, a little over a year ago, we started introducing thehe bility to have compute as part of that device, and the reason for that was customers were telling us as we're moving the data, we would like to be able to do some pre processing before it makes it onto AWS before it goes into history, is example. So we started providing that capability that ended up expanding into a full blown if you would cloud platform on a device that could be run in disconnected environments or stare environments. So with Snowball today of the ability to have easy two instances CBS storage s3 storage all in one device. And so that's a really powerful construct because you can build your applications on AWS using the same service is prove out if you wouldn't Dev UPS model that there what you need to be and then literally lift them onto, ah, snowball device and have those executing in the field as if they were running directly in the cloud. >>Change the subject a little bit when I look at the logo slide of all your customers, a lot of big names on their their global companies, a lot of things. So I run a cloud and they got a data center. You know he's Boston or something. No offense if you have a data center, East Boston, but regions are critical, um, especially for global scale. Cloud brings global scale, but it's also important to have data approximate to the users. So you're reducing late and see there's availability and redundancy aspects. Talk about your philosophy around regions and how it fits into your portfolio. How do you take advantage of all that capability? >>So a lot of our customers have global presence and the ability for them to have their application to have their business function in the regions that they're doing business and have those little agencies and also the availability model of being in multiple places. Case of disasters super important. Um, are regions are built, have at minimum three availability zones and an availability zone. You could think of boat as, ah, data center. So, for example, with the F. S. When you stand up a file system with the F S, your file system is automatically distributed, replicated across all three availability zones within that region. But as the user, you don't worry about any of that. We take care of it all for you. In the unfortunate event that our availability zone is made unavailable, your data is still fine. You still have access to that data all time? >>Yeah, and your customers, I think increasingly understanding this the beginning toe architect around regions and availability zones. It's a different way of thinking, but it's in some respects sort of the modern way of thinking. >>If you if you if you go back a few years and you think about all of the disaster recovery or business continue in software and capabilities that had been created, we're providing all of those capabilities today in our regional construct. >>Yeah, well, you know this. I mean, you both better have been around for a while, and we've seen the unnatural acts that you had to do to sort of create that level of redundancy and business continuance. And it was extremely expensive, complex and really risky to test. So I'll, uh, I'll leave you with the last word. Any other thoughts that you want to share with our audience? We're >>We're We're just first off. Thank you for giving you the time. Today. We're really excited about what we're doing with each of these. Service is we're very excited about the portfolio overall on the value that it's going to bring, and he's bringing to our customers today. We're excited about all the announcements. >>Yeah, we'll say we're seeing a lot of innovation. Expansion of the Amazon portfolio. Optionality, granularity performance, horses for courses, the right tool for the right job way. Thanks so much for coming to >>my pleasure. Thank you. >>You're welcome. All right. Keep it right to everybody. You watching the cube storage day from Amazon in Boston? Right back.

[Music] hi everybody this is David on tape with the Cuban welcome to Boston we're covering storage here at Amazon storage day and we're looking at all the innovations and the expansion of Amazon's pretty vast storage portfolio Duncan Lennox is here is the director of product management for Amazon DFS Duncan good to see it's great to be here so what is so EF s stands for elastic file system what is Amazon EFS that's right EFS is our NFS based filesystem service designed to make it super easy for customers to get up and running with the file system in the cloud so should we think of this as kind of on-prem file services just stuck into the cloud or is it more than that it's more than that but it's definitely designed to enable that we wanted to make it really easy for customers to take the on pram applications that they have today that depend on a file system and move those into the cloud when you look at the macro trends particularly as it relates to file services what are you seeing what a customer's telling you well the first thing that we see is that it's still very early in the move to the cloud the vast majority of workloads are still running on Prem and customers need easy ways to move those thousands of applications they might have into the cloud without having to necessarily rewrite them to take advantage of cloud native services and that's a key thing that we built EFS for to make it easy to just pick up the application and drop it into the cloud without the application even needing to know that it's now running in the cloud okay so that's transparent to the to the to the application and the workload and it absolutely is we built it deliberately using NFS so that the application wouldn't even need to know that it's now running in the cloud and we also built it to be elastic and simple for the same reason so customers don't have to worry about provisioning the storage they need it just works NFS is hard making making NFS simple and elastic is not a trivial engineering task is it it hadn't been done until we did it a lot of people said it couldn't be done how could you make something that truly was elastic in the cloud but still support that NFS but we've been able to do that for tens of thousands of customers successfully and and what's the real challenge there is it to maintain that performance and the recoverability from a technical standpoint an engineering standpoint what's yes sir it's all of the above people expect a certain level of performance whether that's latency throughput and I ops that their application is dependent on but they also want to be able to take advantage of that pay-as-you-go cloud model that AWS created back with s3 13 years ago so that elasticity that we offer to customers means they don't have to worry about capex they don't have to plan for exactly how much storage they need to provision the file system grows and shrinks as they add and remove data they pay only for what they're using and we handle all the heavy lifting for them to make that happen this this opens up a huge new set of workloads for your customers doesn't it it absolutely does and a big part of what we see is customers wanting to go on that journey through the cloud so initially there starting with lifting and shifting those applications as we talked about it but as they mature they want to be able to take advantage of newer technologies like containerization and ultimately even service all right let's talk about EFS ia infrequently access files is really what it's designed for tell us more about it right so one of the things that we heard a lot from our customers of course is can you make it cheaper we love it but we'd like to use more of it and what we discovered is that we could develop this infrequent access storage class and how it works is you turn on a capability we call lifecycle management and it's completely automated after that so we know from industry analysts and from talking to customers that the majority of data perhaps as much as 80% goes pretty cold after about a month and it's rarely touched again so we developed the infrequent access storage class to take advantage of that so once you enable it which is a single click in the console or one API call you pick a policy 14 days 30 days and we monitor the readwrite IO to every file individually and once a file hasn't been read from or written to in that policy period say 30 days we automatically and transparently move it to the infrequent access storage class which is 92% cheaper than our standard storage class it's only two and a half cents in our u.s. East one region as opposed to 30 cents for our standard storage class two and a half cents per per gigabyte per gigabyte month we've done about four customers that were particularly excited about is that it remains active file system data so we move your files to the infrequent access storage class but it does not appear to move in the file system so for your applications and your users it's the same file in the same directory so they don't even need to be aware of the fact that it's now on the infrequent access storage class you just get a bill that's 92 percent cheaper for storage for that file like that ok and it's and it's simple to set up you said it's one click and then I set my policy and I can go back and change my that's exactly right we have multiple policies available you can change it later you can turn off lifecycle management if you decide you no longer need it later so how do you see customers taking advantage of this what do you expect the adoption to be like and what are you hearing from them well what we heard from customers was that they like to keep larger workloads in their file systems but because the data tends to go cold and isn't frequently accessed it didn't make economic sense to say to keep large amounts of data in our standard storage class but there's advantages to them in their businesses for example we've got customers who are doing genomic sequencing and for them to have a larger set of data always available to their applications but not costing them as much as it was allows them to get more results faster as one example you obviously see that yeah what we're what we're trying to do all the time is help our customers be able to focus less on the infrastructure and the heavy lifting and more on being able to innovate faster for their customer so Duncan Duncan some of the sort of fundamental capabilities of EFS include high availability and durability tell us more about that yeah when we were developing EFS we heard a lot from customers that they really wanted higher levels of durability and availability than they typically been able to have on Prem it's super expensive and complex to build high availability and high durability solutions so we've baked that in as a standard part of EFS so when a file is written to an EFS file system and that acknowledgement is received back by the client at that point the data is already spread across three availability zones for both availability and durability what that means is not only are you extremely unlikely to ever lose any data if one of those AZ's goes down or becomes unavailable for some reason to your application you continue to have full read/write access to your file system from the other two available zones so traditionally this would be a very expensive proposition it was sort of on Prem and multiple data centers maybe talk about how it's different in the clouds yeah it's complex to build there's a lot of moving parts involved in it because in our case with three availability zones you were talking about three physically distinct data centers high-speed networking between those and actually moving the data so that it's written not just to one but to all three and we handled that all transparently under the hood in EFS it's all included in our standard storage to your cost as well so it's not something that customers have to worry about more either a complexity or a cost point of view it's so so very very I guess low RPO and an RTO and my essentially zero if you will between the three availability zones because once your client gets that acknowledgement back it's already durably written to the three availability zones all right we'll give you last word just in the world of file services what should we be paying attention to what kinds of things are you really trying to achieve I think it's helping people do more for less faster so there's always more we can do and helping them take advantage of all the services AWS has to offer spoken like a true Amazonian Duncan thanks so much for coming on the queue for thank you good all right and thank you for watching everybody be back from storage day in Boston you watching the cute

>>We're back in storage day at Amazon in Boston, on detente with the Cube. Ed name is here. He's the general manager of X ed. Welcome to the Cube. Good to say thanks for having me, Dave. Okay, So explain to me why you guys launched FSX for Windows File server. You know why now? >>Well, we did it because customers asked us to do it. What customers told us was that they were tired of all of the effort and overhead in managing windows, file systems and Windows file servers on their own, everything from routine maintenance, like patching to provisioning. They just didn't wanna have to do all of that heavy lifting. So they asked us for a simple solution. Fully manage solution on the cloud. There's a lot of windows data out there. A lot of data that's access from windows computers. Eight of us is the cloud that has the most windows workloads running on it. So it was a very natural ask for customers to ask us as they're moving their windows workloads onto eight of us to have a file system that's fully managed for them that could be accessed by those workloads. So it was It was actually very natural and, uh, unexpected. Ask from customers, >>you know, love. You may not know that, but it does kind of make sense. Is so much windows out there You're the cloud leader. So peanut butter and jelly. Um, how do you see customers using FSX for Windows? >>Yeah, What's really exciting is they're using it for a really broad spectrum of workloads eso everything from traditional user shares and home directories, Thio development environments to analytics, workloads, tau video, trance coating. So it's a very wide spectrum of workloads that they're on the service and we're continuing to see new new types of workloads every day, which is really exciting. >>So we're hearing stories. What exactly is new around FSX for Windows file service Specifically. >>Yeah, Well, we've launched a number of capabilities this year throughout the year s 01 of the significant ones that we launched was the ability for customers to use their self managed active directories on dhe join their FSX file systems to those. So we now have two options. Customers can use a fully managed AWS fully managed active directory or their own with FSX. We launched a number of capabilities around access from on premises. For example, customers can now access. Or when we launched it, we announced that they could now access their file systems over direct connect connections over VPN so they can access the Windows file systems from computers and from end users that are running on premises. So quite a few announcements this year Those are just two examples, and we're really excited about really a slew of announcements and feature features that we're launching now. And I can get into those if you like, give me some examples of your work. So one of the, uh, the most common questions we've had from customers is. Can we offer a native multi daisy capability, multi availabilities own capability? So a lot of customers are running enterprise grade workloads on FXX, and they want to move more and more of those workloads onto AWS, and they don't wanna have to, ah, manage the overhead of using something like a distributed file system or D F s replication between fsx file systems and different disease. So we're launching a fully managed, super simple, multi easy capability, and that's a deployment options that custom the customers will have in addition to what we already had, which was the single easy deployment options. >>Let me see some recurring themes when you talkto folks at Amazon announced service is it's the it's the same sort of mantra. Be able to reduce that heavy lifting, shift your focus to things that will add more value to your business. Take advantage of these other service is through these integrations that that we're doing. So I mean, it kind of feels like a no brainer, but I give you the last the last word. I mean, is it Why is it why should customers, you know, sell me on why I should move by dated to the cloud? >>Yeah. I mean, we we like to think of it as a no brainer because we are fully managing everything for the customer. Um, the the service is built on top of Windows server, so provides a fully compatible Windows file system, and we've managed that fully four customers, So you get complete compatibility with us and be complete compatibility with Auntie if s file system semantics and features. So it's a very simple move for customers to move their existing workloads onto the service and have it before we managed a couple of the other features that we're launching that I do want to mention our We're launching data D duplication we're launching. Ah, whole bunch of administrative capabilities, like user quotas were extending. Our administrative CIA lied to do things like a lot of customers to create shares programmatically so really a very exciting set of capabilities that we really think make this a ah no brainer for customers. >>Well, that's another recurring themes. You guys, you know, you dropped prices and look at the moors losses. Prices continue to drop. The differences them is on. You make it transparent on DDE. If I use a service is lower cost, my bill goes down and then, of course, I end up using more because this is an elastic world. So that's a good thing. But, Ed, thanks so much for coming on. The key. Thank you. Share is that any other thing is you guys only window specialists. It's just kind of ironic, you know, leader in windows. And, uh, >>well, it really comes from What are our customers are asking us for? So they see moving their windows. Workloads is the first step to the full modernization and being all in on the cloud. >>Great. We'll get exit. Thank you. All right. And thank you for watching everybody right back after this. Short break, Dave. A lot with the Cube.

(upbeat music) >> Hi, everybody, we're back. This is Dave Vellante with theCUBE. We're here talking storage at Amazon in Boston. Asa Kalavade's 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 DataSync, Storage Gateway, and Transfer. As a set of Hybrid and Data Transfer services. The problem that we're 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, DataStorage Gateway today is used by customers to get unlimited access to cloud storage from on-premises. And they can do that with low latency, so they can run their on-prem workloads, but still leverage storage in the cloud. In addition to that, we have DataSync, which we launched at re:Invent last year, in 2018. And DataSync 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 DataSync help solve the access and transfer problem for customers. >> Let's double down on the benefits. You started the segment just sort of describing the problem that you're solving, connecting on-prem to cloud, sort of helping create these hybrid environments. 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. >> Maybe talk a little bit more about that. >> So with DataSync, we see two broad use cases. There is a class of customers that have adopted DataSync 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 on 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 DataSync allows customers to address. >> You're also talking today, about Storage Gateway high availability version of Storage Gateway. What's behind that? >> 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 DataSync, 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. Today we have 10's of thousands of customers that are using Gateway to do their back-ups, do archiving, or in some cases, use it as a target to replace their on-premises storage, with cloud backed 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 can not 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 us to do even more workloads on the Gateway. This announcement will allow customers to have a highly available Gateway, in a VMware environment. With that, their workloads can continue running, even if one of the Gateways goes down, if they have a hardware failure, a networking event, or software error 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 anything customers have to do, any prerequisites they have. How does it all fit? >> Customers can essentially use this in their VMware H.A. 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. The Gateway integrates into the VMware H.A. environment. It builds up a number of health checks, so we keep monitoring for the application up-time, network up-time, 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 one of the benefits. But maybe talk about some of the other benefits. >> We saw a large number of our on-premises customers, especially in the 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're 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 cache 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 attach more storage to it, or move it to a higher resourced VM, and they can continue to get the performance they need. 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 Gateway's as well. So it's one pane of control. They can get CloudWatch health reports on their infrastructure on-prem. >> And if course it's cloud, so I can assume this is a service, I pay for it when I used it, I don't have to install any infrastructure, right? >> So the Gateways, 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 transfer through the Gateway, and it's capped at $125 a month. And you just pay for whatever storage is consumed by the Gateway. >> When you talk to senior exec's like Andy Jassy, always says "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 really hear much talk about hybrid. You talked to your customers and say, "Hey, we want to connect our on-prem to the public cloud." You're bringing services to do that. Asa, thanks so much for coming to theCUBE. Appreciate it. >> Thank you, thanks for your time. >> You're welcome. And thank you for watching everybody. This is Dave Vellante with theCUBE. We'll be back right after this short break. (upbeat music)

>>day, Volonte. And welcome to the Cuban special presentation here from Amazon in Boston. We're talking storage, really? A group of intelligent people here in the storage world and really excited to have Kevin Miller. You got hard news today around this. Think of replication. Time >>control. Yeah. >>What? What's that all about? What should we know about S3 replication? What problems isn't solving for customers? Why'd you do this? >>Yeah, absolutely. So we're very >>pleased to announce the launch today of s three replication Time control. >>This is a >>future that a number of customers across really across the board, large enterprise as well as public sector customers have asked us >>for to really give >>them insight and confidence that critical data they need to have replicated will be done in the time frames that they require. So we're actually today offering industry first s L. A of 99.9% of data will be replicated with within 15 minutes when using replication, time control and really, most data is replicated within a matter of seconds. But then having that escalate to >>back up that promise. So >>we have a number of customers who >>use as three replication today. Both is in our cross region replication as well as same region replication. And so the >>use cases really >>span the gamut from customers were looking to just back up their data so they might make a copy into a lower cost storage class to have a backup of that data. A CZ well as customers that I want to have on always on disaster recovery site, where they can replicate the data and then have a live hot, ready to go replication in another region for disaster >>recovery. Okay, so let's double click on that a little bit. Cross region replication. C r R >>r r >>Tell us more about that. What should we know there? >>Well, see, you're ours. The >>capability we've had for a long time, and it's it's a really critical capability. Ah, building block that our customers used to ensure that they can maintain a second copy of the data in another region. And so, and with Sierra are they can not only replicate the data, but they can actually replicate it into a completely different accounts so they can actually have two accounts that with potentially different access control and different administrators who can access those accounts. So they really have confidence that even if there was a knish you with their application in one region, that they can immediately begin operating in that second region. And so so we have customers who use replication for backup recovery, but also for a ZAY said sort of live replication to have ah always on D our site. >>Okay. And you also just recently announced the same reason. Region replication tell us more about that. >>Well, same region replication. It provides many of the benefits of cross region replication, but does so within one region. So we do have some customers >>who would like to, for example, make a backup copy of their data into a different account. But they >>need to >>maintain that data within the same geography, but perhaps for data, sovereignty reasons, or that they just want Thio, keep everything in one region but still have that second copy. So with same region replication, it's really just one parameter in the replication configuration, and they have all the benefits that we have historically had with across region application. >>So, Kevin, what should we be watching for? Just in terms of s three replication. Replication generally is very important for customers, really. But what's next for Amazon as three replication that we should be paying attention to? >>Well, you know, we, uh we think the >>replication today has ah range of different differentiated capabilities in terms of the ability to replicate on a tag level or replicate subset of the data. And so, you know, >>really, our goal with replication is just to make it as easy as >>possible for customers. Thio configure the replication they need Andi provide that flexibility while also providing the sort of the fully managed experience that we have with us three where you don't have to build your own software to do it. So, >>you know, we're gonna be continuing >>to work with customers. Uh, Thio simplify the things that they need to d'oh to configure replication for their different use cases. >>Let's talk about that customer angle you're just thinking about as three replication time control. What you expect customers to be saying about this, how they're going to be using it. What kind of problems are they going to be solved? >>Yeah, well, we have customers, you know, particularly those >>in regulated industries or in government public sector where they are under very stringent requirements. Thio be able to prove that they always have a second copy of the data and and this is the way that they can do that. So we air, you know, working with customers in with some of the tightest regulations you can imagine who were saying, Yeah, this is what I need with this capability Now I can I can watch it. I can monitor it. Ah, and I and more importantly, I know that the data is there for them. They can't start processing the data until they know that that second copy is is made. So they're using the replication time control metrics to really look at it real time and say, Okay, I'm ready to begin processing this data because I know I have both copies made. >>Well, it's great to see you guys really expanding the storage portfolio again. It started very simple, but you get that flywheel effect going. It's it's a critical part of the value chain. So congratulations. I'll give you last word, and >>I I just think that >>obviously that s three stands for simple storage service. And despite all of the flexibility and capability we're trying to build in. At the same time, simplicity is job number one for us. And so >>we're just >>really excited about with replication. Time control. Uh, we think that we've built something that both hits, that that mark of being simple but also provides just a lot of capability that that otherwise, you know, would take quite a bit of effort. >>Always a balance. Right? The simple you make it that war customers wants. Kevin, thanks so much for coming on The Cube. Really appreciate it. >>Absolutely. Thanks for having me. >>You're welcome. And thank you for watching everybody, right? Right back, Right after this short break.

>>This is Dave Violante. We're here at a W s with the Keep talking About Storage palate cars. Here is the director of product management for E B s Elastic block storage. Welcome. Good to see again. >>Nice to see it. If >>so, let's talk about E b s. You know, it all started with us. Three and course customers demand Maur. What do we need to know about E b s? Like, what are the options that you provide? Give us the late low down. >>Yeah. So the way to think about block storage in the AWS eight abreast constructors. Really two kinds of offerings. One is around instant storage, which is a form of block strategy. And then you have a block started service, which is E. B s Andi. Sort of. The key thing they're from customer standpoint of different shit between the two is if you warn your storage like cycle to be coincident with your instance like cycle, then you use instant surgeon. That's why we see a lot of our customers using since storage, because they won't want that experience if you want. On the other hand, it's storage life cycle that's different from your instance life cycle. So the ability to change instances, the ability to grow size is the ability to to take back ups. Then you want to choose the obvious experience. And there we have a series of volume types that customers can consume. Be a GP two we have, I want. We have our stream volumes, which are a C one and C one. >>So she's when you talk to customers of block stores. What did they tell you that they most care about? >>Yeah, uh, it is. It is a Lord around performance. It is a lot around. Availability is a lot on your ability. He's a fuse. Those of the core characteristics that that customers care about earlier this year as an example, one of the things that we launched for customers was the ability to encrypt their volumes by default on you. Say, Well, why is that important? So security becomes a big concern for customers a day as they think about their environment and with encryption by default. We just made it simple. With a single setting, you can now, at an account level, ensure that all your PBS volumes created from that point on our fully encrypted. >>Okay, let's talk about snapshots. So how o r r. Snapshots in the cloud? Different. And how are your customers using stamps? >>Yeah, that's great. Great. Great. Cigarette in tow. Common conversation. Customers who are coming from on premises environment are used to snapshots is being sort of this copy on right type attack volumes. The way to think about aws snapshot. Devious snapshots in particular are really to think of them as backup. And so that is the one sort of key thing that I always tell customers is to think of what we call snapshots, really as backups. Especially if you're coming from a non premises environment. >>Okay, um, how about things you're doing to really improve? Uh, EBS snapshots. I mean, is it more performance? Is it making simple Are expanding use cases. Yeah. >>Yeah. Let's talk about the use case scenario Is that that snapshots get use, and snapshots are really the underlying storage for water called Amazon machine images. Our aim eyes. That is how snaps that is, how our instances boot. That is also the way that customers create CBS Williams from, so you can create an obvious volume from a snapshot. So on that on that particular use case, one of the things that we're we're now launching is a capability via calling far snapshot restored. So you can now take a knee, be a snapshot and then within an availability is soon. Make it such that you can. You can now launch volumes from it without encountering any Leighton sing and back on DDE. That we think is a tremendously powerful capability for customs. Because if you can, it takes away all the undifferentiated heavy lifting that they had to do in order to lure the data from the snapshot into the volume completely out of the picture and allows them to focus on getting their data to their applications. That's right. >>All right, we'll give you the last word. Final thoughts on the innovations that you had. Congratulations on all the hard work. >>No, actually, this is the team has done a tremendous amount of work in art launches. Couldn't be happier to see this in the hands of customers. We look forward to seeing what they build from from the things that we provided them so excited to see that happen. >>That's actually quite amazing. It started all very simple with us three. And now we've seen service is just become more granular. Higher performance. Really meeting customer demands. She's thanks so much. Thank you so much. All right. Thanks for watching. Your body will be back right after this short break.

>>so we're seeing the dramatic impact of cloud in the market place. But you know what's interesting? We're just getting started. Very high growth rates and cloud huge, huge market. But there's so much more to go. There's a multi trillion dollar marketplace. When you talk to Andy Jassy, he's got huge visions in the cloud. And so the storage portfolio has to emerge beyond just S three e. B. S. You've gotta have all kinds of other capabilities and service is which we've seen today in the announcements here. Here it's storage day. We're going to see Maur it reinvent. We're very excited. The Cube is gonna be there and where it again. We're just seeing the innovation from Amazon continuing now really trickled down to the storage of the big take away from me was it's not only the benefits of cloud being able to reduce all that non differentiated heavy lifting to use that popular term. It's really about the integrations. So I can now take advantage of all the innovations around new availability zones and and and the regional capabilities that Amazon brings the machine intelligence capabilities. I can take advantages of new service's around functions or lander what many people call serverless. So whatever the Amazon engine does now, all these storage service is Come take advantage of that. And that really to me was when the light bulb went off. We talked about this flywheel effective cloud. It's just getting Maur and more and more momentum. So So check out these announcements, Dig in deep, check out the queue. But AWS reinvent will be there and thank you for watching everybody.