0% found this document useful (0 votes)

7 views150 pages

Advanced+Migrating+to+AWS+-+Student+Guide

The AWS Solutions Training for Partners focuses on advanced strategies for migrating to AWS, emphasizing re-hosting and re-platforming methodologies to modernize enterprises. Participants will learn to utilize tools like CloudEndure Migration Factory and AWS App2Container for large-scale migrations and containerization. The course includes hands-on labs and covers prerequisites, migration strategies, and the benefits of enterprise modernization.

Uploaded by

burhanamet919

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

7 views150 pages

Advanced+Migrating+to+AWS+-+Student+Guide

Uploaded by

burhanamet919

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 150

AWS Solutions Training for Partners

Advanced Migrating to AWS –

Technical

1
Module 1

Introduction
In this course, you will learn how to:

Course objectives • Identify how re-host and re-platform migration

strategies apply to customer migration use cases
• Describe how to plan and perform large-scale
rehosting migrations
• Identify scenarios for modernizing enterprises
through migrating to reliable, secure, cloud
infrastructures
• Identify scenarios for migrating applications to run in
container environments
• Use CloudEndure Migration Factory (CEMF) to
automate large-scale migrations that involve
rehosting
• Use AWS App2Container (A2C) to migrate
applications to container-based platforms

In this course, you will learn how to:

• Identify how re-host and re-platform migration strategies apply to customer

migration use cases
• Describe how to plan and perform large-scale rehosting migrations
• Identify scenarios for modernizing enterprises through migrating to reliable,
secure, cloud infrastructures
• Identify scenarios for migrating applications to run in container environments
• Use CloudEndure Migration Factory (CEMF) to automate large-scale migrations
that involve rehosting
• Use AWS App2Container (A2C) to migrate applications to container-based
platforms
Course overview

1. Introduction
Lab: Setup

2. Modernize the enterprise

3. Implement AWS CloudEndure Migration Factory
Lab: CloudEndure Migration Factory

4. Containerize applications with AWS App2Container

Lab: App2Container

5. Course review and additional resources

The course includes the following topics and activities:

• Module 1 - Introduction
• Lab 1 - Setup
• Module 2 - Modernize the enterprise
• Module 3 - Implement AWS CloudEndure Migration Factory
• Lab 2 - CloudEndure Migration factory
• Module 4 - Containerize applications with AWS App2Container
• Lab 3 - App2Container
• Module 5 - Course review and additional resources
Objectives

In this module, you will learn how to:

• Identify course goals and objectives, agenda, and prerequisites

• Describe re-host and re-platform migration methodologies
• Identify migration opportunities to help customers realize a lower total cost of
ownership (TCO) and overcome the migration bubble
• Navigate the hands-on labs environment

In this module, you will learn how to:

• Identify course goals and objectives, agenda, and prerequisites

AWS Solutions Training

AWS Technical for Partners (STP):
Accreditations

Professional Foundations (Technical)

Assess AWS Well-Architected
Framework, TCO, business

Previous knowledge
AWS STP:
AWS Cloud Economics case
Well-Architected Best
Practices (Technical) Mobilize Application discovery,
Courses

Landing Zone,
database migration
AWS STP: Migrate and
AWS Certified CloudEndure Migration
Migrating to AWS Modernize
Solutions Architect
Certifications

(Technical)
Associate
or
AWS Certified AWS STP:
SysOps Administrator Containers on AWS
Associate (Technical)

These are the prerequisites for this course:

• Completed AWS Solutions Architect Associate or AWS SysOps Administrator

Associate certifications
• Received AWS Technical Professional accreditation AWS Cloud Economics
accreditation
• Completed the following courses: STP: Technical Foundations; STP: Well-
Architected Best Practices – Technical, STP: Migrating to AWS – Technical and STP:
Containers on AWS – Technical

• Previous knowledge – Able to:

• Assess (AWS Well-Architected Framework, TCO or business case)
• Mobilize (application discovery, landing zone, database migration)
• Use CloudEndure Migration
Common migration strategies

In this section, you learn about how to apply the rehost and replatform
methodologies to real-life situations. You also learn how this is different from
refactoring. This section is just a preview (level-set) of what is covered later in the
course. The 7 R’s of migration are reviewed for reference.
Migration strategies review (match)

A. Lift and shift

1 REHOST
2 minutes
2 REPLATFORM

3 REPURCHASE
Type in chat
B. Rewrite
application
4 REFACTOR

5 RETIRE

C. Lift, tinker,
and shift
6 RETAIN

7 RELOCATE
© 2021 Amazon Web Services, Inc. or its affiliates. All rights reserved. 8

In this exercise, match the phrase on the left with the type of migration on the right.

Starting with lift and shift, identify the correct migration strategy.

Migration answers:
A. Life and shift → 1. Rehost
B. Which migration requires rewriting or redesigning the application? → 4. Refactor
C. Which migration is a lift, tinker, and shift that might require operating system (OS)
changes or updated versions? → 2. Replatform
Migration strategies
4 Manual Install Config Deploy
Rehost
1 Automated Migration
tools

Determine Modify
Replatform
Discover platform infrastructure

Validation

Transition
2 3
Assess/ App code Production
Refactor Redesign ALM/SDLC Integration
Prioritize development
Determine
Buy
Repurchase Install/setup
COTS/SaaS

5 Relocate Automated

Retain
• COTS: Commercial “off-the-shelf” software
Retire • SaaS: Software as a service
• ALM: Application lifecycle management
© 2021 Amazon Web Services, Inc. or its affiliates. All rights reserved. • SDLC: Software development lifecycle 9

In previous courses, you learned about the 7 R’s of migration: Retire, Retain, Relocate,
Rehost, Repurchase, Replatform and Refactor. The illustration shows you how the
migration strategies fit in this course. This course focuses on rehost and replatform
strategies.

1. To develop a migration strategy, it is critical that you collect application portfolio

data and rationalize it into the 7 Rs framework. Using this method, categorize the
applications in your environment and their interdependencies. Include each
application’s technical complexity and business criticality and how to migrate
each application or set of applications.

2. Assessing the application portfolio and determining the application migration

pattern for all applications is a critical step in planning and performing a
successful migration.

3. Chief information officers (CIOs) from large enterprises who were early cloud
adopters warn against the all-in, Refactoring approach to take advantage of the
cloud. Refactoring applications can result in lengthy design processes before
rewriting and moving the first workloads to the cloud.
4. Based on the CIOs’ advice and other customer successes, we advise you to take
advantage of significant opportunities to re-host or lift and shift applications. Re-
hosting lets you migrate quickly, gain cloud experience, and see cost-savings. You
can always refactor after you lift and shift and have the cloud experience to
jumpstart the re-factoring effort.

5. Relocate is an emerging migration strategy, especially for customers who must

maintain large hybrid environments. You can relocate applications based on
VMware and container technologies to Amazon Web Services (AWS) quickly and
with minimal effort and complexity.

9
Help customers realize cost savings

Payback period
Cost

Migration bubble
Current /
TCO Do nothing
(with growth)
Cost optimizing /
modernizing

AWS
environment
Time

In this time-to-value chart, you can see that customers realize savings by performing a
lift-and-shift as fast as possible.

While the data center is being migrated, customers start to see an AWS bill. It appears
to be an increase in costs with limited value. You can help customers overcome this
migration bubble by migrating as much as possible quickly. This helps them realize a
lower TCO and prepare for further modernization.

In upcoming modules, you will learn about steps to modernize the enterprise as you
rehost compute resources to the AWS Cloud that take advantage of a modern,
secure, reliable infrastructures. Additionally, there are steps that are better to
perform after cloud residency is proven. It’s not an either/or proposition – sometimes
it’s both.
Activity: Experience and feedback

Classroom feedback:

• What is your experience with AWS? 2 minutes

• What are your goals for the course?
• What type of migration situations do you face?

This is an open-ended activity for the instructor to learn the students’ knowledge,
experience, and background.
Lab 1: Setup

1. Access AWS accounts.

20 minutes
2. Navigate and use the lab environment.
3. Open the lab instructions by following this link:

Hands-on lab

https://advancemigrationtraining.s3.amazonaws.com/public/index.html

For the initial lab setup, you access AWS accounts and learn how to navigate and use
the lab environment.

For setup lab instructions, see:

https://advancemigrationtraining.s3.amazonaws.com/public/index.html.
Summary

In this module, you learned how to:

• Identify course goals and objectives, agenda, and prerequisites

In this module, you learned how to:

• Identify course goals and objectives, agenda, and prerequisites

Modernize the Enterprise

Welcome to Module 2: Modernize the Enterprise.

Objectives

In this module, you will learn how to:

• Define enterprise modernization and its benefits

• Describe modernization as a continuous cycle
• Identify options for modernizing applications
• Modernize enterprise systems with rehosting
• Modernize applications with containers
• Identify applications for containers
• Describe how to host and run container-based applications
• Explain how to prepare for a migration

In this module, you will learn how to:

• Define enterprise modernization and its benefits

What is enterprise modernization?

• Maximizes resiliency, engineering
efficiency, and business agility – with
Architecture operational excellence
• Combines modern infrastructure,
Enterprise architecture, and organizational patterns
modernization • Replatform or refactor

Organizational
Benefits
patterns • Increases uptime, streamlines fixes
Infrastructure • Improves customer experience
• Reduces effort to support
© 2021 Amazon Web Services, Inc. or its affiliates. All rights reserved. 16

Modernization is the process of progressively transforming applications so customers

can achieve the benefits of running in the cloud. Benefits include availability,
scalability, business agility, and cost optimization.

Modernization applies to infrastructure as well as applications. Application

modernization requires a modern infrastructure that provides a secure and flexible
operational framework. Modernizing only applications can lead to higher overall costs
and negatively impact performance and quality.

The combination of applications and infrastructure improves the quality of business

processes and provides high availability and agility. Modernizing applications as part
of migrating to AWS is a multidimensional approach. It is the combination of efforts
across infrastructure, organizational patterns, and architecture that drive the
maximum benefits of digital transformation.

Benefits of enterprise modernization include:

• Increases uptime and streamlines the processes for fixes

• Improves response times and customers’ experiences
• Reduces effort to support by reducing reliance on aging systems that are expensive
to run and hard to maintain.

16
Innovation flywheel
Feedback
Gain availability, scalability,
business agility, cost optimization

• Track metrics to collect and analyze

feedback
Innovation • Fine-tune applications – always
flywheel evolve
Experiment Ideas • Go to market with new offerings
• Fund experimentation and new ideas

The innovation flywheel illustrates how businesses can operate and optimize
iteratively.

Businesses that increase their speed of innovation and stay competitive must
modernize their applications for their business. They also must maximize value as
they modernize their applications.

To increase speed and agility, businesses must:

• Track metrics – Businesses can collect and monitor log files and analyze feedback.
The goal is to resolve issues before they impact the business. The more efficiently
businesses collect and analyze feedback, the more readily they can react to their
customers.
• Fine-tune applications – Businesses improve by proactively monitor their
applications end-to-end. Applications should continuously evolve. This is an
iterative process.
• Go to market – Businesses that regularly have new ideas to market are more
successful.
• Fund experimentation and new ideas – By reducing costs, business can spend
more on innovation.
Options

Migration
automation
tools

Rehost

Replatform Infrastructure

Refactor Integration

Businesses can modernize in a few ways. Here’s one view of what the process can
look like in real life.
As a first step, assess the application portfolio and determine the migration patterns.
Migration approaches can be combined and optimized by using automation.
This diagram shows a lift-and-shift approach that enables a business to migrate
efficiently, gain cloud experience, realize cost-savings, and proceed to refactoring
efforts.
It positions the rehosting and replatforming activities at the beginning. By employing
automation tools (covered later in this course), you can migrate servers to the AWS
Cloud as quickly as possible. After servers and services are resident in the cloud, you
can refactor the applications that benefit most from technologies such as
microservices and containerization.
Sample solution
AWS Cloud

Amazon
EC2
Users Amazon Elastic Load Amazon
CloudFront Balancing RDS

Amazon
EC2

Rehost Replatform
• Rehost to resilient, secure networks
• Replatform critical components
• Minimize changes
© 2021 Amazon Web Services, Inc. or its affiliates. All rights reserved. 19

This solution shows a basic approach to modernization. The migration process

combines rehosting and replatforming with minimal changes.

• Rehost – Migrate existing servers to Amazon Elastic Compute Cloud (Amazon EC2)
instances
• Replatform – Move the database infrastructure to Amazon Relational Database
Service (Amazon RDS)
• Infrastructure changes – Add Amazon CloudFront and Elastic Load Balancing to
provide scalability and resilience to the rehosted applications and servers

By migrating existing applications and services to Amazon EC2 instances, customers

