Build modern

applications
on AWS
Manage less. Build fast. Innovate more.

1
INTRODUCTION

Modern applications are changing how

you deliver customer value
In the next few years, organizations will build over 500 million new apps,
more than the number developed in the previous 40 years combined.¹ Many
are building them the hard way as they struggle to find a balance between
managing technology and delivering new features.

While the cloud promises agility, that doesn’t happen automatically. As

organizations look to accelerate innovation, get more out of their data, and
build new customer experiences, they need to modernize the way they build
and operate applications. Modern applications are built with a combination
of modular architecture patterns, serverless operational models, and agile
developer processes.

In this eBook, we’ll guide you through the three pathways that will help
lay the foundation for modern application development in your own
organization. We’ll also explore how modern application development with
AWS can help your organization innovate, reduce costs, accelerate time to
market, and improve reliability.

1
IDC PlanScape: Connected Cloud Architectures to Enable the Future of Digital Infrastructure, October 2020 2
MODERN APPS EMPOWER DIGITAL INNOVATORS

Innovation means listening

to your customers
In a recent Vision Report, Digital Rewrites the Rules of Business, Forrester
Research defines the customer-centric mindset of a digital innovator. The core LISTEN
mission of these modern disruptors is to:

“…Harness digital assets and ecosystems to continually improve

customer outcomes and, simultaneously, improve operational
excellence…by applying digital thinking to customer experiences,
operations, ecosystems, and innovation.”

INNOVATION
Focusing on your customer means making business decisions by working
backward from your customer’s point of view. It means constantly evolving FLYWHEEL
products and services to better deliver the outcomes that delight customers.
And it means listening to what your customers truly care about so that
you can continue inventing and iterating on their behalf. This is called the
“innovation flywheel.” ITERATE EXPERIMENT

The basic idea is that the driver for any innovation begins with customer
demand, improves with customer feedback, and repeats constantly (and
profitably) until the demand changes and the whole cycle begins again. The
faster your teams can get your own innovation flywheel spinning, the better
you’ll be able to build modern applications and the more you will stand apart
from competitors.

3
MODERN APPS EMPOWER DIGITAL INNOVATORS

Building modern applications on AWS will get you to market faster.

By speeding up the build-and-release cycle and offloading operational

50%
overhead, developers can quickly build new features. You’ll increase
innovation with a modular architecture that lets teams experiment with
individual application components without risking the entire application.
By automating test procedures and monitoring at every stage of the of information and communications
development lifecycle, you’ll improve reliability. And you’ll improve total technology is predicted to be directly
cost of ownership (TCO) with a pay-for-value pricing model that reduces allocated for digital transformation by 2023
the cost of over-provisioning or paying for idle resources.

To build modern applications, you may need to reconsider the foundation

on which they are built. While shifting this architecture may be dramatic
at an organizational level, the process doesn’t need to be brutal. Many
organizations take an inspired leap to build new modern apps in the
cloud, but plenty of others take a hybrid approach, often taking a team-
by-team and workload-by-workload journey, moving opportunistically
one step at a time.
67%
of executives believe they must pick
up the pace to remain competitive

90%
of new applications are predicted
to be cloud-native by 2025

4
DIGITAL INNOVATORS

Through our experience building applications for Amazon.com and from

serving millions of AWS customers, we’ve observed three pathways
that organizations can take for translating their vision of application
modernization into a reality, generating value for business in the process.

1 Re-platform to managed container services. Organizations already

running containers on-premises or thinking about moving applications
to containers can re-platform those workloads to container services on
AWS to simplify operations and reduce management overhead costs,
such as orchestration and infrastructure provisioning.

2 Build new apps on serverless architecture. As organizations build

new applications or features, we recommend that they use serverless
technologies and purpose-built databases to maximize agility, as well as
advanced development tools to accelerate development.

3 Transform to a Modern Dev+Ops model. To create a cultural shift

to build modern applications at scale, organizations can leverage
DevOps services and tools while maintaining a high bar on security and
governance.

We’ll explore each pathway in more detail, demonstrating how each can
help lead to increased agility, lower costs, and building better apps that
support business success. While you can modernize applications from
any starting point, the outcome needs to be the same: applications that
are secure, reliable, scalable, and quickly available for your customers and
partners at the onset.

5
MODERN APPLICATIONS IN PRACTICE

Three pathways to modern application Pathways to modern applications

