 Have a welcome back to theCUBE's cover of DockerCon main stage. I'm John Furrier, host of theCUBE. We're here with Chubhub Rao, senior manager, product manager at AWS and the container services. Chubhub, thanks for coming on theCUBE. Hi, thank you very much for having me excited to be here. So Ashley, we've been, we're doing a lot of coverage with AWS recently on containers, cloud native, microservices, and we see you guys always at the events. But tell me about what your role is in the organization. Yeah, so I did the product management and developer advocacy team in the AWS container services group where we focus on elastic containers. And what I mean by elastic containers is that all the AWS opinionated out of the box solutions that we have for you, like ECS and AppRunner and Elastic Beanstalk. So where we bring in our services in a way that integrates with the AWS ecosystem and my team manages the product management and speaking to customers and developers like you all to understand how we can improve our services for you to use it more seamlessly. So I mean, I know AWS has a lot of services that have containers involved with the Manus Vada integration within the cloud, it's cloud native, Amazon is cloud native, it's going to get at AWS. If I was a new customer, where do I start with containers? If you had to give me advice and then where I have a nice roadmap to grow within AWS? Yeah, I know that's a great question. A lot of customers ask us this. Do you recommend that the customers choose whatever is the best fit for their application needs and for their operational flexibility? So if you have an application which you can use a pretty abstracted like end-to-end managed by AWS service, we recommend that you start at the highest level of abstraction that's okay to use for your application. And that means something like AppRunner where you can bring in a web application and run it like end-to-end. And if there are things that you want to control and tweak, then we have services like ECS where you get control and you get flexibility to tweak it to your needs. Be it needs of like integrations or running your own agents and running your own partner solutions or even customizing how it scales and all the characteristics related to it. And of course we have, if a lot of our customers also run capabilities. So that is a requirement for you if your apps are already packaged to run easily with the Kubernetes ecosystem, then we have a guest for you. So like application needs, the operational, how much of the operations do you want us to handle or how much of it do you want to actually have control over? And with all that, like the highest level of abstraction so that we can do the work on your behalf which is the goal of AWS. We always hear that all that heavy lifting, undifferentiated heavy lifting on you guys handle all that. Since you're in product management and I have to ask the question because you guys have a little bit longer view as you have to think about what's on the roadmap. What type of customer trends are you seeing in container services? So that's, we see a lot of trends about customers who want to have the plugability for their services of choice and our EKS offerings actually help in that. And we see customers who want an opinionated, give me an out-of-the-box solution rather than building blocks and EKS brings you that experience. The newest trends that we are seeing is that a lot of our customer workloads are also on their data centers and in their on-prem like environments be it branch offices or data centers or like in other areas. And so we've recently launched the anywhere offerings for you. So EKS anywhere brings you an experience for letting your workloads run in an environment that you control where we manage the scaling and the orchestration and the whole like monitoring and troubleshooting aspects of it, which is the new trend which seems to be something that the customers use as a way to migrate their applications to the cloud in the long-term or just to get, you know, they're the same experience and the same like constructs that they're familiar with come onto their data centers and their environments. You know, Shuba, we hear a lot about containers becoming standard in the enterprise now mainstream but customers when we talk to them they kind of have this evolution. They start with containers and they realize how great it is and they become container full, right? And then you start to see kind of them trying to evolve to the next level and then you start to see EKS come into the equation. We see that in cloud native. Is EKS a container? Is it a service? How does that work with everything? So EKS is a Amazon managed service container service where we do the operational set up, you know, upgrades and other things for the customer on that we have. So basically you get the same properties APIs that you get to use for your application but we handle a little bit of the integrations and the operations related to keeping it up and running with high availability in a way that actually meets your needs for the applications. And more and more people are dipping their toe in the water as we say with containers. What are some of the things you've seen customers do when they jump in and start implementing that kind of phase one containers? Obviously there's a lot of head room beyond that. As you mentioned, what's the first couple of steps that they take they jump in? Do they, is it a learning process? Is it serverless? Where has the connection points all come together? Right, so I want to say that no one solution that we have fits all needs. Like it's not the best case, the best thing for all your use cases and not for all of your applications. So how it all comes together is that AWS gives you a great ecosystem of tools and capabilities. Some customers want to really build the, casual themselves with each of the Lego block and some customers want it to be a ready made thing. And I want, one of the things that I speak to customers about is to rethink which of the knobs and controls do they really need to have? Because none of the services we have is a one reader. Like there is always flexibility and ability to move from one service to the other. So my recommendation is to always start with things where Amazon handles many of the heavy lifting operations for you. And that means starting with something like serverless offerings. Where like for example, with Lambda and forget we manage the host, we manage the patch and we manage the monitoring. And that would be a great place for you to use ECS offering and basically get into an experience in a couple of days. And over time, if you have more needs, if you have more control, if you want to bring in your own agents and whatever else you have the option to use your own EC2 instances or to take it to other parts of the AWS ecosystem where you want to tweak it to your needs. Well, we're seeing a lot of great traction here at DockerCon and all the momentum around containers. And then you're starting to get into trust in security supply chain as open source becomes so more exponentially in growth. It's growing like crazy, which is a great thing. So what can we expect to see from your team in the coming months as this rolls forward? It's not going away anytime soon. It's going to be integrated and keep on scaling. What do we expect from the team in the next month or so, a couple of months? Security is our number one job. So you will continue to see more and more features capabilities and integrations to ensure that your workloads are secure. Availability and scaling are the things that we do as keep the lights on. So you should expect to see any, all of our services growing to make it like more user friendly, easier simple ways to get the whole availability and scaling to your needs better. And then like, very specifically on a touch on a few services, AppRunner. Today we have support for public facing web services. You can expect that the number of use cases that you can meet with AppRunner is going to increase over time. You want to invest into making it AWS end to end workflow experience for our customers because that's the easiest journey to the cloud. And we don't want you to actually wait for months and years to actually leverage the benefits of what AWS provides. If you look at ECS already launched out, like, you know Fargate and Fargate and anywhere to bring you more flexibility in terms of easier networking capabilities more granular controls in deployment and more controls to actually help you plug in your preferred solution twice. And in ECS, we are going to continue to keep the Kubernetes versions and bring simpler experiences for you to use. A lot of nice growth there containers, EKS, a lot more goodness in the cloud. Obviously we have 30 seconds left. Tell us what you're most excited about personally and what should the developers pay attention to in this conference around containers and AWS? I would say that AWS has a lot of offerings, but you know, speak to us, like come and come to us with your questions or anything that you have, like in terms of feature requests, we are very, very eager and happy to speak to you all. You know, you can engage with us on the containers roadmap, which is on GitHub or you can find many of us in events like this AWS summits and in our DockerCon and many of the other meetups. I'll find us on LinkedIn, we are always happy to chat. Yeah, always open, open source. Open source meets cloud scale, meets commercialization, all happening, all great stuff. Shubha, thank you for coming on theCUBE. Thanks for sharing. We'll send it back now to the DockerCon main stage. I'm John Furrier with theCUBE. Thanks for watching.