gain the benefits of reliable, scalable computing in a secure network. They will not
have to deconstruct their applications, which refactoring sometimes requires.
Modernize with containers

One way to modernize applications is to run them in containers. In this section, you
learn about containerizing applications.
Why containers

Implement leading technology for cloud-native applications – use the

same technology for existing applications

Deliver applications efficiently

Keep applications agile and portable

Provide standardized packaging

Reduce risks – defined and managed as code

A common approach to accelerate application delivery and reduce costs is to use

container technology. Containers can be more effective, agile, and deliver
applications more quickly.

By containerizing existing applications, customers can use the same technology for
applications they migrate. It allows customers to achieve a higher level of agility while
also updating the skills of their teams with one of the latest technologies.

Businesses know that getting software products and services to market faster
translates into increased market share. Using containers can help enterprises
modernize legacy applications and create new cloud-native applications. When used
with DevOps and agile practices, containers provide an option for development and
operations teams who are under pressure to adapt to the growing business needs.
They can use containers to deliver applications quickly.

Container frameworks, such as Docker, provide a standardized way to package

applications — including the code, runtime, and libraries — and to run them across
the entire software development lifecycle, regardless of the environment.
Containers can also be considered less risky. A primary reason is because containers
can be defined as code. Containers package code with the configuration files for
building the container and the dependencies it needs to run in any environment.
Containers also help streamline testing.

21
Container benefits

Develop and deploy efficiently to

Agility achieve business goals

Build and operate with cloud-

Enterprise DevOps native tools

Enable portable, scalable, and isolated

Portability and isolation application deployment

Reduce IT overhead, optimize

Operational efficiency compute infrastructures

Containers provide several benefits for modernizing:

• Agility – Development methods are evolving. Developers are shifting to agile

methods and DevOps, They are using continuous integration/continuous
deployment (CI/CD) systems. Containers are lightweight, portable, and can be used
to wrap code and push it through new software pipelines.

• DevOps – DevOps brings software developers and IT operations closer together to

increase collaboration. This allows teams to release software more efficiently.
DevOps engineers create services and process automation to allow developers to
focus on creating code and getting it into testing and deployment as quickly as
possible. The goal is to achieve this in an automated way without additional
human overhead. Containers are useful in DevOps because they promote
infrastructure as code. They package code with configuration files for building the
container and the dependencies it needs to consistently run in any environment.
Note that enterprise DevOps does not happen because of containerization;
containerization can facilitate enterprise DevOps.

• Portability – Container images are governed by the Open Container Initiative (OCI).
The OCI container image specification defines container image formats. This allows
a compliant container to be portable across all major, compliant operating systems
and platforms without artificial technical barriers. You can deploy applications that
run in containers in a scalable, isolated way by employing services that manage
containers.

• Operational efficiency – With appropriate training and support, customers can save
money by containerizing instead of a lift and shift to a virtual machine (VM).
Containers and virtual machines have similar resource isolation and allocation
benefits, but function differently. Containers virtualize the operating system
instead of hardware. They are more portable and efficient and take up less space
than VMs. Container images are typically tens of MBs in size. Containers can
handle more applications and require fewer VMs and operating systems.

22
Containerized example
AWS Cloud

Users Amazon Elastic Load Amazon Amazon

CloudFront Balancing Elastic RDS
Container
Service

Replatform/
Replatform
Refactor

• Migrate to resilient, secure networks

• Refactor and containerize to gain agility and cost savings
• Replatform critical components, such as databases
© 2021 Amazon Web Services, Inc. or its affiliates. All rights reserved. 23

In this example, an application that previously required compute services and

dedicated servers now runs in a container managed by Amazon Elastic Container
Service (Amazon ECS). Since the database is replatformed to Amazon RDS, data is
accessible by the application. By using Amazon CloudFront and Elastic Load Balancing,
the application benefits from a modernized infrastructure that makes it scalable and
globally available.

By containerizing and deploying applications in the AWS Cloud, customers can:

• Migrate to resilient, secure networks

• Refactor and containerize to gain agility and cost savings
• Replatform critical components, such as databases, for more cost savings
Containerization complexity
Time/effort
to migrate
Attributes of application to migrate

Package or source install, single process, single file or folder,

static files secrets, HTTP/S, web interface, open-source license

Unattended install, multiple processes, several files, folders,

network secrets, TCP/UDP, services, background processing,
scheduled jobs, agent-daemon, proprietary source license

Interactive install, self-modifying processes, data

everywhere, dynamic secrets, IPsec (isolated), desktop client,
restrictive license
© 2021 Amazon Web Services, Inc. or its affiliates. All rights reserved. 24

The effort to refactor or containerize existing applications depends on the attributes

of the application to be modernized. Attributes can include:

• Package or source install, single process – These are attributes of applications that
are easy to containerize.
• Unattended install, multiple threads – Applications with these attributes are more
difficult to containerize.
• Interactive install, self-modifying processes – Applications with these attributes are
difficult or impossible to containerize.

Applications with open-source code that store secrets in a single static file are easier
to migrate than applications with proprietary or no source code that stores secrets in
several places.

You will learn about these elements in detail later in this course.
Get started

Once you identify a migration method, the next step is to complete pre-migration
tasks.
Premigration tasks

Ensure that a landing Complete an initial

zone is ready, including portfolio assessment
networking, server
authentication, and
logging

Group servers and Grant permissions to AWS

applications into Professional Services or an
migration waves AWS Partner to run the
migration

Before the migration process begins, your customer must complete key tasks. They
include:

• Ensure that a landing zone is ready, which includes networking (e.g., routing, DNS,
and firewalls), server authentication, and logging.
• Complete an initial portfolio assessment
• Group servers and applications into migration waves
• Grant permissions to AWS Professional Services or to an AWS Partner to run the
migration
Review

Question 1 Question 4

Question 2

Question 3 Proceed to Summary

Choose the option that matches the activity you want to perform or choose Proceed
to Summary to continue to the next section of the course.
Question 1

What are key elements of enterprise modernization?

1 minute
A. Allow enhanced security, reliable networks, and operational
efficiency
B. Combine modern infrastructure, architecture, and
organizational patterns Type in chat

C. Perform well-architected migrations to positively impact

performance of the business process
D. Use cookie-cutter approaches that leverage fast-paced
innovation to deliver agile IT processes

What are key elements of enterprise modernization?

Question 1 answer

What are key elements of enterprise modernization?

A. Allow enhanced security, reliable networks, and operational

efficiency
B. Combine modern infrastructure, architecture, and
organizational patterns (Correct)
C. Perform well-architected migrations to positively impact
performance of the business process
D. Use cookie-cutter approaches that use fast-paced
innovation to deliver agile IT processes

B. Combine modern infrastructure, architecture, and organizational patterns

Question 2

What are some benefits to modernizing applications?

1 minute

Type in chat

What are some benefits to modernizing applications?

Question 2 answer

What are some benefits to modernizing applications?

• More uptime
• Streamlined fixes
• Improved response times
• Improved end-user experience
• Reduced headcount to support
• Less reliance on systems that are expensive to run, hard to maintain, and
difficult to find employees to support

Here are some key benefits of modernizing applications:

Which step in the innovation flywheel helps

businesses resolve issues before they impact the
1 minute
business?

Type in chat

Which step in the innovation flywheel helps businesses resolve issues before they
impact the business?
Question 3 answer

Which step in the innovation flywheel helps

businesses resolve issues before they impact the
business?

Track metrics to collect and monitor log files and

analyze feedback.
The more efficiently businesses collect and analyze
feedback, the more responsive they can be to their
customers’ needs.

What step in the innovation flywheel should businesses take to resolve issues before
they impact business and react quickly to customers?

Track metrics to collect and monitor log files and analyze feedback. The faster
businesses collect and analyze feedback, the quicker they can respond to their
customers.
Question 4

What are the attributes of applications that are

easier to migrate to containers?
1 minute
• Installation methods
• Application modes
• Storage Type in chat
• Security, authentication, connectivity
• Networking
• User interface
• Source license

What are some attributes of applications that are easier to migrate to containers?

• Installation methods
• Application modes
• Storage
• Security, authentication, connectivity
• Networking
• User interface
• Source license
Question 4 answer

What are some attributes of applications that are

easier to migrate to containers?
• Installation methods: Package or source installer
• Application modes: Single process
• Storage: Single file, single folder
• Security, authentication, connectivity: Static file secrets
• Networking: HTTP or HTTPS
• User interface: Web interface
• Source license: Open-source licensing

What are some attributes of applications that are suitable for containers?

• Installation methods – Package or source installer

• Application modes – single process
• Storage – Single file, folder
• Security, authentication, connectivity – Static file secrets
• Networking – HTTP/S
• User interface – Web interface
• Source license – Open-source licensing
Summary

In this module, you learned how to:

• Define enterprise modernization and its benefits
• Describe modernization as a continuous cycle
• Identify options for modernizing applications
• Modernize enterprise systems with rehosting
• Modernize applications with containers
• Identify applications for containers
• Describe how to host and run container-based applications
• Explain how to prepare for a migration

In this module, you learned how to:

• Define enterprise modernization and its benefits

Implement AWS CloudEndure

Migration Factory

Welcome to Module 3: Implement AWS CloudEndure Migration Factory

Objectives

In this module, you will learn how to:

• Describe the benefits of using automation to perform large-scale migrations
• Identify the tasks required to plan, test, perform, and switch to a large-scale
migration
• Describe a framework for large-scale migrations
• Describe the CloudEndure Migration Factory workflow
• Identify the steps to prepare, perform, and monitor an CloudEndure Migration
Factory migration

In this module, you will learn how to:

• Describe the benefits of using automation to perform large-scale migrations

• Identify the tasks required to plan, test, perform, and switch to a large-scale
migration
• Describe a framework for large-scale migrations
• Describe the CloudEndure Migration Factory workflow
• Identify the steps to prepare, perform, and monitor an CloudEndure Migration
Factory migration
Migration tasks

Typical tasks
• Verify prerequisites
• Install CloudEndure agents
• Verify replication status
• Launch servers for boot test
• Schedule application cutover time frame

While implementing migrations, the migration team runs typical, predefined tasks
that automate the migration process. These tasks can include:

• Verifying prerequisites – For example, identifying available storage space in root

and temporary drives, firewall ports, the version of Microsoft .NET running, and
Dynamic Host Configuration Protocol (DHCP) settings
• Installing the CloudEndure agent on source machines
• Verifying replication status – the ability of CloudEndure Migration to replicate
servers. This is unique to CloudEndure and potentially faster using automation
instead of checking each status individually.
• Launching servers for boot-up testing – Using automation to launch a few servers
together instead of launching one server at a time
• Scheduling a time frame for application cutover.
Migration at scale

Migrate thousands of servers

efficiently

Challenges:
• Multiple tools are not integrated
• Slow, cumbersome manual processes
can be error prone

Companies want to migrate their servers to AWS as efficiently as possible. This is a

complex job, especially if you want to migrate thousands of servers in a short period
such as 6–12 months. Large-scale migrations present challenges, such as:

• Multiple tools that are not integrated – Many tools support migration, such as
discovery tools, migration tools, and configuration management database (CMDB)
tools. They must be connected so data flows from one tool to another. However,
different tools use different data formats, which can make integration difficult. A
migration is more likely to be successful with integrated tools.
• Manual processes that are slow and hard to scale – Migrations involve many minor
tasks, and each task takes a few minutes to complete. A short time multiplied by
many instances can result in a long time. A migration is faster when tasks are
automated.
Migration activities

You learned about migration tasks and the challenges of migration at scale. This
section introduces the phases of activities you perform to complete a CloudEndure
Migration.
Migration phases

Build Validate Test Cutover

An at-scale migration with CloudEndure Migration involves four phases of activities,

each with several tasks, to complete. The phases are:

• Build
• Validate
• Test
• Cutover

Next, you learn about the steps in each phase and their functions.
Build phase
1 2 3

Install Push post-

Check source CloudEndure
prerequisites launch script to
agent on each source
source

The build phase has three main steps:

1. Check source prerequisites. Check the settings in the source machines, such as
required TCP port availability, free storage space in root and temporary drives, the
version of .NET running, and Dynamic Host Configuration Protocol (DHCP)
settings.
2. Install the CloudEndure agent. The agent software is installed on each in-scope
machine in the source infrastructure.
3. Push the post-launch script. This step is optional. Post-launch scripts help
automate OS-level activities after launching target instances. Example activities
include:
• Install and uninstall software
• Change DNS settings
• Update OS-level settings

Resource
• For more information about CloudEndure prerequisites, see:
https://docs.cloudendure.com/Content/Preparing_Your_Environments/Preparing_
Your_Environments.htm
Validate phase
1 2 3

Create local Perform

Monitor administrator CloudEndure
replication (optional) dry run

The steps in the validate phase are:

