 It's not like you guys at Johnny come lately on Amazon Web Services. Can you just quickly give some color on the relationship with AWS and what it means with respect to HANA Enterprise Cloud? Absolutely, and I think there is part on here. I think the relationship between SAP and Amazon Web Services dates quite some years back. All the way to Amazon Web Services being participant, especially with their teams, their architects sitting side by side with SAP in Maldon to conduct a lot of these validations, to conduct a lot of these certifications that took place. So I think that that level of collaboration is basically almost coming to a fruition, if you may. When you look at some of these offerings that come out there, I think also the way that you see instance sizes developing, whether it's compute, otherwise, that's been built specifically for those kind of HANA workloads, that clearly will happen only if these two companies are working extremely closely together, but not just from a go-to-market perspective and more importantly from an engineering and from a development perspective. And having that voice in within the HANA Development Organization ensures that we are actually representing the voice of the customer around consumption patterns that we know for a fact are going to take place only in the 12th. And congratulations on that Amazon relationship. So it's good to know, it's not a one-truth, and just to clarify, I want to get to see if you can just verify my, as a source, since I have you on the phone here and you're Senior Vice President, is it true? I've heard, I just want to confirm with you, I've heard that the Amazon relationship has always been there for four years, but a lot of the stuff that's come out of the announcement that you announced this week was already going on independently with customers and third parties. You guys are now formalizing that with official teams and joint development. Is that correct? So I think the, like I mentioned, the engineering relationship between SAP and Amazon is based back for quite some time now. I think we would not have made decisions. In fact, I mean, even before the HANA Enterprise Cloud managed services offering on AWS was offered, based on these certified workloads, based on these certified instance sites, there was an option for customers to go and deploy some of their SAP systems, not just testing development, but also product assistance directly in the Amazon Web Services Cloud. What the HANA Enterprise Service, what the HEC offering on Managed Public offers is, it's now SAP putting some of these workloads directly in the AWS environment and helping the customers manage all of this from an end-to-end perspective. So that's the key. So the difference, if I get this right, is before it wasn't fully end-to-end because you didn't have your piece there, but you were there anyway with the engineers. So is that, and that might get in that right, because it seems like you've always been there with the engineering, but now there's so much more formal relationships. And that should ease things up. Is that correct? Yeah, so I think the difference in the past, John, was it was pretty much up to the customer to manage the entire transition, whether it goes around provisioning, whether it goes around administration, whether it was around patching, whether it was around upgrades, all of that stuff was pretty much entirely done in the domain of the customer. The customer was responsible for doing that themselves. With this offering, what SAP is doing, is SAP is selling the customers, we are going to stand up these environments for you in AWS and we are going to manage it end-to-end for you. And that includes the entire slew of managed services that goes around managing a HANA-based system. And we obviously, as SAP, as a native vendor of these products, have a very specific point of view on what constitutes or what makes a best run HANA application. And just to close the loop on that, and just to close the loop on that, what you just said is what you call managed public cloud model. That's the offering. Okay, great. Well, thanks for clarifying that. I wanted to make sure I got that on the record. I think that's kind of what, I thought you said it the best. I'll just plagiarize what you just said and put that in my write-up on that. So appreciate, I'll source you on that, of course. Final question, what's the vibe of the show? Every year I come out of SAP, this is our first year we haven't been there in seven years, it's usually a theme pops up. You mentioned convergence. Is that the top-level theme? And the second part of the question is, Hasso always kind of has a great motivating, relevant speech, but he also kind of connects the dots, or puts the dots out there to be connected. He kind of teases next year in his vision. He always has his point of view, which a lot of people watching the industry as kind of a bellwether for next year. So what's the theme this year and what's the bellwether vibe that Hasso's telling you? I think you recognized a couple of things that stood out for me. And I think, by the way, it was one of the most brilliant or most inspiring keynotes that I heard personally from Hasso. I think the one thing that stood out for me is the amount of time or the amount of effort and the way that we actually build user interfaces. I think there is absolutely a radically different approach type thing that we need to take. We need to be spending far, far more time building out those user interfaces and making it a lot more intuitive and absolutely seismic-straight simple. I think that's where we need to focus on number one. The other key item that he did touch upon was the topic of integration. And I think the new reality is the one of a multi-cloud solution, the hybrid reality. And I think for all of these things to come together in a sensible fashion, integration becomes more and more key. And I think he even quoted something to the extent saying almost about 40% of our development folks are now working directly on some of these integration topics, which is, I think, a testament to the scale and the value that integration is going to play, especially when it talks about both SAP and non-SAP applications going forward. So I think these are kind of one or two items that stood out for me. And of course, the big announcement specifically around SAP Leonardo and the tool sets, obviously the story around the big data and analytics. I think these were the key standouts, especially for me, as part of the keynote. Sanjay, thank you for spending the time this morning here on the West Coast, but also early in the early morning for you guys, or late morning for you guys in Orlando. Thanks for sharing the insight from on the ground in Orlando at SAP. Sapphire are now Sanjay Kulkarni, who's the global head of architecture and advisory for SAP HANA Enterprise Cloud. Congratulations on the Amazon announcement that adds to your portfolio of cloud. And congratulations on the CenturyLink Cisco Alliance as well, we covered that as well. Thanks so much for spending the time. This is the CUBE coverage of SAP HANA Day 3 from Palo Alto and Orlando. We'll be back with more coverage after this short break. Stay with us.