Homepage Rankings and Research Companies Channelcast Marketing Matters CRNtv Events WOTC Cisco Partner Summit Digital 2020 HPE Zone The Business Continuity Center Enterprise Tech Provider Masergy Zenith Partner Program Newsroom Hitachi Vantara Digital Newsroom IBM Newsroom Juniper Newsroom Intel Partner Connect 2021 Avaya Newsroom Experiences That Matter Lenovo GoChannelFirst The IoT Integrator NetApp Data Fabric Intel Tech Provider Zone

50-Plus Biggest AWS Announcements From re:Invent 2020

CRN breaks down more than 50 new product and service announcements from the top-ranked cloud provider’s annual partner and customer conference that continues in January.

Back 1 ... 5   6   7   8   9   ... 26 Next

AWS Proton

AWS Proton automates infrastructure provisioning and deployment tooling for developers’ serverless and container-based applications.

“AWS Proton is a big leap forward for customers and for Mission, delivering the first fully managed deployment service for containers and microservices,” said Simon Anderson, CEO at Mission, a Los Angeles-based managed services provider and AWS Premier Consulting Partner.

Jassy called the new application management service a “game changer” for managing the deployment of microservices.

“If you look at containers and serverless, these apps are assembled from a number of much smaller parts that together comprise an application,” Jassy said. “It‘s actually hard. If you look at each of these microservices, they have their own code templates, they have their own CI/CD pipelines, they have their own monitoring, and most are maintained by separate teams. It means that there’s all these changes happening all the time from all these different teams, and it’s quite difficult to coordinate these and keep them consistent. It impacts all sorts of things, including quality and security. There really isn’t anything out there that helps customers manage this deployment challenge in a pervasive way.”

AWS’ team answered that with AWS Proton, which is now in preview. Jassy explained how it works.

“A central platform team or anybody central to an application will build a stack, and a stack is really a file that includes templates that use code to define and configure AWS services using a microservice, including identity and including monitoring,” he said. “It also includes the CI/CD pipeline template that defines the compilation of the code and the testing and the deployment process. And then it also includes a Proton schema that indicates parameters for the developers that they can add -- things like memory allocation or a Docker file…basically everything that‘s needed to deploy a microservice except the actual application coder.”

Then that central platform team will publish the stack to the Proton console. When a developer is ready to deploy their code, they‘ll pick the template that best suits their use case, plug in the parameters they want and hit deploy.

“Proton will do all the rest,” Jassy said. “It provisions the AWS services specified in the stack using the parameters provided. It pushes the code through the CI/CD pipeline that compiles and tests and deploys the code to AWS services, and then sets up all the monitoring and alarms.”

The AWS Proton console lists all the downstream dependencies in a stack, according to Jassy. If an engineering team makes some a change to the stack, they know all the downstream microservices teams that need to make those changes and can alert them and track whether the changes are made, he said.

Back 1 ... 5   6   7   8   9   ... 26 Next

sponsored resources