AWS Mainframe Modernization LAB

1. Assess Your Mainframe Applications

• Identify applications: Identify the mainframe applications you want to migrate.
• Assess compatibility: Assess the compatibility of your applications with cloud environments.
• Analyze dependencies:
  Identify dependencies between applications and data.

assessing mainframe applications for migration

2. Choose a Migration Strategy

• Select a strategy: Choose a migration strategy based on your application's characteristics and business objectives. Options include rehosting, refactoring, or rebuilding.

selecting a migration strategy for mainframe applications

3. Replicate Data

• Replicate data: Use AWS Database Migration Service (DMS) to replicate your mainframe data to AWS.

replicating mainframe data using AWS DMS

4. Migrate Applications

• Migrate applications: Use AWS Application Migration Service (AMS) to migrate your applications to AWS.

migrating mainframe applications using AWS AMS

5. Refactor Applications (if necessary)

• Refactor: If your applications require refactoring, use AWS tools and services to modernize the code and architecture.

refactoring mainframe applications

6. Test and Validate

• Test applications: Thoroughly test your migrated applications in the AWS environment to ensure they function correctly.
• Validate performance: Validate the performance of your migrated applications to ensure they meet your requirements.

testing and validating migrated mainframe applications

7. Optimize and Monitor

• Optimize: Optimize your migrated applications for performance and cost efficiency.
• Monitor: Continuously monitor the performance and health of your migrated applications.

AWS Application Migration Service LAB

 

AWS Application Migration Service 

AWS Application Migration Service (AMS) is a managed service that helps you migrate your on-premises applications to AWS. It provides tools and automation to simplify the migration process.

1. Launch an Agent

• Launch an agent: Download the AMS agent and install it on your on-premises servers.

downloading the AWS AMS agent

2. Configure the Agent

• Configure the agent: Configure the agent to connect to your AWS account and report application data.

configuring the AWS AMS agent

3. Start the Agent

• Start the agent: Start the AMS agent to begin collecting data.

4. Create a Migration Task

• Create a migration task: Use the AWS Management Console to create a migration task.

creating a migration task in the AWS Application Migration Service console

5. Configure the Migration Task

• Configure settings: Configure the migration task settings, such as the source and target environments.

configuring a migration task in the AWS Application Migration Service console

6. Assess Applications

• Assess applications: AMS will automatically assess your applications for migration suitability.

assessing applications in the AWS Application Migration Service console

7. Create Migration Strategies

• Create strategies: Create migration strategies for each application, specifying the migration approach (e.g., rehost, refactor).

creating migration strategies in the AWS Application Migration Service console

8. Migrate Applications

• Migrate applications: Use AMS to migrate your applications to AWS based on the defined strategies.

migrating applications in the AWS Application Migration Service console

9. Validate Migration

• Validate migration: Validate the migrated applications to ensure they are functioning correctly in the AWS environment.

Application Discovery Service LAB

 

1. Launch an Agent

• Launch an agent: Download the ADS agent and install it on your on-premises servers.

downloading the AWS ADS agent

2. Configure the Agent

• Configure the agent: Configure the agent to connect to your AWS account and report application data.

configuring the AWS ADS agent

3. Start the Agent

• Start the agent: Start the ADS agent to begin collecting data.

4. View Discovered Applications

• View applications: Use the AWS Management Console to view the applications discovered by ADS.

 AWS Application Discovery Service console

5. Analyze Application Data

• Analyze data: Use the ADS console to analyze application data, including dependencies, usage patterns, and performance metrics.

analyzing application data in the AWS Application Discovery Service console

6. Create Application Groups

• Create groups: Group related applications together for easier management.

 creating application groups in the AWS Application Discovery Service console

7. Export Data

• Export data: Export application data to CSV or JSON format for further analysis.

Direct Connect LAB

 

. Create a Direct Connect Connection

• Navigate to the Direct Connect console: In the AWS Management Console, search for "Direct Connect" and select the Direct Connect service.
• Create a connection: Click on "Create connection".
• Choose a location: Select the AWS Direct Connect location closest to your on-premises data center.
• Configure connection settings: Specify the desired connection settings, such as the location, bandwidth, and connection type.
• Create the connection: Click on "Create connection".

creating a Direct Connect connection in the AWS Management Console

2. Establish Physical Connectivity

• Establish physical connectivity: Work with your network service provider (NSP) to establish a physical connection between your on-premises data center and the AWS Direct Connect location.

establishing physical connectivity for a Direct Connect connection