1. Monitor and verify replication. This step occurs when the servers are in the
correct state – when they can connect to the CloudEndure server and perform
continuous replication.
2. Create a local administrator in the source (optional). For Windows environments,
if a local administrator user is not available (for example, the password is not
known), create a temporary local administrator user. This user can log in to the
server for troubleshooting purposes. For example, the server cannot connect to
an authentication server, such as an Active Directory domain. For Linux
environments, a sudo user might have to troubleshoot issues that occur after
migration cutover.
3. Perform a CloudEndure dry run. The dry run feature lets you validate your
configurations in the YAML file. It can save time during cutover because syntax
errors can take time to troubleshoot. Using the – dry run parameter in the
script forces CloudEndure to update blueprints for the machines in the
configuration file and revert back. This ensures that CloudEndure accepts
blueprint updates during cutover.
Test phase
1 2 3

Perform
Test launch instance 2/2 Terminate
check test instances

The steps in the test phase are:

1. Verify the target machines by launching the Amazon Elastic Compute Cloud
(Amazon EC2) instances with CloudEndure test mode.
2. Perform 2/2 health checks (system status and instance status) on instances. This
step checks the system status and boot process for target servers.
3. Terminate the test instances. This activity terminates the tested instances to avoid
AWS charges.
Cutover phase
1 2 3

Shut down Launch Verify

server cutover applications

The steps in the cutover phase are:

1. Shut down servers at the source location. This step depends on the customer’s
requirements. Most customers shut down the source server during the cutover
window. Some prefer to stop the service to stop transactions from the clients
without completely shutting down the servers.
2. Orchestrate the CloudEndure cutover process. This includes retrieving target IP
addresses, updating DNS records, and verifying the target server connections.
3. Verify that all application servers are up and running.
Automate migrations with a
factory

In this section, you learn about automating large-scale migrations by using

CloudEndure Migration Factory.
Automation benefits

• High efficiency
• Less prone to error
• Large-scale migrations
with less effort
• Reduced cost

A complete lift-and-shift migration might require dozens of tasks in each phase. Each
task could take a few minutes to run. When run manually, tasks are prone to error.
They risk being missed, skipped, or run in the wrong order.

Automating migration tasks reduces manual operation. It removes the time between
tasks, making migrations more efficient. You can complete large-scale migrations with
less effort, which saves time and cost.
Automation example – 1

Automate CloudEndure agent installations

• One server: 5 minutes
• 100 servers, different platforms, manually: 500 minutes
• 100 servers, automated: 5 minutes

Automation scripts help you save significant time and effort with large-scale
migration tasks, as shown in this example.

Automate a CloudEndure agent installation for 100+ servers

Installing the CloudEndure agent on one server takes about 5 minutes. If you have
100 servers running Microsoft Windows and Linux for 10 different CloudEndure
projects, the process could take over 500 minutes. The agent on the source machines
can be installed in many ways. An automation script reduces the agent installation
time from 500 minutes to less than 5 minutes of operator time. It works for Windows
and Linux operating systems, and any target AWS account.
Automation example – 2

Orchestrate CloudEndure cutover

• Process involves checking status, updating

blueprints, launching servers, verifying job status,
and cleaning up server
• Automation manages the entire cutover process

This example describes how automation scripts help customers during the
CloudEndure cutover process.

Orchestrate the CloudEndure cutover process

This process involves many tasks, such as checking replication status, checking server
status, updating the blueprint, launching servers in cutover mode, verifying job
status, and cleaning up the server. It is a long process for one server. It could be an
enormous undertaking with hundreds of servers in a single cutover. One solution
automates and orchestrates the entire process for you.
Automation example – 3

Customer example: Migrated hundreds of

servers in one day
• 418 servers in 1 day
• One week later, 626 servers in one day

Tips
• Minimize network changes
• Automate as much as
possible
• Prepare application owners
© 2021 Amazon Web Services, Inc. or its affiliates. All rights reserved. 51

Automation scripts can help you save your customers’ time and effort.

Customer example
An AWS Partner used the Migration Factory to help a customer migrate 1,400 servers.
They successfully migrated 418 servers in one day, and 626 servers in one day, one
week later. You can migrate 600 servers in a few hours. Here are tips that can help
make that happen:

• Minimize changes, including IP and security groups

• Automate migration with CloudEndure Migration Factory
• Train application owners for running their applications in the cloud
CloudEndure Migration Factory (CEMF)

AWS solution powered

by CloudEndure

• Rehosting
• Integrates with AWS Managed Services
• Solves integration, automation, and
orchestration problems
• Offers simplicity, speed, and cost reduction

The CloudEndure Migration Factory (CEMF) is an AWS solutions implementation. The

solution is an orchestration platform powered by CloudEndure. It is integrated with
AWS Managed Services for rehosting servers to the AWS Cloud at scale.

CEMF offers the following benefits:

• Helps solve the integration, automation, and orchestration problems typically

encountered in large-scale migrations
• Offers simplicity, speed, and cost reduction to cloud migrations by automating
CloudEndure Migration activities.
Migration metadata pipeline
Pre-migration Discover Build Validate Test Cutover
Configuration
CSV file Management
Database Automation
API API API

Migration metadata integration pipeline

API-driven pipeline: Frontend UI + backend database

API API API

CloudEndure AWS Managed

Migration Services

CEMF includes a migration metadata pipeline tool and automation scripts. As shown
in the diagram, the metadata pipeline tool integrates with other migration tools and
scripts through Representational State Transfer (REST) APIs. This enables migration
metadata to flow from one tool to another to support end-to-end automation.

Currently, CEMF is integrated natively with CloudEndure APIs and the AWS Managed
Services workload ingest process. By integrating these tools and processes, CEMF can
automate migration tasks across multiple tools.

Reference
For more information about the CEMF migration metadata pipeline tool, see:
https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-factory-
cloudendure/metadata.html.
Migration Factory workflow

Cutover Build
Pre- Wave Post-
migration 0-n migration
Test Validate

Migration implementation

Follow this workflow when using Migration Factory for migrations.

1. Pre-migration. Prepare the implementation environment (covered in detail next).

2. Migration implementation. In this phase, you automate the migration activities
covered in the previous section:
• Build
• Validate
• Test
• Cutover
3. Post-migration. After the migration is complete, perform customer-specific tasks,
such as decommissioning source machines, updating the source CMDB, and
optimizing performance on target EC2 instances.
Premigration requirements

1. Complete AWS landing zone design

and build.
2. Complete portfolio assessment.
3. Complete wave planning.
4. Deploy migration factory to your
AWS account.
5. Increase Amazon EC2 limits in your
AWS account.
6. Have a CloudEndure account.
7. Prepare source environments.
© 2021 Amazon Web Services, Inc. or its affiliates. All rights reserved. 55

Before starting CloudEndure Migration Factory, you must meet these requirements:

1. Complete AWS landing zone design and build. The AWS infrastructure is ready
with a secure, cloud-based environment.
2. Complete portfolio assessment. This helps you estimate the level of effort and
costs associated with the migration and prioritize application migrations.
3. Complete wave planning. Split servers into groups of 25–35 servers and repeat
the migration activities.
4. Deploy the migration factory solution to your AWS account. You will learn more
about this later in this course.
5. Increase Amazon EC2 limits in the target AWS account to handle migrations.
Contact support for this request.
6. Register a CloudEndure account, Complete the setup so that you have
CloudEndure API tokens ready to use with the CloudEndure Migration Factory
solution.
7. Prepare your source environments, as described later in this module.
Deploy CloudEndure Migration Factory

Access a Launch AWS Create the first Build a Test solution

domain CloudFormation user in migration migration server by using
user with stack with an factory and automation
local admin automation update schema scripts
permissions template

https://docs.aws.amazon.com/solutions/latest/aws-cloudendure-migration-factory-solution/deployment.html

Before starting, a domain user is required for Windows and Linux (sudo permissions)
servers. The user must have local administrator permissions to the source servers.
Verify that you have the necessary permissions or coordinate with the appropriate
person in the organization with domain permissions before launching the solution.

Deploy the solution in an existing AWS account. To build CEMF, complete the
following steps:

1. Launch the AWS CloudFormation stack into your AWS account*. During the
launch, supply the stack name, application name, environment
name, version, security group ID (if not using the default security group),
and subnet ID (if not using the default subnet).
2. Create the initial user in migration factory, update the schema, and change the
default CloudEndure project name.
3. Build a migration server. The migration server runs the automation tasks. You can
build the server in the AWS Cloud or on premises. The migration server runs
Windows Server 2012 R2 or later. It’s where you install Python and the required
packages. Download the sample automation scripts from the GitHub repository
and customize the configuration to match the outputs that were produced by the
AWS CloudFormation deployment.
4. Test the solution using the provided automation scripts. To perform a test run,
you need a user with administrator permissions on the source servers. Conduct a
test run of the migration automation.

*CEMF can be installed into the target account or another management account
provided the administrator creates the appropriate AWS Identity and Access
Management (IAM) permissions to CloudEndure on the target account.

Resource
• For more information about CEMF deployment, see:
https://docs.aws.amazon.com/solutions/latest/aws-cloudendure-migration-
factory-solution/deployment.html

56
Prepare the source environment

• Create (or enable) a user capable of connecting to the servers

• Open the following firewall ports:
• TCP 443 outbound from the source server to the CloudEndure console
• TCP 1500 outbound from the source server to the CloudEndure replication
server
• Verify that Windows servers run .NET Framework 3.5 or later
• Verify that Windows servers have a least 3 GB of free space on drive C
• Configure the migration server’s network settings

To prepare the source environment, complete these tasks:

• Create (or enable) a user (or user in domain) that can connect to all the servers.
For example, a domain user or an SSH (Secure Shell) user with sudo permissions
that has access to all servers.
• Open the following firewall ports:
• TCP 443 outbound from source server to CloudEndure console
• TCP 1500 outbound from source server to CloudEndure replication server
in the target Virtual Private Cloud on AWS
• Verify that Windows servers run .NET Framework 3.5 or later
• Verify that Windows servers have at least 3 GB of free space on drive C
• Configure the migration server network settings to connect to AWS and the source
servers
Migration waves
Migration implementation plan
Week 1 Week 2 Week 3 Week 4 Week 5 Week 6
Build Validate
Wave 1
Test Cutover

Build Validate
Wave 2
Test Cutover

Build Validate
Wave 3 Test Cutover

Build Validate
Wave 4
Test Cutover
© 2021 Amazon Web Services, Inc. or its affiliates. All rights reserved. 58

Migration tasks are scheduled in waves. Each wave consists of a group of applications
and servers that have the same cutover date. Waves that contain 25–35 servers are
easier to manage and troubleshoot.

Each wave should be completed in a predefined period. For example, in the three-
week period shown:

• Week 1 is the build stage.

• Week 2 is the validate and boot testing stage.
• Week 3 is the cutover stage.

The waves run in parallel.

Migration implementation
Build Validate Test Cutover
Check prerequisites CloudEndure dry run Test launch App verification
Source Automated CE Automated CE Automated Source Automated

CE agent install Create local admin Instance 2/2 check Cutover launch
Source Automated Source Automated AWS Automated CE Automated

Push post-launch script Monitor replication Terminate test Server shutdown

Source Automated CE Automated AWS Automated Source Automated

CloudEndure Migration Factory (CEMF) - Automation

API-driven pipeline: Frontend UI + backend database

The CEMF implementation phase employs provided scripts that automate the
migration tasks you learned about in previous sections.

All the tasks are shown here. You complete the process outlined for each wave of
servers you migrate.
Migration wave automation
1. Check prerequisites. Corporate AWS Cloud
Build

2. Install CloudEndure agents. data centers

3. Push post-launch scripts. Migration wave 1

4. Monitor data replication.

Validate

5. Create local admin account. CEMF Amazon

application DynamoDB
6. CloudEndure cutover dry run. and APIs
Migration wave 2
7. Test launch.
Migration
Test

8. EC2 instance 2/2 status check. server

9. Shut down test instance.

10. Shut down source machine.

Cutover

11. Cutover launch.

The left side of the diagram shows the activities that must be completed and are
automated. The right side shows a high-level diagram of the Migration Factory
solution, including the waves of servers to migrate.

Migration Factory operates on a wave basis, meaning that the automation scripts
operate on each wave (rather than individual servers). For large-scale migrations, you
must plan the waves to contain servers with similar requirements so that they are
migrated together.

Implementation automation scripts are provided for each step. The scripts save
significant time and effort, reduce complexity, and enable migration data.

The Migration Factory solution automates and orchestrates the process.

Example: Install CloudEndure agents
1. Check prerequisites. Corporate AWS Cloud
Build

2. Install CloudEndure agents. data centers

3. Push post launch scripts. Migration wave 1

4. Monitor data replication.

Validate

