 From the Aria Resort in Las Vegas, it's theCUBE. Covering AWS Marketplace, brought to you by Amazon Web Services. Hey, welcome back everybody. Jeff Frick here with theCUBE. We're at AWS re-invent in Las Vegas. I don't know, 50,000, 60,000. I can't wait till the number comes in. There's a lot of people at this event. Been coming for years. We actually have nine days of coverage here spread out over three sets in four different locations but we're kicking it off tonight at the AWS Marketplace and Service Catalog event here at the Aria. Come on by. There's no lines over here. I'm sure there's giant lines over at the Sands. And we're excited to see an old friend and make a new friend and talk about service catalogs from some of the experts. And Dave Wright, Chief Innovation Officer from Service Now has been on many, many times. Dave, great to see you. No, good to be here. And our new friend, Misanya Scott, Chief Senior Business Development Manager at AWS Service Catalog. Hi, how are you? Thank you. So there's a lot of talk about Service Catalog. We know about the Service Now, Service Catalog. We've got the AWS Service Catalog but now you guys have brought these two things together. Yes. Why did you bring it together? How did it happen? How did we get here today? So at AWS, 95% of our features are based on what customer feedback. And so we were listening to our customers tell us that, hey, it's your innovation in AWS Service Catalog where you provide the governance, the guardrails, the launch constraints is great but we already have a Service Catalog with our ITSM tools, such as Service Now and how can we federate that in just the details and the information into Service Now so we can do it in one place? So our developers don't have to swivel chair between two different systems. So we listened to that feedback, got requirements, started a proof of concept and then we built on it and we're now on our third iteration. And Dave, what were you hearing from your side of the chair? So we were getting, customers were coming to us saying they wanted a similar experience so they were getting used in a regular Service Catalog. So they wanted a unified experience. They wanted the ability to have governance and control over what was happening. But most importantly, they wanted us to integrate because they'd say, hey, you two are both strategic platforms for us. We don't want to go the last mile and have to write the integration so you guys need to work together and sort it out. So it was very much customer driven. It was customers that were saying we want you guys to work together more closely. I love it. I just love the customer centric nature because we hear it over and over again. And this is kind of a great example of a real instance. And you didn't really care per se whose was kind of on top. You know, what are they logging into initially? You just wanted to get the integration done. And it sounds like today, right now it's a ServiceNow login and then it integrates with the AWS Service Catalog underneath. Right, so for the AWS Service Catalog, we state the source of truth for all the resources, the products and the portfolios. And then we sync to ServiceNow Service Catalog through their scheduled job process. And we exposed products that the ServiceNow administrator wants their end users to see. So they can order an iPhone and now they can order a web server. And where's the identity? Is that in the ServiceNow platform now in terms of the rights and access that an individual person has inside of your catalog? In ServiceNow, where you correlate the identities in AWS to a role in ServiceNow. So that's that. And then the best thing about the app is that the ServiceNow end user doesn't have direct access to the AWS console. They just order what is a compliant secure product that they need to have. And then even in the AWS console, the connection only gives the end user role that's assumed access to the AWS Service Catalog. So not even direct resources to EC2 or S3. And so what that enables is that segregation of duty. And so we put the permissions on the launch constraints and then they deploy products and then you can give the evidence in an audit to what you provision. And then where is this kind of in the life cycle, you said? I think we're kind of past PLCs getting into production. Yeah, our customers are starting to move to production, doing PLCs, giving us feedback. And as they give us more feedback, we're creating more releases. We launched our third iteration of features last Monday, the 19th. And what we did was we integrated not only just AWS Service Catalog but the ability through AWS Systems Manager to do SSM actions. So if you provision a web server, now you can start, stop, reboot it. And so, and then once you do that, we create a change in Service Now's IT change management. So we're moving more from provisioning as well as into operational actions as well. And that's what was great for us was if you've got that point of initiation where you know something's happening, we can then update the CMDB in real time. We can start looking at software asset management so we can see what's deployed. And then we've also found this great use cases where we can look at how we actually map the service to then be able to use Amazon's Cloud migration products to be able to speed up migrations as well. Yes, yes. And so customers are not only just provisioning storage or EC2s, but anything from a cloud formation template, workspace, an Amazon workspace. You can also send those requests through Service Now. We've got a lot of feedback on that. We have sessions and builder projects today to re-invite that are showing how that works. So begs the question, obviously, down the road, will kind of the priority switch from the customer perspective? Will Service Now be integrated in through the marketplace of the service catalog and people access it through that way? I think there's no reason why it couldn't be at some point. The only challenge we have at the moment is obviously people using the service catalog as a provision, all kinds of things, as well as AWS components. But if you were a core AWS shop and that was what you were using everything for, there's no reason why you couldn't flip that around. I would just think of what screen are you on all day, right? That's the, everybody wants your attention. They want that screen. And if that's your work screen, that's your work screen. So now that you're opening this up, really adds a whole lot of power to a Service Now work screen that wasn't there before. Well, we've always focused on kind of changing what the employee experience was like to just try and give them, ironically, an Amazon-like experience, because we've always said, it's easy for me to order stuff in the real world for me to just get something from Amazon. Why couldn't I have exactly that same experience when I wanted to order any piece of IT equipment, whether it be physical, virtual, peripherals, whatever? So that's why we're trying to change the experience. But it's funny that it's come through that full circle of everyone going, ah, it'd be good if it was like that and then we end up working with these guys anyway. So did you get a cake? I get a cake. I've seen mini-cakes in my career, but no, I think you need to send me a cake. You didn't do a go live cake, you're right. I know, I know. Yeah, you got to get a go live cake once you get that first wand up and official and ready to roll. We got to do that and take a picture. You can see your partner manager. It's one of the coolest things of the Service Now culture, I have to say. Yes, yes. All right, so any final words on this partnership beyond just continuing to make the improvements, get closer into production and build more functionality, anything you want to highlight as you turn the calendar on 2018 and 2019, just around the corner. So we're looking to get feedback more on not just provisioning, but going through other management tool services and trying to see what the customers are looking for. So that's one of those key features is building bigger, not just AWS service catalog, but a connector between the two platforms so that we can continue to create that synergy. Excellent. All right, well, thanks for taking a few minutes of your day and we'll see you, I think in May, usually when we see AWS all, I think we had like six shows this year. You guys just keep rolling. So thanks for taking a few minutes and have a terrific show. Oh, great to be here. Thank you. All right, she's Masonia. He's Dave, I'm Jeff. You're watching theCUBE. It's the AWS Marketplace Service Catalog Enterprise Hub at the Aria. Come on by. Thanks for watching.