development
Modern application development is a powerful approach to designing,
1 Re-platform to managed container services
building, and managing software in the cloud. This proven approach
increases the agility of your development teams and the reliability
2 Build new, secure apps on serverless architecture
and security of your applications, allowing you to build and release
better products faster. From our experience helping organizations of
3 Transform to a Modern Dev+Ops model
every kind build applications, we’ve identified three solution pillars of
modern application development to help you on your journey toward
modernization.

6
RE-PLATFORM TO MANAGED CONTAINER SERVICES

Re-platform to Containers are a lightweight and portable way to container service helps to reduce operational burden
run and deploy applications. Containerizing existing while improving scalability, reliability, security, and
managed container applications is often a first step in an organization’s availability. With managed container services on
services modernization journey. If you are considering moving AWS, you no longer have to worry about managing
your applications to containers, you would benefit containers. Instead, you can focus your resources
from re-platforming those workloads to AWS on education for the upskilling you need to develop
managed services like Amazon Elastic Kubernetes modern applications with serverless computing.
Service (Amazon EKS) or Amazon Elastic Container
Service (Amazon ECS) with AWS Fargate. A managed

7
CUSTOMER SNAPSHOT

“AWS Fargate Spot has reduced our unit costs and

reinforced our business case to migrate to AWS. We’re
delivering more value for our dollars each month with
this optimization. Returning value to our shareholders
through increased efficiency is core to our company-wide
mission.”
– Tim Treston, Senior Manager, Cloud Business Office, Vanguard

Since beginning its migration to AWS in 2015, The Vanguard Group has seen managed container orchestration service, alongside AWS Fargate. AWS
significant benefits. For example, Vanguard’s use of AWS services removed Fargate is a serverless compute service that removes the need to provision
the need for its IT department to manage servers. As a result, developers and manage Amazon Elastic Compute Cloud (Amazon EC2), a web service
have more time to build innovative, new microservices and enhance current that provides secure, resizable compute capacity in the cloud. And by taking
applications, increasing Vanguard’s speed to market from three months to advantage of a new purchase option for AWS Fargate, the financial services
24 hours. firm reduced its unit costs by 50 percent.

But speed to market is not the only benefit the company has seen. Vanguard See the full story »
opted to use Amazon Elastic Container Service (Amazon ECS), a fully

8
BUILD NEW ON SERVERLESS

Modernizing app development is the adoption of services, practices, and Key considerations for building
strategies that enable developers to build more agile applications. And with scalable modern apps
the speed and reliability of modern infrastructure, developers can deliver
secure apps that scale from prototype to millions of users automatically, so Architectural patterns: microservices
they can innovate and respond to change faster.

Many modern applications are built serverless-first, a strategy that prioritizes Although your monolithic app might be easy to manage today,
the adoption of serverless services so customers can increase agility challenges often arise as you grow, including how to distribute
throughout the application stack. With serverless technologies, you no longer ownership of the app across your teams. You can build a strong
have to manage physical servers and you’ll benefit from automatic scaling, culture of ownership but still struggle to scale up if your application
built-in high availability, and a pay-for-value billing model. Instead of worrying architecture includes hard dependencies that prevent teams from
about managing and operating servers or runtimes, you can focus on product taking ownership of the final product. This is why we recommend
innovation while enjoying faster time to market. building microservices architectures for apps that grow and change
rapidly. Microservices are the architectural expression of a culture of
In addition, front-end web and mobile tools and services can be built on top ownership—they neatly divide complex applications into components
of AWS. The reliability of this infrastructure helps brands deliver secure, highly that a single team can own and run independently.
available apps that can scale automatically across the globe.
With a monolith, you have many developers all pushing changes
through a shared release pipeline, which causes friction at many points
of the lifecycle. During development, engineers need to coordinate
their changes to make sure theyʼre not breaking someone elseʼs
code. In order to upgrade a shared library to take advantage of a new
feature, you need to convince everyone else to upgrade at the same
time—a tough ask! And if you want to quickly push an important fix
for your feature, you still need to merge it with changes in progress.

After development, you also face overhead when youʼre pushing the
changes through the delivery pipeline. Even when making a one-line
change in a tiny piece of code, engineers need to coordinate their
changes ahead of time, merge their code, resolve conflicts within
releases, rebuild the entire app, run all of the test suites, and redeploy
once again.

9
BUILD NEW ON SERVERLESS

EVERYTHING VS. ONE THING:

With a microservices architecture, an application TWO TYPES OF APPLICATIONS
is made up of independent components that run
each application process as a service. Services
are built for business capabilities, and each
Monolith apps Do everything
service performs a single function. Because it
runs independently and is managed by a single Single app
development team, each service can be updated,
deployed, and scaled to meet the demands for Must deploy entire app
specific functions of an application. For example,
One database
an online shopping cart can be used by many more
users during a sale. Microservices communicate Organized around technology layers
data with each other via well-defined interfaces,
using lightweight APIs, events, or streams. Our State in each runtime instance
customers are increasingly relying on event-driven
One technology stack for entire app
architectures—those in which actions are triggered
in response to changes in data—to improve
application scalability and resiliency while also
reducing costs.

Microservices Do one thing

Minimal function services

Deployed separately, interact together

Each has its own datastore

Organized around business capabilities

State is externalized

Choice of technology for each microservice

10
CUSTOMER SNAPSHOT

Centrica is a British multinational energy and services company that Building on that success, other teams in the organization have now also
was looking to decrease its costs and increase its agility by changing the adopted the approach—serverless is now common across the organization.
way its application was architected. The company opted to refactor to a
With serverless, Centrica is able to see and respond to customer issues in
microservices architecture and adopt a serverless strategy to achieve
real time, something it had not been able to do before.
those goals.

In order to change the organization, Centrica set up a serverless working Watch the video »
group with representative teams and started building a pilot together.

11
BUILD NEW ON SERVERLESS

Serverless operational model How do we define serverless at AWS?

As serverless as possible When we say serverless, we mean it’s the removal of the undifferentiated
heavy lifting that is server operations. This is an important distinction because
As your architectural patterns and software delivery processes change, you
it allows you to focus on the building of the application rather than the
will probably want to adopt an operational model that enables you to offload
management and scaling of the infrastructure to support the application. The
any activity that isn’t a core competency of your business. To gain agility
four tenets of a serverless operational model are:
that can enable rapid innovation, we recommend building microservices
architecture, operating and deploying software using automation for things
like monitoring, provisioning, cost management, deployment, and security 1 No server management – There is no need to provision or maintain
any servers. There is no software or runtime to install, maintain, or
and governance of applications. Choosing a serverless-first strategy—opting administer.
for serverless technologies wherever possible—enables you to maximize the
operational benefits of AWS.
2 by
Flexible scaling – Your application can be scaled automatically or
adjusting its capacity through toggling the units of consumption
With a serverless operational model, you can build and run applications and
(e.g., throughput, memory) rather than units of individual servers.
services without provisioning and managing servers. This eliminates server
management, provides flexible scaling, enables you to pay only for value, and
automates high availability. This model lets you build and manage the aspects 3 Pay for value – Instead of paying for server units, pay for what you
value—consistent throughput or execution duration.
of your application that deliver customer value without having to worry about
the underlying detail.

Whether you are building net-new applications or migrating legacy, building with
4 Automated high availability – Serverless provides built-in availability
and fault tolerance. You donʼt need to architect for these capabilities
serverless primitives for compute, data, and integration will enable you to benefit since the services running the application provide them by default.
from the most agility the cloud has to offer.

A serverless operational model is ideal for high-growth companies that want to innovate quickly.
Serverless enables teams to move even faster and keep a laser focus on the activities that
differentiate your business so you can speed up your innovation flywheel.

12
BUILD NEW ON SERVERLESS

Leveraging AWS Lambda and managed container services

on AWS
With the rise of containers and serverless computing, instances are no
longer your only cloud computing option. Choosing the optimal compute
for your modern application starts with exploring several questions. Does
self-managing infrastructure improve your business results? Do you have the
expertise to do it? And will the extra effort ultimately drive value?

Increasingly, customers are choosing to offload server management by

adopting container services like Amazon ECS and Amazon EKS or event-
driven serverless compute services like AWS Lambda.

In reality, most customers use a combination of both. About 80 percent of

AWS containers customers have also adopted AWS Lambda.² Leveraging
both options has its benefits, including fully managed services that have deep
integration with AWS infrastructure, support for a wide range of use cases,
abstraction from complexity, and a broad ecosystem of partners.

2
Datadog State of Serverless, 2020 13
RE-PLATFORM TO MANAGED CONTAINER SERVICES

So how do you frame the decision?

Customers choose AWS Lambda when they have teams focused primarily on Customers often choose containers when they have existing containers
writing code and no limitations on existing instances or container platforms. investments, open-source preferences for Kubernetes, or specific
AWS Lambda offers the maximum abstraction from infrastructure, and so requirements for managing or configuring infrastructure. Containers are the
it enables customers to release fastest, which is why new applications are a most popular way to package code and are a great choice for modernizing
great fit for AWS Lambda. legacy applications.