5. Create local admin account. CEMF Amazon

application DynamoDB
6. CloudEndure cutover dry run. and APIs
Migration wave 2
7. Test launch.
Migration
Test

8. EC2 instance 2/2 status check. server

9. Shut down test instance.

10. Shut down source machine.

Cutover

11. Cutover launch.

A key component of the solution is Amazon DynamoDB, where migration metadata is

stored. Migration wave plans, source service information, server migration status,
and so forth are kept in DynamoDB.

The CloudEndure Migration Factory (CEMF), a React JavaScript portal, accesses the
DynamoDB data through APIs and connects to a Migration Server, which you build.

In this example, to install the CloudEndure agent, the script initiates a call to the
CEMF application to obtain the data related to the servers in the specified wave
(wave 1 contains 12 servers). With the provided data (such as operating system, fully
qualified domain name, and so on) CEMF connects to the 12 servers and installs the
agent. The migration server updates CEMF with progress status.
Example: Monitor data replication
1. Check prerequisites. Corporate AWS Cloud
Build

2. Install CloudEndure agents. data centers

3. Push post launch scripts. Migration wave 1

4. Monitor data replication.

Validate

5. Create local admin account. CEMF Amazon

application DynamoDB
6. CloudEndure cutover dry run. and APIs
Migration wave 2
7. Test launch.
Migration
Test

8. EC2 instance 2/2 status check. server

9. Shut down test instance.

10. Shut down source machine. Your

Cutover

automation
11. Cutover launch. scripts

In this example, a script automates the data replication monitoring process by calling
an API to the CEMF application, to retrieve data about the migration wave. Then, the
migration server queries CloudEndure Migration service by using APIs to capture the
data replication status for the specified wave.

The fundamental purpose of CEMF is to automate manual tasks to decrease

complexity and increase the velocity of the migration. You should consider
developing additional automation scripts that can help automate other migration
processes that meet specific customer requirements. For example:

• Integrate existing CMDB (or other inventory sources) directly into CEMF so that
data changes in the CMDB are automatically reflected, and CEMF can update the
CMDB when changes are completed in the migration.
• Use CEMF to push software changes to servers to meet premigration
requirements. For example, CEMF requires a specific version of .NET on Windows
source servers. A CEMF automation script could enact the software push, and
persist the .NET version ID inside the CEMF data store.
• Use software such as CyberArk to store and retrieve Active Directory credentials
that are required to connect to source servers. This automates a required manual
task for each wave where it is used.

62
Post-migration activities

Activities depend on specific scenarios

and requirements

Example tasks:
• Update servers in the source configuration
management database (CMDB)
• Decommission source machines
• Optimize Amazon EC2 instance
performance

When the migration activities are complete, post-migration activities can take place.
The specific migration scenarios and customer requirements determine the activities.
Tasks and activities might include the following:

• Update servers in the source configuration management database (CMDB). The

servers are migrated by lift-and-shift, so server names might be preserved, and
source servers are shut down. The CMDB can be updated to reflect the same
server running in the cloud.
• Decommission source machines. When the migration is complete, and testing is
successful, you can start to decommission the source machines.
• Optimize performance for the target Amazon EC2 instances. Start to measure
performance metrics against standard tests, and match the size, type, and
parameters of the EC2 instances where the services run to benefit performance at
the lowest possible cost.
Customers use Migration Factory

Energy • Intended to migrate 1,000 servers in a year, but

they only completed 25 servers. They deployed
company CloudEndure Migration Factory and migrated
1,200 servers in 5 months.

Hospitality • Used CloudEndure Migration Factory to rehost

1,400 servers to AWS. Successfully migrated 626
company servers in a single cutover.

• Migrated 621 servers within 4 months with an

IT company increasing velocity due to the automation: 100
servers in July, 140 servers in August, 160 servers
in September, and 211 servers in October.
© 2021 Amazon Web Services, Inc. or its affiliates. All rights reserved. 64

Enterprises use CEMF to fast track their large-scale rehost migration to AWS. Here are
three key customer stories.

Energy company
An energy company intended to migrate 1,000 servers in a year; however, they only
managed to migrate 25 servers. After working with a Partner, they deployed CEMF,
and then migrated 1,200 servers in 5 months.

Hospitality company
While working with a Partner, a hospitality company used CloudEndure Migration
Factory to rehost (lift and shift) 1,400 servers to AWS. They successfully migrated 626
servers in a single cutover.

IT company
An IT company migrated 621 servers within 4 months, with an increasing velocity due
to the automation. They migrated 100 servers in July, 140 servers in August, 160
servers in September, and 211 servers in October.
Migration Factory solution architecture
Solution deployment

Amazon Elastic Container Service

(front-end code)

Amazon Amazon S3
CloudFront
AWS Lambda Amazon Cognito
Migration (login functions)
server
Amazon DynamoDB
Amazon API Admin functions
Gateway
AWS Managed Services
User functions

Tool functions CloudEndure Migration

The CEMF solution uses AWS Lambda to ingest migration metadata into Amazon
DynamoDB. It provides the standard REST API to the migration user to support
automation using Amazon API Gateway. The CEMF solution uses an Amazon Cognito
user pool for authentication.

The CEMF solution uses React JavaScript for the front-end web console. It uses
Amazon Simple Storage Service (Amazon S3) and Amazon CloudFront to serve front-
end traffic.

The AWS CloudFormation template deploys the AWS resources in the customer’s
AWS account. It uses Amazon Elastic Container Service (Amazon ECS) to build the
front-end code and upload the code to an Amazon S3 bucket as part of the
deployment process.

The customer builds a migration server to connect to the CEMF solution platform
using REST APIs.
Lab architecture
Corporate data center AWS Cloud

Public subnet
VPC
User CloudEndure
CloudEndure
Bastion replication subnet

Private subnet

Private subnet
Application Database
server server
Migrate here

Application Database
server server

In the lab exercise, you will migrate to AWS from a corporate data center, as shown in
the architecture diagram. To save time, you are provided with a Windows migration
server (which is also the bastion host), with PuTTY and Python applications installed.
Lab 2: CloudEndure Migration Factory

In this lab, you will:

1. Connect to the bastion host desktop. 120 minutes

2. Configure CloudEndure.
3. Create a user and log in to the migration factory.
4. Configure a CEMF endpoint. Hands-on lab
5. Configure migration factory.
6. Automate migration tasks.

In this lab, you will:

1. Connect to the bastion host desktop.

2. Configure CloudEndure.
3. Create a user and log in to the migration factory.
4. Configure a CEMF endpoint.
5. Configure migration factory.
6. Automate migration tasks.
Best practices

In this section, you learn about patterns to follow when performing migrations at
scale.
Best practices

Save time and avoid pitfalls

• Plan migration waves

• Develop the end-to-end process
• Minimize unnecessary change
• Automate as much as possible
• Prepare application teams

These are migration best practices you can use for your migrations at scale:

• Plan migration waves in advance. This saves time when configuring the migration
factory and validating the automation steps.
• Develop end-to-end process and automation in the early stage. You can customize
the process and the automation to more precisely match the customer’s
requirements.
• Minimize unnecessary change. This is not a wish list. Rehost the servers while
changing less to reduce troubleshooting.
• Automate migration with CEMF as much as possible. The more you use
automation, the faster the migration.
• Prepare the application teams for migration and document as much as possible.
Review

Question 1 Question 4

Question 2

Question 3 Proceed to Summary

Choose the option that matches the activity you want to perform. The Proceed to
Summary option takes you to the next section of the course.
Question 1

Which application migration strategy is the focus of

CloudEndure Migration Factory?
1 minute

A. Repurchasing
B. Retain
C. Refactoring Type in chat

D. Rehosting

Which application migration strategy is the focus of CloudEndure Migration Factory?

A. Repurchasing

B. Retain

C. Refactoring

D. Rehosting
Question 1 answer

Which application migration strategy is the focus of

CloudEndure Migration Factory?

A. Repurchasing
B. Retain
C. Refactoring
D. Rehosting (correct)

Which application migration strategy is the focus of CloudEndure Migration Factory?

The correct answer is D. Rehosting

Question 2

What are the benefits of CloudEndure Migration

Factory discussed in this module?
1 minute
A. Simplicity, speed, cost reduction
B. Speed, high availability, security
C. Ease of use, speed of implementation Type in chat
D. Support available, cost reduction, security

What are the benefits of CloudEndure Migration Factory discussed in this module?

A. Simplicity, speed, cost reduction

B. Speed, high availability, security
C. Ease of use, speed of implementation
D. Support available, cost reduction, security
Question 2 answer

What are the benefits of CloudEndure Migration

Factory discussed in this module?

A. Simplicity, speed, cost reduction (correct)

B. Speed, high availability, security
C. Ease of use, speed of implementation
D. Support available, cost reduction, security

What are the benefits of CloudEndure Migration Factory discussed in this module?

A. Simplicity, speed, cost reduction

Question 3

Where must customers build the migration server?

(Select TWO.)
1 minute
A. On premises
B. In an AWS account
C. On all admin desktops Type in chat
D. Local networks
E. Virtual private networks

Where must customers build the migration server? (Select TWO.)

A. On premises
B. In an AWS account
C. On all admin desktops
D. Local networks
E. Virtual private networks
Question 3 answer

Where must customers build the migration server?

(Select TWO.)
A. On premises (correct)
B. In an AWS account (correct)
C. On all admin desktops
D. Local networks
E. Virtual private networks

Where must customers build the migration server?

The correct answer is A and B. Customers can build the server near the source or the
target, as long as it can connect to both environments.
Question 4

Which of the following is a build migration

automation step?
1 minute
A. Monitor replication, create local admin, CloudEndure
dry run
B. Check source prerequisites, create local admin,
CloudEndure agent install at source Type in chat

C. Check source prerequisites, CloudEndure agent install

at source, push postlaunch script at source
D. Check source prerequisites, CloudEndure agent install
at source, CloudEndure dry run

Which of the following is a build migration automation step?

A. Monitor replication, create local admin, CloudEndure dry run

B. Check source prerequisites, create local admin, CloudEndure agent install at
source
C. Check source prerequisites, CloudEndure agent install at source, push
postlaunch script at source
D. Check source prerequisites, CloudEndure agent install at source, CloudEndure
dry run
Question 4 answer

Which of the following is a build migration

automation step?
A. Monitor replication, create local admin, CloudEndure
dry run
B. Check source prerequisites, create local admin,
CloudEndure agent install at source
C. Check source prerequisites, CloudEndure agent install
at source, push postlaunch script at source (correct)
D. Check source prerequisites, CloudEndure agent install
at source, CloudEndure dry run

Which of the following is a build migration automation step?

The correct answer is C. Check source prerequisites, CloudEndure agent install at

source, push postlaunch script at source
Summary

In this module, you learned how to:

• Describe the benefits of using automation to perform large-scale migrations

Containerize applications with

AWS App2Container

Welcome to Module 4: Containerize applications with AWS App2Container (A2C).

Objectives

In this module, you will learn how to:

• Describe the benefits of replatforming applications to run in containers

• Identify considerations for migrating applications to containers
• Evaluate containerizing applications based on an application’s requirements
• Identify the tasks to switch to containers
• Describe AWS App2Container and its benefits
• Describe the AWS App2Container workflow
• Identify the steps in the containerization process

In this module, you will learn how to:

• Describe the benefits of replatforming applications to run in containers

On-premises servers Virtual machines (VMs) Containers

Container Container Container

App A App B App C
VM VM VM
App A App B App C Libraries Libs

Applications A, B, C Libs Libs Libs Libraries

Guest Guest Guest
Libraries OS OS OS Containerization platform

Operating system Virtualization platform Operating system

Server hardware Server hardware Server hardware

On-premises servers
Many customers are familiar with on-premises servers. On-premises servers run a
standalone operating system (OS) with one or many applications using libraries, such
as Java. Costs remain constant, whether or not the server is in use. To scale,
customers must buy and configure additional servers.

Virtual machines
Adding a virtualization layer on an on-premises server enables virtual machines
(VMs). The virtualization layer is an abstraction from the underlying host OS and
kernel resources. This layer has more separation. It has higher use of the host central
processing unit (CPU) and random access memory (RAM) since more VMs can be
added to a single physical machine. The virtualization layer, whether software or
hardware, adds performance overhead.

Furthermore, because a VM emulates a physical machine, each VM needs its own full
guest OS, which also adds to overhead. Now, customers must manage and patch as
many operating systems as they have VMs instead of one OS. Additionally, customers
have the start-up cost of a full boot cycle associated with a VM.
Containers

With the container platform, containers can deliver efficiency and performance. The
platform lets containers share a machine’s OS system kernel. It exposes the
underlying OS file system to allow for shared libraries but can permit individual
libraries as necessary.