3. Create a Virtual Interface

• Create a virtual interface: In the Direct Connect console, click on the connection you created.
• Create a virtual interface: Click on "Create virtual interface".
• Configure virtual interface settings: Specify the desired virtual interface settings, such as the VLAN ID and Amazon side address prefix.
• Create the virtual interface: Click on "Create virtual interface".

creating a virtual interface in the AWS Direct Connect console

4. Configure Your On-Premises Routers

• Configure routers: Configure your on-premises routers to route traffic to the Direct Connect connection.

5. Test Connectivity

• Test connectivity: Test the connection between your on-premises data center and AWS using ping or traceroute.

CloudFront LAB

 

1. Create a Distribution

• Navigate to the CloudFront console: In the AWS Management Console, search for "CloudFront" and select the CloudFront service.
• Create a distribution: Click on "Create distribution".
• Choose a distribution type: Select the desired distribution type (e.g., web, download).
• Configure distribution settings: Specify the desired distribution settings, such as the origin domain name, default cache behavior, and viewer protocol policy.
• Create the distribution: Click on "Create distribution".

creating a CloudFront distribution

2. Configure the Origin

• Configure the origin: Specify the origin domain name where your content is stored (e.g., S3 bucket, EC2 instance).

configuring the origin in a CloudFront distribution

3. Configure Cache Behavior

• Configure cache behavior: Specify the cache behavior for different types of content (e.g., HTML, images, videos).

configuring cache behavior in a CloudFront distribution

4. Deploy the Distribution

• Deploy the distribution: CloudFront will automatically deploy your distribution to its global network of data centers.

5. Access Content

• Access content: Use the CloudFront domain name to access your content. CloudFront will automatically route requests to the nearest data center, improving performance and reducing latency.

accessing content through a CloudFront distribution

6. Monitor and Manage Your Distribution

• Monitor performance: Use CloudFront metrics to monitor the performance of your distribution.
• Manage cache behavior: Modify cache behavior settings as needed.
• Invalidate cache: Invalidate cached content when it's updated.

AWS Cloud Map LAB

 

1. Create a Service

• Navigate to the Cloud Map console: In the AWS Management Console, search for "Cloud Map" and select the Cloud Map service.
• Create a service: Click on "Create service".
• Name your service: Give your service a unique name.
• Choose a service type: Select the desired service type (e.g., HTTP, HTTPS, DNS).
• Create the service:
  Click on "Create service".

creating a service in the AWS Cloud Map console

2. Register Instances

• Register instances: Use the AWS CLI, AWS SDKs, or the Cloud Map console to register instances with your service.

registering instances with a Cloud Map service

3. Discover Instances

• Discover instances: Use the DNS name provided by Cloud Map to discover instances of your service.

discovering instances using Cloud Map

4. Configure DNS Records

• Configure DNS records: If you're using a custom DNS provider, you may need to configure DNS records to route traffic to your Cloud Map service.

Amazon Application Recovery Controller LAB

 

1. Create a Recovery Plan

• Navigate to the Application Recovery Controller console: In the AWS Management Console, search for "Application Recovery Controller" and select the Application Recovery Controller service.
• Create a recovery plan:
  Click on "Create recovery plan".
• Name your recovery plan: Give your recovery plan a unique name.
• Choose a recovery strategy: Select the desired recovery strategy (e.g., failover, failback).
• Create the recovery plan: Click on "Create recovery plan".

creating a recovery plan in the AWS Application Recovery Controller console

2. Add Resources to the Recovery Plan

• Add resources: Click on the recovery plan you created.
• Add resources: Click on "Add resources".
• Choose resources: Select the AWS resources you want to include in the recovery plan (e.g., EC2 instances, databases).

adding resources to a recovery plan in the AWS Application Recovery Controller console

3. Define Recovery Steps

• Define recovery steps: For each resource, define the recovery steps that need to be executed in case of a disaster.

defining recovery steps in the AWS Application Recovery Controller console

4. Test the Recovery Plan

• Test the recovery plan: Use the Application Recovery Controller console to test your recovery plan. This will simulate a disaster and execute the defined recovery steps.

testing a recovery plan in the AWS Application Recovery Controller console

5. Monitor Recovery Status

• Monitor recovery status: Monitor the status of the recovery test and identify any issues.

monitoring recovery status in the AWS Application Recovery Controller console

6. Refine the Recovery Plan

• Refine the recovery plan: Based on the test results, refine your recovery plan to address any identified issues.