AWS Manages Customer Manages

Least
AWS Lambda Data source integrations Application code
Serverless functions Physical hardware, software, networking,
facilities

Provisioning

AWS Fargate Container orchestration, provisioning Application code Management tasks

What you manage

Serverless containers Cluster scaling Data source integrations

Physical hardware, host OS/kernel, Security config and updates, network

networking, facilities config

Amazon ECS/ Container orchestration control plane Application code Work clusters
Amazon EKS Physical hardware, networking, facilities Data source integrations Management tasks
Container management
Security config and updates, network
as a service
config, firewall

Amazon EC2 Physical hardware, networking, facilities Application code Security config and updates, network
Most Infrastructure as a service config
Data source integrations
Provisionining, managing scaling and
Scaling
patching of servers
Management tasks

14
CUSTOMER SNAPSHOT

“We believe our technology running on AWS will allow the

growing number of elderly people to live independently at
home—where they are happier.”
–Robin Mysell, CEO, ATF Services and AbiBird

AbiBird is a wholly owned division of ATF Services, an Australian group of AbiBird also uses container services on AWS, hosting a public API on Amazon
companies with 350 employees and contractors and 60 branches in Australia ECS and leveraging AWS Fargate to run its containers without the hassle of
and New Zealand. AbiBird offers a service consisting of infrared sensors administering its own fleet of virtual machines.
for homes, which help monitor the activities of elderly residents through a
Since launching this system on AWS in 2019, AbiBird has not had to raise a
smartphone-based app.
single support ticket, which enables the company to run efficiently with a
AbiBird was running on Microsoft Azure and found it was raising far too minimal amount of overhead support.
many support tickets with its cloud provider to keep its service running. The
company needed more stability and scalability. AbiBird moved to AWS and
See the full story »
now uses a combination of compute services based on its needs. It uses AWS
Lambda on the backend due to its ease of use and scalability, as well as for
the managed nature of the service.

15
CUSTOMER SNAPSHOT

One of America's most iconic food brands, Taco to focus less on managing servers and more on serverless services, Taco Bell is able to save on
Bell has over 7,000 restaurants in the U.S. During building business logic and data transformations upfront costs, start small and only pay for what
the COVID-19 pandemic, Taco Bell needed to to deliver real-time menu and restaurant is needed, and automatically scale as it consumes
rapidly shift to meet consumer demand for information to its delivery partners. “We have a more services.
delivery. According to Vadim Parizher, vice menu that is very complex and has to be shared
president of engineering and analytics, Taco Bell across multiple digital channels. Serverless fits
Watch the video »
runs nearly all of its infrastructure on Amazon that model really well,” says Parizher. By using
Web Services (AWS) and uses serverless on AWS

16
CUSTOMER SNAPSHOT

When COVID-19 hit, consumer habits literally latency, or scalability. Because with AWS Lambda, “Low latency is essential to the user
changed overnight. Coca-Cola responded rapidly that’s all built in. The new application launched experience, which is why we’re committed to
with a no-touch drink dispensing experience in just 100 days, and now more than 52,000 a serverless solution on AWS.”
to go along with its innovative Freestyle drink machines have the touchless capability.
– Michael Connor, Chief Architect, Coca-Cola Freestyle
dispensers. Coca-Cola opted to build with AWS
Watch the full story » Equipment Innovation Center
Lambda, and as a result, its team was able to
focus on the application rather than security,

17
TRANSFORM TO A MODERN DEV+OPS MODEL

Modern Dev+Ops is the combination of cultural philosophies, practices,

Developer agility: abstraction,
and tools that enables an organization to quickly and safely develop
software, release it to production, and maintain its target availability and automation, and standardization
performance.
Microservices architectures make teams agile and enable them to
AWS has identified a set of common, broadly accepted practices that, move faster, which means youʼre building more things that need
when adopted, provide a mechanism for building a high-performing to get released—great! However, you won’t get new features
DevOps organization. This approach takes a simple idea—continuous to your customers faster if your build-and-release process does
improvement—and applies it to everything in the DevOps lifecycle, from not keep up with your team’s pace. Traditional development
planning and code writing to deployment and monitoring. processes and release pipelines are slowed mainly by manual
processes and custom code. Custom code is ultimately a long-
We call this approach Modern Dev+Ops, and it’s centered around term liability because it introduces the possibility for errors and
bringing developers and operations closer by sharing operational tasks long-term maintenance. Manual steps—from code changes and
like compliance, observability, resilience, and infrastructure earlier into build requests to testing and deploying—are the greatest drag on
the development process and enhancing it with artificial intelligence and release velocity. The solution involves abstraction, automation, and
machine learning (AI/ML). standardization.