A platform with a container image lets containers start nearly instantly. The fast spin-
up and spin-down of containers, with the immutable, read-only nature of the
container image, enable quick scaling and high usage of the container host.

82
Containerizing benefits

Agility Portability Operational

efficiency

Containerizing applications provides a few key benefits:

• Agility – Applications are rapidly deployed, patched, and scaled since containers do
not include OS images and require less system resources than traditional
environments.
• Portability – By running applications in containers, you can deploy applications to
multiple operating systems (such as Linux or Windows) and hardware platforms
easily.
• Operational efficiency – Containers reduce IT operational overhead costs and
achieve optimized compute infrastructure. For example, customers can reduce
costs by containerizing instead of a lift-and-shift to a VM. Containers might take up
less space than VMs (container images are typically tens of MBs in size), can
handle more applications, and require fewer VMs and operating systems. This
means customers can fit more applications on each server or cluster.

While these benefits are reasons to containerizing an application, customers face

challenges when working with applications that were built before cloud technology.
Containerizing challenges

Technology Staff Process

The main challenges of containerizing applications are technology, staff, and process
related.

• Technology – When customers containerize applications, they face challenges with

legacy platforms such as earlier versions of operating systems, Java, Component
Object Model (COM), COM+, and .NET. Plus, differentiating operating in containers
versus VMs. With the legacy platforms, customers often must overcome
challenges related to:

• Monolithic on-premises applications built with different underlying

development frameworks and Windows OS versions that are tedious to
refractor and containerize
• Discovery of applications based on legacy architecture, like Windows 2003
or 2008, and migrating to modern, supported operating systems
• Optimum use of Windows licensing, and suggestions during the process
that don’t slow down the migration
• Migration of AIX applications to open systems without affecting
development timelines
Customers must become familiar with operating in containers. For example, if a
customer must apply a patch or a hot fix to an application, they usually log in to the
VM and apply the patch or hot fix to the application directly. In containers, the
customer must terminate the old container, build a new container image, and
relaunch the application from scratch.

• Staff – When customers are containerizing applications, they face challenges with
their staff due to:

• Absence of developer tooling support for cloud migration and container

migration
• Lack of domain knowledge about legacy applications
• Lack of expertise about containers
• Lack of expertise about cloud technologies

• Process – Customers often replatform applications to open systems to reduce

operating expenses. They face challenges with the complications of moving
workloads to different platforms. When moving applications, you must consider
the efforts to deploy and maintain the systems. Even script-based build and deploy
methods can be time consuming if the process requires repeated manual effort.
For example, moving from Windows to Linux would require rewriting and
recompiling the code. However, the same automated deployment (such as Puppet
or Chef) can be retained to maintain most of the process already in place.

85
Application discovery

In this section, you will learn about the discovery process that leads to applying
containerization efforts to applications.
• Software applications that fit
Common design containerized solutions are
patterns designed to be:
• Portable between environments
• Deployed on modern cloud
platforms
• Run in maximum agility
deployments
• Scaled up without significant
changes in architecture

Software applications that fit containerized solutions are designed to be:

• Portable between environments

• Deployed on modern cloud platforms
• Run in maximum agility deployments
• Scaled up without significant changes in architecture
Before you containerize

Dependencies Compactness

Configuration Data storage

Logging External access

Before containerizing applications, a few factors must be considered:

• Dependencies. Before containerizing applications, customers must declare and

isolate dependencies. All dependencies should be declared with no implicit
reliance on system tools or libraries. For example, if a customer has a function that
is used in multiple places of application code, they must package the function into
its own library and include it in the application deployment package.

• Configuration. Before containerizing applications, customers must store

configurations that vary between deployments in the environment. They should
keep configurations as environment variables to avoid losing the configurations.
For instance, if a configuration is embedded with an application in a container, and
the container fails and is deleted, the configuration would be lost with the
application.

• Logging. Before containerizing applications, customers should make sure that the
applications produce logs as event streams, which means that the applications log
to stdout (standard output). This allows an application to be deployed in multiple
orchestration layers, without having to build special logging in each environment.
• Compactness. Compactness refers to the size of the application being
containerized. Instead of containerizing an entire OS, we recommend that
customers containerize applications that are the core components of the OS. For
example, Microsoft upgraded the Windows container to reduce the size of the OS.
The 2016 base .NET container image was 6 GB. For 2019, the size was reduced to
1.5 GB.

• Data storage. Data should be stored and accessed externally. That way, the
databases and shared file systems are not part of the containerized applications.

• External access. To access data externally, customers need information such as a

user name, password, and connection settings. The best practice is to store this
information as environmental variables inside a database table or in an external
encrypted file, rather than as an external file.

For more information about container image sizes, see:

https://devblogs.microsoft.com/dotnet/we-made-windows-server-core-container-
images-40-smaller/ on the .NET blog.

88
Determine containerization complexity

Installation

License

Programming language

more
© 2021 Amazon Web Services, Inc. or its affiliates. All rights reserved. 89

When going through the containerization process, a few main categories dictate the
process’s complexity. These include installation, license, language, application binary,
sessions, user interface, and network.

• Installation. Installation refers to the application installation process on the target

machine. When going forward with installation, consider the following questions:

• What kind of an application installation platform is being used?

• Does a package or source code run and install the application?
• Will an unattended installer be placed in the container?
• Will an interactive installer require the customer to complete multiple
steps to install the application?

The answers to these questions identifies the complexity of containerizing the

application. For example, if the customer is using an interactive installer and
working with 100 containers, they would have to run the interactive installer 100
times or automate the process.

• License. The license refers to the software application license. For licenses,
consider the following questions:

• What kind of license does the application have?

• Does the customer or company own the license?
• Is the license for an open-source application?
• Is the license restricted on number of installations?

The answers to these questions helps identify the complexity of the

containerization. For example, a customer has an application with a license that
allows for only one installation. If the license has been used on the legacy server, it
will be difficult to reinstall the application on another server. In this case,
containerizing would be challenging, because the software license will restrict the
application from being usable.

• Language. Language refers to the programming language used. When considering

the issues regarding programming languages, consider the following questions:

• What kind of language is used for the application? Is it a modern

programming language, such as C#, Java, JavaScript, PHP, or Python? Is it
x86 precompiled binaries?
• Is the customer going to put the application code compiler inside the
container? Will they use a pipeline to compile the application code and put
the binaries file inside the container?

The answers to these questions influences how the customer will deploy the
applications.

A major concern is whether the language is non-x86. In that case, the customer is
working with application code that runs on a platform without an Intel-based
processor. The customer must take additional components into consideration, such as
determining how to deploy the specific non-x86 precompiled binary files. For
example, assume that a customer wants to use an AWS Graviton processor. If the
compiled code is running in C, to run on AWS Graviton, the customer must compile
the code in AWS Graviton. Next, the customer would save the compiled object to
deploy in their container.

89
Containerization complexity factors

Application binary

Sessions

User interface (UI)

Network

• Application binary. Application binary refers to the machine language process that
runs the application. When assessing the application to be containerized,
determine if it’s a single binary, multiple process or a self-modifying code. This will
help the customer decide if containerizing the application makes sense or if the
application should be left in a VM. A single binary application is a good candidate
for containerization because it is more portable and compact.

Example: If the application is a single binary or Java Archive (JAR) file, it can be
containerized. Java applications and JAR files are especially flexible and can be
readily converted. Containerized Java carries the specific JRE environment inside
the container, which allows for more efficient deployment. This also allows many
versions of Java runtimes to be run side by side on the same servers due to the
isolation that the containers provide.

• Sessions. Sessions refers to the way an application runs. The key question for
sessions is if the session is stateless, stateful, or cluster dependent. If the
application is cluster dependent, it will be challenging to containerize, because it is
connected to other applications and depends on another application to run.
• User interface (UI). UI refers to the interface of the application being containerized.
For instance:

• Is it a website, a process running in the background of an application, or

something else?
• Is the interface a service?
• Are there scheduled jobs or agents associated with the interface?
• Is the interface an interface daemon?
• Is the interface a desktop client? (Desktop clients are more complicated as
the container scales up.)

Answering these questions helps customers plan the detailed work and processes
required to containerize. The more time and resources the work and processes
require, the more complex the containerization becomes.

• Network. Network refers to the type of communication protocols the application

uses to communicate with other systems. Key network questions include:

• Does the application need open standard HTTP/HTTPS ports or something

custom?
• Does the application need TCP or UDP ports?
• Is the application highly isolated (that is, does it need an IPsec virtual
tunnel interface setup, which entails the need of certificates)?

90
AWS App2Container (A2C)

When applications to be containerized are portable and ready, AWS App2Container

(A2C) can automate the process.
AWS App2Container
Modernize applications into containers

Create Deploy
Discover Extract and
deployment in the
and analyze containerize
artifacts AWS Cloud

AWS App2Container (A2C) helps customers lift and shift applications that run in an
on-premises data center or on VMs. It enables applications to run in containers that
are managed by Amazon Elastic Container Service (Amazon ECS) or Amazon Elastic
Kubernetes Service (Amazon EKS).

You use AWS App2Container to:

1. Discover and analyze candidate applications

2. Extract and containerize, building an application container
3. Create deployment artifacts that are needed to deploy the containers on Amazon
ECS or Amazon EKS
4. Deploy in the AWS Cloud
A2C benefits

Accelerates
Streamlines Scales and
application
operations secures applications
modernization

A2C provides the following three primary benefits:

• Streamlines operations. A2C allows customers to containerize existing applications.

For monitoring, operations, and software delivery, A2C standardizes on a single set
of tooling. By containerizing applications with A2C, customers can unify
infrastructure and skill sets needed to operate applications. This can save time as
well as infrastructure and training costs.
• Accelerates application modernization. A2C analyzes applications that are
candidates for being containerized. It automatically generates a container image
that is configured with the correct dependencies, network configurations, and
deployment instructions for Amazon ECS or Amazon EKS. This process can help
customers save time as well as avoid manual settings and errors from negligence.
• Scales and secures applications. A2C allows customers to deploy an existing
application on the cloud that is provisioned with the correct networking and
security configurations.
Supported runtimes and middleware

Java ASP.NET
Frameworks Distributions Frameworks and system
requirements
• Tomcat • Ubuntu
• Windows Server Core 2016 or
• Spring Boot • CentOS 2019 (earlier OS do not
• JBoss* • RHEL support containers)
• WebLogic* • IIS 7.5 or later
• Amazon Linux
• WebSphere* • .NET framework version 3.5
later
*In standalone mode

AC2 supports the Java runtimes and middleware (Linux) presented here.

Frameworks
• Tomcat
• Spring Boot
• JBoss (standalone mode)
• Weblogic (standalone mode)
• Websphere (standalone mode)

Distributions
• Ubuntu
• CentOS
• Red Hat Enterprise Linux (RHEL)
• Amazon Linux

NOTE
If the applications are running on Ubuntu 14, Red Hat versions 4-6, or CentOS 5, the
customer might still be able to use App2Container by using a worker machine for
containerization and deployment steps.
Supported ASP.NET applications (Windows)
App2Container can identify and containerize ASP.NET applications deployed on
Internet Information Services (IIS) running on Windows Server 2016 or later. It
supports Windows Server Core as a base image corresponding to the Windows Server
version of an application server or worker node.

Application framework and system requirements:

• Windows Server Core 2016 or 2019 (prior operating systems do not support
containers)
• IIS 7.5 or later
• .NET framework version 3.5 or later

If the applications are running on Windows Server 2008 or 2012 R2, the customer
might be able to use App2Container by setting up a worker machine for
containerization and deployment steps.

Reference
For more information about containerizing applications using A2C, see:
https://docs.aws.amazon.com/app2container/latest/UserGuide/supported-
applications.html.

94
A2C limitations

Java application frameworks ASP.NET

• ASP.NET applications that

Cluster/HA mode depend on Windows
Communication
Foundation
• Non-IIS applications
• Pre-Windows Server Core
2016 applications

A2C doesn’t support Cluster/HA mode for Java application frameworks. Additionally,
unsupported ASP.NET (Windows) applications include:

• ASP.NET applications that depend on the Windows Communication Foundation

(WCF).
• ASP.NET applications that use files and registries outside of IIS web application
directories and depend on other Windows services or processes outside of IIS.
• ASP.NET applications that depend on features of a Windows OS version prior to
Windows Server Core 2016.

Even though these frameworks and applications are unsupported by App2Container,

you can use other tools to containerize them, such as Image2Docker.

Reference
For more information about containerizing applications and App2Container, see:
https://aws.amazon.com/app2container/faqs/.
Containerize existing applications
Deployment source Application server AWS Cloud
(VM or EC2 instance)
Running
application Deployment target
Virtual
machine 4
.NET

On-premises IIS server App2Container Amazon Elastic Amazon Elastic Amazon Elastic
server Container Container Container Registry
1 Service Kubernetes
Amazon EC2
instance Java Lifecycle management
2 3 5
Other cloud Springboot
environments Tomcat Artifacts
Jboss AWS CodePipeline AWS CodeBuild AWS CodeDeploy
WebSphere
WebLogic
© 2021 Amazon Web Services, Inc. or its affiliates. All rights reserved. 96

AWS App2Container (A2C) is a command line tool that helps customers lift and shift
applications that run in an on-premises data center or on VMs. It enables applications
to run in containers that are managed by Amazon Elastic Container Service (Amazon
ECS) or Amazon Elastic Kubernetes Service (Amazon EKS).

The AWS App2Container workflow is:

1. Discover and analyze. The first step identifies and lists candidate applications
(.NET or Java) for the application server to containerize.
2. Extract and containerize. The next step extracts application artifacts for
containerization and generates a Dockerfile. It then initiate builds for the
application container.
3. Create deployment artifacts. Next, AWS artifacts are generated. These are needed
to deploy the containers on either Amazon ECS or Amazon EKS.
4. Deploy in the AWS Cloud. The final step is to deploy the containers in AWS Cloud.
5. (Optional) create a CI/CD pipeline with AWS CodePipeline. This option step is to
automate building and deploying the containers.
Java (Linux) prerequisites

AWS Command Docker engine is One or more Customer has Server has
Line Interface installed Java applications root access GNU Tar
(AWS CLI) is are running installed and
installed 20 GB of free
space

For Java applications, ensure that:

• AWS Command Line Interface (AWS CLI) is installed to configure the AWS profile on
the application server.
• Docker engine is installed on the server where the containerization and
deployment steps will be running. If the customer cannot install Docker in the
same machine or server that is the running the application, the customer must use
a worker machine with Docker and App2Container installed.
• One or more Java applications are running on the application server.
• The customer has root access on the application server (and worker machine, if
applicable).
• The application server (and worker machine, if applicable) has GNU Tar and 20 GB
of free space.
.NET (Windows) prerequisites

AWS Tools for Docker engine is One or more IIS Customer is a Server has
PowerShell are installed application is Windows PowerShell v5.1
installed running administrator or later and
20–30 GB of
free space

For ASP.NET applications, ensure that:

• AWS Tools for Windows PowerShell are installed to configure the AWS profile on
the application server.
• Docker engine is installed on the server where the containerization and
deployment steps will be running. If the customer cannot install Docker in the
same machine or server that is the running the application, the customer must use
a worker machine with Docker and App2Container installed.
• One or more applications are running in IIS on the application server.
• The customer is a Windows administrator on the application server (and worker
machine, if applicable).
• The application server or worker machine has PowerShell version 5.1 or later and
at least 20–30 GB of free space.
Get started with A2C

1. Sign up for AWS 2. Grant 3. Decide where

permissions to containerization
IAM users will run

4. Configure the 5. Install the

AWS profile Docker engine

Here are the setup steps:

1. Once the customer signs up for AWS, they are automatically signed up for all AWS
services.

2. The customer grants permissions for IAM users. To run commands, A2C needs
access to AWS services. Deployment requires elevated AWS Identity and Access
Management (IAM) permission, while general-purpose users and groups can run
all other commands.

3. The customer decides where containerization will run. To use A2C on the
application server, they must install A2C and Docker engine. They can use the
server for containerization or set up a worker machine to perform the task.
Customers might want to use a worker machine if:

• The application server is located in a data center without internet access.

• The application server is running an OS that does not support containers.
• The customer prefers to use a dedicated server for the containerization and
deployment process.
If the customer sets up a worker machine, the machine must run the same OS as
the application server and the OS must support containers.

4. The customer configures the AWS profile. A2C uses the customer’s AWS profile to
configure access to AWS resources. The customer must configure the AWS profile
information. First, they determine if it will use AWS CLI for Java or PowerShell for
Windows on the application server and worker machine (if applicable).

5. The customer installs the Docker engine. A2C uses the Docker engine to create
container images to generate Docker files that run containers on Amazon ECS or
Amazon EKS. The customer must install the Docker engine on the application
server or worker machine that will be used to containerize the application.

Reference
For more information about A2C setup, see:
https://docs.aws.amazon.com/app2container/latest/UserGuide/a2c-setup.html.

99
A2C tools
Application server AWS Cloud
• Command line (VM or EC2 instance)

interface run on an Running application Artifacts

application server
Java .NET
Amazon S3
• End-to-end workflow Docker image
on the application
server Amazon Elastic
Container Registry
• Same commands and App2Container

command options for

Task definition
Windows and Linux Artifacts Container
Amazon Elastic
Container
Service

Application2Container is a command line interface that runs on an application server,

and provides commands that discover, analyze, extract, containerize, and deploy
applications in the AWS Cloud.
The same commands run on Linux and Windows environments to containerize Java or
.NET applications.
App2Container produces artifacts that you can use to create and deploy containers.
The artifacts include:

• Customizable application templates (JSON format)

• Tar archive
• Dockerfile
• Entryfile
• Logfile
Containerization steps

1. Install 2. Initialize 3. Analyze 4. Modify

App2Container App2Container application application

5. Transform 6. Deploy 7. Clean up

application application

To containerize an application, complete the following steps:

1. Install App2Container. Depending on the application type (Java or .NET),

App2Container is packaged in an archive file (tar.gz (Java) or zip (.NET)). The
archive contains scripts for installing App2Container. In an application server
where a worker machine is going to be used, App2Container must be installed on
both.

2. Initialize App2Container. On each server where App2Container is installed, run the

init command.

3. Analyze application. Prepare the application to be containerized on the

application server.

4. Modify applications. After analyzing the application, if it was not built following
best practices, modify the application by making it more container friendly
following the 12-factor methodology. You will learn more about 12-factor
methods in Module 5.
5. Transform application. This step involves containerizing the application before
proceeding to deployment. If the application is going to be containerized on the
application server, run the containerize command for the specific platform (Java
or .NET). The output, a set of deployment files, is stored in the workspace
directory specified in Step 2. Initialize App2Container. If the application is going to
be containerized on a worker machine:

a. Run the extract command on the application server.

b. Manually copy the archive file to the worker machine if there was not
automation set to save files in Amazon S3 in Step 2. Initialize
App2Container.
c. Run the containerize command on the worker machine. The output, a set
of deployment artifacts, will be stored in the workspace directory
specified in Step 2. Initialize App2Container.

6. Deploy application. Review the deployment artifacts generated in the previous

step and modify as needed. Run the generate app-deploy command to
deploy the application on AWS.

7. Clean up. This step is optional. If the App2Container needs to be removed by the
customer from the application server or worker machine, delete the
/usr/local/app2container (for Java application) or
C:\Users\Administrator\app2container (for .NET application) folder
where it is installed.

References
• For more information about detailed steps for Java applications, see:
https://docs.aws.amazon.com/app2container/latest/UserGuide/start-containerize-
java-app.html
• For more information about detailed steps for .NET applications, see:
https://docs.aws.amazon.com/app2container/latest/UserGuide/start-containerize-
dotnet-app.html

101
Customers use App2Container

• A public sector customer with minimal container

Public sector expertise containerized two ASP.NET and deployed
to Amazon Elastic Container Service (Amazon ECS).

Financial • A financial services customer containerized one

services .NET and one Java application and deployed to
Amazon Elastic Kubernetes Service (Amazon EKS).
Manufacturing • Two Fortune 500 customers (in manufacturing and
banking banking sectors) containerized Java applications.

• A European retailer containerized five ASP.NET

Retail applications in a few hours.

Enterprises use App2Container to modernize applications they migrate to AWS. Here

are some key customer stories.

Public sector customer

A public sector customer with minimal container expertise containerized two ASP.NET
and deployed to Amazon Elastic Container Service (Amazon ECS).

Financial services customer

A financial services customer containerized one .NET and one Java application, and
deployed to Amazon Elastic Kubernetes Service (Amazon EKS).

Fortune 500 customers (manufacturing and banking)

Two Fortune 500 customers (in manufacturing and banking sectors) containerized
Java applications.

Retail customer
A European retailer containerized five ASP.NET applications in a few hours.
Lab 3: App2Container

In this lab, you will:

1. Install AWS CLI. 60 minutes

2. Create a Docker base image.
3. Install App2Container.
4. Initialize App2Container. Hands-on lab
5. Analyze your application.
6. Transform your application.
7. Set up deployment artifacts.

In this lab, you will:

1. Install AWS CLI.

2. Create a Docker base image.
3. Install App2Container.
4. Initialize App2Container.
5. Analyze your application.
6. Transform your application.
7. Set up deployment artifacts.
Review

104
Review

Question 1 Question 3

Question 2 Proceed to Summary

Choose the option that matches the activity you want to perform. Choose Proceed to
Summary to continue to the next section of the course.
Question 1

Put the App2Container workflow phases in the

correct order.
1 minute
A. Create deployment artifacts
B. Discover and analyze
C. Deploy in AWS Cloud Type in chat
D. Extract and containerize

Put the App2Container workflow phases in the correct order.

A. Create deployment artifacts

B. Discover and analyze
C. Deploy to AWS Cloud
D. Extract and containerize
Question 1 answer

Put the App2Container workflow phases in the

correct order.

A. Create deployment artifacts – 3

B. Discover and analyze – 1
C. Deploy in AWS Cloud – 4
D. Extract and containerize – 2

The correct answer is B, D, A, C.

The correct order is:

1. Discover and analyze (B)

2. Extract and containerize (D)
3. Create deployment artifacts (A)
4. Deploy in AWS Cloud (C)
Question 2

Which of the following are benefits of containerization?

A. Accuracy, rigidity, portability 1 minute

B. Agility, portability, operational efficiency

C. Stability, scalability, strategic value
D. Accessibility, agility, risk aversion Type in chat

Which of the following are containerization benefits?

1. Accuracy, rigidity, portability

2. Agility, portability, operational efficiency
3. Stability, scalability, strategic value
4. Accessibility, agility, risk aversion
Question 2 answer

Which of the following are benefits of containerization?

A. Accuracy, rigidity, portability

B. Agility, portability, operational efficiency (correct)
C. Stability, scalability, strategic value
D. Accessibility, agility, risk aversion

The correct answer is B. Agility, portability, and operational efficiency are

containerization benefits.
Question 3

What is a benefit of using App2Container?

A. Disrupts operations 1 minute

B. Creates new practices to scale and secure applications

C. Accelerates application modernization
D. Complicates deployments Type in chat

What is a benefit of using App2Container?

1. Disrupt operations
2. Create new practices to scale and secure applications
3. Accelerate application modernization
4. Complicate deployments
Question 3 answer

What is a benefit of using App2Container?

A. Disrupts operations
B. Creates new practices to scale and secure applications
C. Accelerates application modernization (correct)
D. Complicates deployments

The correct answer is C.

Summary

In this module, you learned how to:

• Describe the benefits of replatforming applications to run in containers

In this module, you learned how to:

• Describe the benefits of replatforming applications to run in containers

Course Review and Additional

Resources
Objectives

In this module, you will learn how to:

• Recap migration strategies to rehost enterprise fleets and containerize

applications
• Identify additional AWS Partner programs and resources to assist with large-scale
customer migrations
• Identify next steps to engage in large-scale migrations, and find AWS support
when needed

In this module, you will learn how to:

• Recap migration strategies to rehost enterprise fleets and containerize applications

• Identify additional AWS Partner programs and resources to assist with large-scale
customer migrations
• Identify next steps to engage in large-scale migrations, and find AWS support when
needed
Learner path and accreditation
https://aws.amazon.com/partners/training/path-tech-pro/

AWS STP:
Migrating to AWS
(Technical)

AWS STP:
Containers on AWS
(Technical)

AWS STP:
Advanced Migration
(Technical)

Start by achieving AWS Technical Professional and AWS Cloud Economics

accreditations to confirm you understand Amazon Web Services (AWS) fundamentals.
Then advance to additional training by workload or solution area.

Reference
For more information about the AWS Technical Professional Learning Path, see:
https://aws.amazon.com/partners/training/path-tech-pro/.
Migration and container training

AWS Solutions Training for AWS Solutions Training for

Partners: Migrating to AWS – Partners: Migrating to AWS –
Technical (ILT) Technical (Digital)
https://partnercentral.awspartner. https://partnercentral.awspartner.co
com/LmsSsoRedirect?RelayState= m/LmsSsoRedirect?RelayState=/lea
/learningobject/curriculum?id=49 rningobject/wbc?id=51827
730

AWS Solutions Training for AWS Solutions Training for

Partners: Containers on AWS – Partners: Containers on AWS –
Technical (ILT) Technical (Digital)
https://partnercentral.awspartner. https://partnercentral.awspartner
com/LmsSsoRedirect?RelayState= .com/LmsSsoRedirect?RelayState
/learningobject/curriculum?id=38 =/learningobject/wbc?id=42827
777