In order to speed the development process, abstract away as

much code as possible, particularly the lines of non-business logic
code, required to develop and deliver production-ready apps. One
way to do this is to employ frameworks and tooling that reduce
the complexity of provisioning and configuring resources. This
gives developers an ability to move quickly while also enforcing
best practices for security, privacy, reliability, performance,
observability, and extensibility throughout the development
process. Development frameworks give you confidence that your
architecture will support your business growth long term.

18
18
TRANSFORM TO A MODERN DEV+OPS MODEL

By defining your software delivery process through the use of best-practice

A bit more detail:
templates, you can provide a standard for modeling and provisioning all
infrastructure resources in a cloud environment. These “infrastructure
Continuous integration - (CI) is a software development practice
as code” templates help teams get started on the right foot because the
where developers regularly merge their code changes into a
template provisions the entire technology stack for an application through
central repository, after which automated builds and tests are run.
code rather than using a manual process.
Continuous integration most often refers to the build or integration
Through automation, you can create a repeatable motion that speeds up stage of the software release process and entails both an automation
your software delivery lifecycle. Automating the release pipeline through component (e.g., a CI or build service) and a cultural component (e.g.,
continuous integration and continuous delivery (CI/CD) helps teams release learning to integrate frequently).
high-quality code faster and more often. Teams that practice CI/CD ship
Continuous delivery - (CD) is a software development practice
more code, do it faster, and respond to issues quicker. In fact, according to
where code changes are automatically prepared for a release to
the Puppet 2020 State of DevOps Report, teams that employ these practices
production. Continuous delivery expands on continuous integration
have a failure rate that is five times lower, a commit-to-deploy rate that is
by deploying all code changes to a testing environment and/or a
440 times faster, and a rate of deployment that is 46 times more frequent.³
production environment after the build stage.
Most notably, teams that practice CI/CD spend 44 percent more of their time
creating new features and code instead of managing processes and tools. Learn how Amazon automates safe, hands-off
deployments »
CI/CD pipelines have become the new factory floor for building modern
applications. At Amazon, we started using CI/CD to increase release velocity,
and the results were dramatic—we have achieved millions of deployments
a year and we grow faster every year. To help companies benefit from our
experience, we built a suite of developer tools based on the tools we use
internally so our customers can deliver code faster.

3
Puppet 2020 State of Devops Report, 2020 19
CUSTOMER SNAPSHOT

With AWS, Lululemon Athletica can stand up development environments HyperTrack is a self-serve cloud platform for live location tracking
in minutes instead of days, automate its environments, and enable through apps. When it launched in late 2015, HyperTrack needed to
continuous integration and deployment. The Canadian company sells build a platform that could scale automatically to meet their anticipated
yoga-inspired apparel and other clothing at more than 350 locations growth without reducing the time their developers spent on building
throughout the world. Lululemon runs its dev and test environments—as new features.
well as an upcoming mobile app—in the AWS Cloud.
HyperTrack opted to use AWS Amplify for a mobile development
Lululemon decreased its time to build new production accounts from two framework and a serverless architecture in order to scale up and down
days to a few minutes, using AWS CloudFormation templates and AWS automatically without engineering intervention.
CodePipeline. With that increased agility, Lululemon dev teams can now
As a result, the company has realized a 30 percent cost savings
experiment and get to the best solutions rather than having to settle for
compared to the architecture they were using before we switched
what they have resources committed to.
to serverless. A big part of that savings comes from not needing
See the full story » operational resources to focus on server management. HyperTrack
saves 40 hours of work, every single week, while managing millions
of events.
“Any continuous integration and deployment pipeline should
be automated, easy to manage, and discoverable, and that’s See the full story »
exactly what we get using AWS. We get a level of simplicity
and transparency we simply couldn’t have in our previous on-
premises environment.”
– Sam Keen, Director of Product Architecture, Lululemon

20
TRANSFORM TO A MODERN DEV+OPS MODEL