Sign in to the AWS Partner Network for migration and container training courses that
you can take digitally or with an instructor.

Migrating to AWS – Technical

These migration courses provide AWS Partner solutions architects with best practices
for applying and implementing migration readiness assessment and planning
activities. The curriculum includes guidelines and best practices for performing
migrations using migration tools and services.

• For more information about instructor-led migration courses, see:

HTTPs://partnercentral.awspartner.com/LmsSsoRedirect?RelayState=/learningobje
ct/curriculum?id=49730.
• For more information about digital migration courses, see:
https://partnercentral.awspartner.com/LmsSsoRedirect?RelayState=/learningobjec
t/wbc?id=51827.

Containers on AWS – Technical

These container courses provide a technical introduction to AWS container solutions.
They include discussions of container platforms, benefits, and use cases.
• For more information about instructor-led AWS container courses,
https://partnercentral.awspartner.com/LmsSsoRedirect?RelayState=/learningobjec
t/curriculum?id=38777.
• For more information about digital AWS container courses, see:
https://partnercentral.awspartner.com/LmsSsoRedirect?RelayState=/learningobjec
t/wbc?id=42827.

116
Documentation

AWS CloudEndure Migration Factory

Solution
• Implementation guide
• Source code
https://docs.aws.amazon.com/solutions/latest/aws-cloudendure-
migration-factory-solution/welcome.html

AWS App2Container (A2C)

• User Guide
• Troubleshooting guide
• Command reference
https://docs.aws.amazon.com/app2container/latest/User
Guide/start-intro.html

For more information about the AWS CloudEndure Migration Factory Solution, see
https://docs.aws.amazon.com/solutions/latest/aws-cloudendure-migration-factory-
solution/welcome.html.

For more information about AWS App2Container (A2C), see:

https://docs.aws.amazon.com/app2container/latest/UserGuide/start-intro.html.
Migration resources

Migrate with AWS

• Migration experience
• Comprehensive and mature migration solutions
• Faster time to business results
https://aws.amazon.com/cloud-migration/

AWS Migration Acceleration Program (MAP)

• Migration methodology
• Support, training, and services
• Migration competency acceleration Partners
https://aws.amazon.com/migration-acceleration-program/

Migrating with AWS solutions addresses people, process, technology, and financial
considerations throughout the migration journey. The solutions help ensure that your
project achieves the desired business outcomes. For more information about
migration, see: https://aws.amazon.com/cloud-migration/.

AWS Migration Acceleration Program (MAP) helps reduce operating costs and
improve agility, global scalability, and resiliency options for IT workloads when
migrating to AWS. For more information about MAP, see:
https://aws.amazon.com/migration-acceleration-program/.
AWS Migration resources

Download this migration

guide to help build your
skills and knowledge
https://d1.awsstatic.com/training-and-certification/ramp-
up_guides/Ramp-Up_Guide_Migration.pdf

Learn how to migrate your on-premises

applications and workloads to the AWS
Cloud
https://www.edx.org/course/migrating-to-the-aws-cloud

Migration Ramp-Up Guide

To build your skills and knowledge about migrating to AWS, you can download the
migration guide from https://d1.awsstatic.com/training-and-certification/ramp-
up_guides/Ramp-Up_Guide_Migration.pdf.

Migrating to the AWS Cloud

This 4-week course focuses on migrating workloads to AWS. We will focus on

analyzing your current environment, planning your migration, and discussing the
actual migration steps.
Tech for Tech for
discovery workload
and mobility
planning Total cost Tech for
Delivery of data
ownership migration
Tech for
Consulting application
profiling

AWS Migration Competency Partners

Helping customers move applications to the AWS Cloud
https://aws.amazon.com/migration/partner-solutions/

• Validated Partners with demonstrated expertise

• APN Consulting Partners offer consulting services for migrations
• APN Technology Partners have deep expertise with migrations to AWS

Learn more about the AWS Migration Competency:

https://aws.amazon.com/migration/partner-solutions/.
AWS App2Container resources

Demonstration of AWS App2Container (A2C) as a

command line tool for modernizing .NET and Java
applications into containerized applications
https://youtu.be/Wodiyv4HBFE

The Twelve-Factor App methodology for building apps

that are portable, scalable, and deployment friendly
https://12factor.net

Resources for AWS App2Container (A2C) include:

• A demonstration of A2C as a command line tool for modernizing .NET and Java
applications into containerized applications, see: https://youtu.be/Wodiyv4HBFE.
• For more information about AWS App2Container, see:
https://amzn.to/38JwmYF.
• The Twelve-Factor App methodology. Developers suggest this methodology for
working smoothly and delivering portable, deployment-friendly, and easily scalable
applications. For more information about the Twelve-Factor App methodology,
see: https://12factor.net.
AWS Partner resources

© 2021 Amazon Web Services, Inc. or its affiliates. All rights reserved. 122
AWS Partner Network
APN Technical Baseline Review (TBR)
• Available to all AWS Partners across all tiers
• Provides one-on-one engagement with AWS Partner solutions architects
• Reviews product offerings and helps Partners optimize and refine processes to
improve quality and deliver successful customer outcomes

APN Navigate
• Provides prescriptive guidance from AWS experts
• Step-by-step instruction to build, market, and sell as an AWS Partner
• Equips Partners with a roadmap, enablement tools, and resources

AWS PartnerCast
Helps Partners:
• Create new client opportunities
• Enhance professional relationships
• Develop their AWS Cloud skills

The AWS Partner Network is a global community that helps transform your business
on AWS. It provides access to business and technical benefits and enablement
content from trusted experts. You can increase visibility with AWS and build
connections with key AWS experts by sharing your organization’s progress. You
develop core go-to-market assets to build your portfolio, highlight your expertise on
AWS, and earn trust with customers.

The Technical Baseline Review (TBR) is available to AWS Consulting and Technology
Partners across all tiers who have a workload running on AWS. The TBR provides one-
on-one engagement with an AWS Partner Solutions Architect (PSA). The PSA reviews
your product offering based on core AWS security, reliability, and operational best
practices. PSAs have years of experience supporting millions of active AWS
customers. They help you optimize and refine processes to improve quality and
deliver successful customer outcomes.

APN Navigate is the AWS Partner Network’s enablement program. The program
provides prescriptive guidance from trusted AWS experts on how to transform your
business on AWS. The step-by-step instruction helps you build, market, and sell as an
AWS Partner. All AWS Partners can participate in the APN Navigate program to
accelerate business growth, regardless of where you are in your Partner journey. APN
Navigate equips Partners with a roadmap, enablement tools, and resources to help
you achieve your business goals.

AWS PartnerCast is a series of free interactive webinars and on-demand training

resources to help APN Partners in business and technical roles. It is designed to help
you create new client opportunities, enhance professional relationships, and develop
your AWS Cloud skills.

123
Review

Combines migration methodology with

1. APN Partner
Partners who achieve migration
Resources competency

Programs to help APN Partners build,

2. AWS Migration market, and sell their AWS based
Competency Partners offerings

3. AWS Migration Validated Partners who help customers

Acceleration Program move to the AWS Cloud

Match each AWS resource on the left with the correct description on the right.
Summary

In this module, you learned how to:

• Recap migration strategies to rehost enterprise fleets and containerize

In this module, you learned how to:

• Recap migration strategies to rehost enterprise fleets and containerize applications

Course review • Identify how re-host and re-platform migration

strategies apply to customer migration use cases
• Describe how to plan and perform large-scale
rehosting migrations
• Identify scenarios for modernizing enterprises
through migrating to reliable, secure, cloud
infrastructures
• Identify scenarios for migrating applications to run
in container environments
• Use CloudEndure Migration Factory (CEMF) to
automate large-scale migrations that involve
rehosting
• Use AWS App2Container (A2C) to migrate
applications to container-based platforms

In this course, you learned how to:

• Identify how re-host and re-platform migration strategies apply to customer

Call to action • Improve your skills with additional

training

• Learn about the available AWS

Partner programs that support you

Call to action:

• Engage with your AWS Partner managers to accelerate your ramp up to AWS
• Improve your skills with additional training
• Learn about the available AWS Partner programs that support you
Take the assessment!
End of course assessment
https://partnercentral.awspartner.com/LmsSsoRedirect?RelayState=%2flearningobject%2fw
bc%3fid%3d61579

Follow this link to the end of course assessment:

https://partnercentral.awspartner.com/LmsSsoRedirect?RelayState=%2flearningobjec
t%2fwbc%3fid%3d61579.
Additional resources

AWS Prescriptive Guidance AWS Migration Competency

Consulting Partner Validation
Checklist
https://aws.amazon.com/prescriptiv
https://apn-
e-guidance/?apg-all-cards.sort-
checklists.s3.amazonaws.com/comp
by=item.additionalFields.sortText&a
etency/migration/consulting/CNIBv
pg-all-cards.sort-order=desc
7Tt8.html

AWS Competency Program AWS Partner Opportunity

Accelerating Funding

https://aws.amazon.com/partners
https://partnercentral.awspartner.co
/competencies/
m/apex/AccelHome

Here are some additional resources:

AWS Prescriptive Guidance provides time-tested strategies, guides, and patterns from
AWS Partners to help accelerate cloud migration, modernization, or optimization
projects. These resources were developed by experts at AWS Professional Services.
They are based on years of experience helping customers realize their business
objectives on AWS.

The AWS Competency Program is designed to identify, validate, and promote AWS
Advanced and Premier Tier Partners with demonstrated AWS technical expertise and
proven customer success. The program helps you market and differentiate your
business to AWS customers by showcasing your skills in specialized areas across
industries, use cases, and workloads.

The AWS Competency Partner Validation Checklist (Checklist) is intended for AWS
Partners who are interested in applying for an AWS Competency. The Checklist
provides the criteria necessary for you to achieve the designation under the AWS
Competency Program.
The Partner Opportunity Acceleration (POA) Funding is designed to accelerate sales
cycles and customer adoption of your solution or products powered by AWS. It helps
you develop wins that can validate and demonstrate your AWS expertise and earn the
trust of your customers.

130
Additional resources

AWS Partner Training and

Certification
AWS Accelerate

https://aws.amazon.com/partners https://accelerate.amazonaws.com/
/training

AWS Managed Services AWS Migration Evaluator

Description (Formerly TSO Logic); Build a
business case for AWS.
https://s3.amazonaws.com/am
s.contract.docs/AWS+Managed https://www.youtube.com/watch
+Services+Service+Description. ?v=xkKMtEwPicg&feature=youtu.
pdf be

AWS Training and Certification enables you to support your customers’ business and
technical needs. We offer both digital and classroom training. You can choose to learn
best practices online at your own pace or from an AWS instructor.

The AWS Managed Services Description is a PDF with descriptions and definitions of
managed services.

AWS Accelerate provides:

• A readiness assessment to evaluate the current state of your customer’s cloud

journey
• Portfolio assessment to automate the process of portfolio analysis
• AWS Prescriptive Guidance (APG) Library resources to help accelerate migration,
modernization, and optimization projects

The AWS Migration Evaluator is a 28-minute video that demonstrates how running a
migration assessment with Migration Evaluator (formerly TSO Logic) can help you
prepare a directional business case.
131
Application containerization
level of complexity
Application component Easy Moderate Difficult
Binary Single process Multiple process Self-modifying
Language Modern programming x86 precompiled binaries None-x86
Configuration In a single file In several files Located everywhere
Data In a single folder In multiple folders and partitions Located everywhere
Access credentials Saved in static files Saved in a file and saved on a Saved as a dynamic
network location certificate
Sessions Stateless Stateful Cluster dependent
User Interface Web, backend Services, background process, Desktop client
processing scheduled jobs, agents, daemons
Network HTTP, HTTPS TCP, UDP IPsec, highly isolated
Installation Packages, source Unattended installer Interactive installer
Licensing In-house, open source Proprietary, no source Restrictive

Before containerizing applications, customers must identify and choose the level of
complexity level for each application component. The discovery process identifies if
containerization is worth the time and cost.

Application components include:

• Binary – Files that run in a server

• Language – Programming or assembly languages
• Configuration – Configuration files that have system information
• Data – Application data
• Access credentials – User names and passwords
• Sessions – These are application connections
• User interface – Websites, desktop application user interface files (e.g., HTML, CSS,
or JavaScript files)
• Network – Network configurations
• Installation – Application installations
• Licensing – Software licenses (for example, a Microsoft license)
Thank you

Allrights
rightsreserved.
reserved.This
Thiswork
workmay
maynot
notbe
bereproduced
reproducedororredistributed,
redistributed,ininwhole
wholeororininpart,
part,without
withoutprior
priorwritten
writtenpermission
permission
from Amazon Web Services,
Services,Inc.
Inc.Commercial
Commercialcopying,
copying,lending,
lending,ororselling
sellingisisprohibited.
prohibited.Corrections,
Corrections,feedback,
feedback,ororother
otherquestions?
questions?Contact
Contactususatat
https://support.aws.amazon.com/#/contacts/aws-training. All Alltrademarks
trademarksare arethe
theproperty
propertyof
oftheir
theirowners.
owners.

Advanced Migrating To AWS - Complete
No ratings yet
Advanced Migrating To AWS - Complete
132 pages
Migrating Your Application - Participant Guide
No ratings yet
Migrating Your Application - Participant Guide
267 pages
Transcript For Introduction To Migration Strategies
No ratings yet
Transcript For Introduction To Migration Strategies
3 pages
AWS Migrations Business 2021
No ratings yet
AWS Migrations Business 2021
130 pages
6Rs of Migration AWS ReInvent
100% (1)
6Rs of Migration AWS ReInvent
38 pages
AWS Cheat Sheet - AWS Migration Strategies - The 6 R's - Tutorials Dojo
No ratings yet
AWS Cheat Sheet - AWS Migration Strategies - The 6 R's - Tutorials Dojo
5 pages
Migration Acceleration Program Intro
No ratings yet
Migration Acceleration Program Intro
11 pages
AWS Innovative Migration
No ratings yet
AWS Innovative Migration
44 pages
AWS Certified Cloud Practitioner Practice Tests
From Everand
AWS Certified Cloud Practitioner Practice Tests
iCertify Training
No ratings yet
Migrating Your Existing Applications To The AWS Cloud
No ratings yet
Migrating Your Existing Applications To The AWS Cloud
23 pages
Cloud Migration
No ratings yet
Cloud Migration
23 pages
Cloud Migration
No ratings yet
Cloud Migration
23 pages
Migration Essentials Student Guide v1
No ratings yet
Migration Essentials Student Guide v1
195 pages
AWS App & Data Migration PDF
No ratings yet
AWS App & Data Migration PDF
64 pages
Module 8 Final
No ratings yet
Module 8 Final
22 pages
AWS Certified Solutions Architect - Associate Exam Prep kit
From Everand
AWS Certified Solutions Architect - Associate Exam Prep kit
SUJAN
No ratings yet
Migrating Microsoft Workloads To Amazon Web Services: Andy Hall Jignesh Suthar June 3, 2020
No ratings yet
Migrating Microsoft Workloads To Amazon Web Services: Andy Hall Jignesh Suthar June 3, 2020
56 pages
Presentation Devops Part
No ratings yet
Presentation Devops Part
6 pages
Buy ebook Migrating to AWS: a Manager's Guide: How to Foster Agility, Reduce Costs, and Bring a Competitive Edge to Your Business 1st Edition Jeff Armstrong cheap price
100% (5)
Buy ebook Migrating to AWS: a Manager's Guide: How to Foster Agility, Reduce Costs, and Bring a Competitive Edge to Your Business 1st Edition Jeff Armstrong cheap price
55 pages
Migrate Away That Technical Debt (Level 200)
No ratings yet
Migrate Away That Technical Debt (Level 200)
47 pages
AWS Migrating - and - Modernizing - Enterprise - Workloads
No ratings yet
AWS Migrating - and - Modernizing - Enterprise - Workloads
44 pages
Migrating to AWS: a Manager's Guide: How to Foster Agility, Reduce Costs, and Bring a Competitive Edge to Your Business 1st Edition Jeff Armstrong - Explore the complete ebook content with the fastest download
100% (1)
Migrating to AWS: a Manager's Guide: How to Foster Agility, Reduce Costs, and Bring a Competitive Edge to Your Business 1st Edition Jeff Armstrong - Explore the complete ebook content with the fastest download
60 pages
AWSPartner MigrationSalesEssentials CourseResources
No ratings yet
AWSPartner MigrationSalesEssentials CourseResources
2 pages
Instant ebooks textbook Migrating to AWS: a Manager's Guide: How to Foster Agility, Reduce Costs, and Bring a Competitive Edge to Your Business 1st Edition Jeff Armstrong download all chapters
No ratings yet
Instant ebooks textbook Migrating to AWS: a Manager's Guide: How to Foster Agility, Reduce Costs, and Bring a Competitive Edge to Your Business 1st Edition Jeff Armstrong download all chapters
65 pages
Handout Accelerate Your On-Premise and VMware Migration Journey With AWS
No ratings yet
Handout Accelerate Your On-Premise and VMware Migration Journey With AWS
43 pages
Learn The Fundamentals of AWS Cloud: Learning Resource Duration Type
No ratings yet
Learn The Fundamentals of AWS Cloud: Learning Resource Duration Type
4 pages
(English) 6 R's - Cloud Migration Strategies - Which One Is Right For You - Tech Primers (DownSub - Com)
No ratings yet
(English) 6 R's - Cloud Migration Strategies - Which One Is Right For You - Tech Primers (DownSub - Com)
19 pages
Community - Understanding The "7 RS" - Cloud Migration Strategies
No ratings yet
Community - Understanding The "7 RS" - Cloud Migration Strategies
12 pages
Datadog_AWSeBook_CloudscaleMonitoring
No ratings yet
Datadog_AWSeBook_CloudscaleMonitoring
88 pages
AWS Certified Solutions Architect Professional Blueprint PDF
No ratings yet
AWS Certified Solutions Architect Professional Blueprint PDF
37 pages
Aws Migration Whitepaper 2018
No ratings yet
Aws Migration Whitepaper 2018
44 pages
Data Migration Report
No ratings yet
Data Migration Report
6 pages
Develop Your Migration Toolkit: Mandus Momberg, Partner Solutions Architect Carmen Puccio, Partner Solutions Architect
No ratings yet
Develop Your Migration Toolkit: Mandus Momberg, Partner Solutions Architect Carmen Puccio, Partner Solutions Architect
28 pages
Migration Strategies
No ratings yet
Migration Strategies
5 pages
AWS Certified Solutions Architect Associate Exam Insights : Q&A with Explanations
From Everand
AWS Certified Solutions Architect Associate Exam Insights : Q&A with Explanations
SUJAN
No ratings yet
AWS Migration
No ratings yet
AWS Migration
14 pages
Questions
No ratings yet
Questions
8 pages
MATI - Migraciones Clase 2 - 2024 2do 50
No ratings yet
MATI - Migraciones Clase 2 - 2024 2do 50
19 pages
9e2610d5-de37-4987-9096-361791946942
No ratings yet
9e2610d5-de37-4987-9096-361791946942
12 pages
Ramp-Up Guide Migration
No ratings yet
Ramp-Up Guide Migration
3 pages
Migrating To Aws Best Practices
No ratings yet
Migrating To Aws Best Practices
20 pages
The 7 Rs of Migration Strategies
No ratings yet
The 7 Rs of Migration Strategies
2 pages
AWS Cloud Adoption Framework (AWS CAF) [Autosaved]
No ratings yet
AWS Cloud Adoption Framework (AWS CAF) [Autosaved]
12 pages
ISV-acce-migration-ps-eBook_final
No ratings yet
ISV-acce-migration-ps-eBook_final
17 pages
PGPCC Aug22 GroupB AMITMOHANSAKLANI CaseAnalysis-1-v1.0
No ratings yet
PGPCC Aug22 GroupB AMITMOHANSAKLANI CaseAnalysis-1-v1.0
5 pages
Expanded_Cloud_Migration_Best_Practices
No ratings yet
Expanded_Cloud_Migration_Best_Practices
5 pages
cloud-to-aws-migration-guide-for-startups
No ratings yet
cloud-to-aws-migration-guide-for-startups
17 pages
(Ebook) Migrating to AWS: a Manager's Guide: How to Foster Agility, Reduce Costs, and Bring a Competitive Edge to Your Business by Jeff Armstrong ISBN 9781492074243, 1492074241 instant download
No ratings yet
(Ebook) Migrating to AWS: a Manager's Guide: How to Foster Agility, Reduce Costs, and Bring a Competitive Edge to Your Business by Jeff Armstrong ISBN 9781492074243, 1492074241 instant download
57 pages
Report Cloud
No ratings yet
Report Cloud
7 pages
Delivery of Cloud infrastructure strategies
No ratings yet
Delivery of Cloud infrastructure strategies
2 pages
N2WS WP Aws Migration PDF
No ratings yet
N2WS WP Aws Migration PDF
18 pages
migrations-business-participants-guide
No ratings yet
migrations-business-participants-guide
140 pages
Cloud Migration Strategy - Best Practices - Whitepaper - v2.0 PDF
100% (1)
Cloud Migration Strategy - Best Practices - Whitepaper - v2.0 PDF
20 pages
Understanding Your Application Readiness When Migrating To AWS
No ratings yet
Understanding Your Application Readiness When Migrating To AWS
27 pages
AWS Migrate Resources To New Region
No ratings yet
AWS Migrate Resources To New Region
23 pages
A Practical Guide To Cloud Migration
100% (1)
A Practical Guide To Cloud Migration
13 pages
Module-8
No ratings yet
Module-8
32 pages
2023 AWS T&C Program Overview
No ratings yet
2023 AWS T&C Program Overview
38 pages
Accelerating+Your+AWS+Journey+ +Migration+&+Modernization+e Book
No ratings yet
Accelerating+Your+AWS+Journey+ +Migration+&+Modernization+e Book
16 pages
ID Partner Migrations Immersion Day - July 2022 v1.2
No ratings yet
ID Partner Migrations Immersion Day - July 2022 v1.2
56 pages
Content Beyond Syllabus
No ratings yet
Content Beyond Syllabus
10 pages
2marks WSN
No ratings yet
2marks WSN
8 pages
Gs Series
No ratings yet
Gs Series
20 pages
Quick Setup Guide: WL-5460AP v2
No ratings yet
Quick Setup Guide: WL-5460AP v2
74 pages
software-architecture-for-developers
No ratings yet
software-architecture-for-developers
376 pages
Practice 18 - Handling Enqueue Waits
No ratings yet
Practice 18 - Handling Enqueue Waits
7 pages
Amarisoft Software Install Guide
No ratings yet
Amarisoft Software Install Guide
21 pages
Quantum CPU Operating System: Upgrade and Update Procedure
No ratings yet
Quantum CPU Operating System: Upgrade and Update Procedure
52 pages
Result of III B.Tech. I Semester (R18) Regular, March 2021 Exams
No ratings yet
Result of III B.Tech. I Semester (R18) Regular, March 2021 Exams
2 pages
Interview For Qualcomm
50% (2)
Interview For Qualcomm
3 pages
SAP S4 Finance Configuration Module
No ratings yet
SAP S4 Finance Configuration Module
85 pages
Discuss Everything About Dragon Sky Wiki - Fandom
No ratings yet
Discuss Everything About Dragon Sky Wiki - Fandom
12 pages
J1939 Introduction
0% (1)
J1939 Introduction
2 pages
EDI Implementation Guidelines Delins Od3 Page 1 of 31
No ratings yet
EDI Implementation Guidelines Delins Od3 Page 1 of 31
31 pages
Digital Assistants
No ratings yet
Digital Assistants
3 pages
Sannidhi Internship
No ratings yet
Sannidhi Internship
18 pages
2024_6COSC020W_CW(1)
No ratings yet
2024_6COSC020W_CW(1)
7 pages
AMP For Endpoints User Guide
No ratings yet
AMP For Endpoints User Guide
225 pages
Enodeb Wraparound Testing
No ratings yet
Enodeb Wraparound Testing
22 pages
Avoid Costly Measures: Remote Thickness Tracking
No ratings yet
Avoid Costly Measures: Remote Thickness Tracking
8 pages
CDA300 Programming Manual
No ratings yet
CDA300 Programming Manual
76 pages
Hacking Https
No ratings yet
Hacking Https
1 page
Fuzzing and Finding Vulnerabilities With Winafl/Afl
No ratings yet
Fuzzing and Finding Vulnerabilities With Winafl/Afl
4 pages
Use Case Question
No ratings yet
Use Case Question
7 pages
Music Rhythm LED Flashlight Circuit - Electronics Projects 2024
No ratings yet
Music Rhythm LED Flashlight Circuit - Electronics Projects 2024
9 pages
1 Lec
No ratings yet
1 Lec
11 pages
Vortex: Quickstart Guide
No ratings yet
Vortex: Quickstart Guide
40 pages
CH 02
No ratings yet
CH 02
8 pages
Adaptation of The Okumura-Hata Model To The Environment of Accra
No ratings yet
Adaptation of The Okumura-Hata Model To The Environment of Accra
6 pages
AI25 EthernetIP Manual
No ratings yet
AI25 EthernetIP Manual
52 pages