Creating a culture of It makes product teams accountable for the for creativity, and develops a risk-taking culture
development of the whole product, not just a in an environment of trust.
ownership: manage piece of it.
less, innovate more with After more than a decade of building and
While embracing a culture of ownership is not
inherently technical, it remains one of the most
Modern Dev+Ops running the highly scalable web application challenging aspects of modern application
Amazon.com, we’ve learned firsthand the development. Empowering teams to become
Innovation ultimately comes from people, importance of giving autonomy to our teams. product owners involves changing the mindset
and so enabling your people to deliver better When we gave our teams ownership of the of your organization, the structure of your teams,
customer outcomes is where modern application complete application lifecycle, including taking and the work for which they are responsible.
development starts. We use the concept of customer input, planning the roadmap, and
“products, not projects” to describe how this For most organizations, IT falls into one of two
developing and operating the application,
impacts team structure. Simply stated, it camps. It is viewed as a strategic competitive
they became owners and felt empowered to
means that the teams that build products are weapon or, more commonly, as a cost center
develop and deliver new customer outcomes.
responsible for running and maintaining them. necessary to support business growth.
Autonomy creates motivation, opens the door

Building a culture of innovation

1 Start with the customers – Every innovation should start with a customer need and ultimately
delight your customers. Prioritize relentlessly to focus on customer demand.

2 Hire builders and let them build – Remove any obstacles that slow the process of building and
releasing products and features for customers. The faster you iterate, the faster your flywheel spins.

3 Support builders with a belief system – Don’t pay lip service to innovation—live and breathe
innovation in all areas of the business, from leadership to sales to support.

21
CLOSING SUMMARY

Manage less, Why build modern applications on AWS?

innovate more
Faster to By speeding up the build-and-release cycle and See the proof:
Modern applications create competitive Market offloading operational overhead, developers Urbanbase launches
differentiation by enabling rapid can quickly build new features. Automated test services 20x faster with
innovation. By adopting services, and release processes reduce error rates, so AWS
practices, and strategies that underscore products are market-ready faster.
speed and agility, you can shift resources
from business as usual to differentiating
activities with deep customer value. Increase With a modular architecture, changes to any See the proof:
You can experiment more and turn Innovation individual application component can be made iRobot uses AWS Lambda
ideas into releases faster. You can quickly and with a lower risk to the whole and the AWS IoT platform
foster an environment where builders application, so teams can experiment with new to manage its Roomba
spend more time building and less time ideas more often. robotic vacuum cleaners
managing. Modern applications are how
organizations, including Amazon, innovate Improve By automating test procedures and See the proof:
with speed and agility. Reliability monitoring at every stage of the development Siemens decreases
lifecycle, modern applications are reliable at customer control system
deployment. Any issues can be evaluated and alerts by 90 percent and
addressed in real time. reduces infrastructure
costs by 85 percent

Improve TCO With a pay-for-value pricing model, modern See the proof:
applications reduce the cost of over- Save up to 80 percent
provisioning or paying for idle resources. on app maintenance
By offloading infrastructure management, with AWS Lambda
maintenance costs are also lower.

22
CLOSING SUMMARY

Start your application modernization journey

Replatform to Managed Container Build New Modern Applications Transform to a Modern Dev +
Services with Serverless Technologies and Ops Model
Tools
80% of all containerized applications running in Save up to 80% time on maintenance and 60% of teams with higher evolved
the cloud run on AWS* 84% of all Kubernetes approximately 70% on development when DevOps practices fully remediate security
workloads in the cloud run on AWS* adopting a serverless-first strategy for building vulnerabilities in less than a day#
modern applications**

Resources Resources Resources

Amazon ECS workshop Innovator Island - Serverless web application The Amazon Builder’s Library
Amazon EKS workshop development workshop. Build a serverless web AWS DevOps services
AWS AppRunner workshop app video tutorial.

Recommended Training (Classroom) Recommended Training (Classroom) Recommended Training (Classroom)

Running Containers on Amazon Elastic Advanced Developing on AWS DevOps Engineering on AWS
Kubernetes Service (Amazon EKS)

Recommended Training (Online) Recommended Training (Online) Recommended Training (Online)

Amazon Elastic Container Service (ECS) Primer Architecting Serverless Solutions Getting started with DevOps on AWS

Learn more about building modern applications on AWS g

Talk to an expert to implement the best practices of modern application development g
Connect with an AWS partner to accelerate your modernization projects g

* Source: Nucleus Research

** Source: Deloitte 23
© 2021, Amazon Web Services, Inc. or its affiliates. All rights reserved. # Source: 2020 DORA state of DevOps Report