AWS m2 documentation change
Summary
Updated product name from 'AWS Blu Age Runtime' to 'AWS Transform for mainframe Runtime' throughout the documentation.
Security assessment
The changes are purely a product rebranding/renaming exercise. There are no modifications to security configurations, procedures, or warnings. The content related to IAM roles, VPCs, subnets, and security groups remains unchanged in its security context.
Diff
diff --git a/m2/latest/userguide/ba-runtime-deploy-container.md b/m2/latest/userguide/ba-runtime-deploy-container.md index 82f0f8908..224eebe8a 100644 --- a//m2/latest/userguide/ba-runtime-deploy-container.md +++ b//m2/latest/userguide/ba-runtime-deploy-container.md @@ -9 +9 @@ AWS Mainframe Modernization Service (Managed Runtime Environment experience) is -# Set up AWS Blu Age Runtime on container +# Set up AWS Transform for mainframe Runtime on container @@ -11 +11 @@ AWS Mainframe Modernization Service (Managed Runtime Environment experience) is -This topic explains how to set up and deploy the PlanetsDemo sample application using AWS Blu Age Runtime on a docker container. +This topic explains how to set up and deploy the PlanetsDemo sample application using AWS Transform for mainframe Runtime on a docker container. @@ -13 +13 @@ This topic explains how to set up and deploy the PlanetsDemo sample application -AWS Blu Age Runtime on container is available for Amazon ECS managed by Amazon EC2, Amazon ECS managed by AWS Fargate, and Amazon EKS managed by Amazon EC2. It isn't compatible with Amazon EKS managed by AWS Fargate. +AWS Transform for mainframe Runtime on container is available for Amazon ECS managed by Amazon EC2, Amazon ECS managed by AWS Fargate, and Amazon EKS managed by Amazon EC2. It isn't compatible with Amazon EKS managed by AWS Fargate. @@ -32 +32 @@ Before you begin, make sure you complete the following prerequisites. - * Complete [AWS Blu Age Runtime prerequisites](./ba-runtime-setup-prereq.html) and [Onboarding AWS Blu Age Runtime](./ba-runtime-setup-onboard.html). + * Complete [AWS Transform for mainframe Runtime prerequisites](./ba-runtime-setup-prereq.html) and [Onboarding AWS Transform for mainframe Runtime](./ba-runtime-setup-onboard.html). @@ -34 +34 @@ Before you begin, make sure you complete the following prerequisites. - * Download the AWS Blu Age Runtime binaries. For instructions, see [Onboarding AWS Blu Age Runtime](./ba-runtime-setup-onboard.html). + * Download the AWS Transform for mainframe Runtime binaries. For instructions, see [Onboarding AWS Transform for mainframe Runtime](./ba-runtime-setup-onboard.html). @@ -55 +55 @@ To set up the PlanetsDemo sample application, complete the following steps. - 3. Prepare a [Dockerfile](https://docs.docker.com/engine/reference/builder/) to build your custom image based on the provided runtime binaries and Apache Tomcat server binaries. See the following example Dockerfile. The goal is to install Apache Tomcat, followed by AWS Blu Age Runtime (for Amazon ECS managed by AWS Fargate) extracted at the root of Apache Tomcat installation directory, and then to install the sample modernized application named PlanetsDemo. + 3. Prepare a [Dockerfile](https://docs.docker.com/engine/reference/builder/) to build your custom image based on the provided runtime binaries and Apache Tomcat server binaries. See the following example Dockerfile. The goal is to install Apache Tomcat, followed by AWS Transform for mainframe Runtime (for Amazon ECS managed by AWS Fargate) extracted at the root of Apache Tomcat installation directory, and then to install the sample modernized application named PlanetsDemo. @@ -107 +107 @@ The following are the contents of `install-gapwalk.sh.` - # Copy Blu Age runtime and tomcat archives to temporary extraction dir + # Copy AWS Transform for mainframe runtime and tomcat archives to temporary extraction dir @@ -118 +118 @@ The following are the contents of `install-gapwalk.sh.` - # Extract Blu Age runtime at velocity dir + # Extract AWS Transform for mainframe runtime at velocity dir @@ -146 +146 @@ The following are the contents of `install-app.sh`. - 6. Specifically, for **Amazon ECS managed by AWS Fargate** case, when creating the Task definition, use the IAM role you created as part of the initial Infrastructure setup. Then, while creating the service, expand the **Networking** section, and configure the VPC, subnets, and security group that you created as part of the initial Infrastructure setup. See, [Infrastructure setup requirements for AWS Blu Age Runtime ](https://docs.aws.amazon.com/m2/latest/userguide/ba-infrastructure-setup.html). + 6. Specifically, for **Amazon ECS managed by AWS Fargate** case, when creating the Task definition, use the IAM role you created as part of the initial Infrastructure setup. Then, while creating the service, expand the **Networking** section, and configure the VPC, subnets, and security group that you created as part of the initial Infrastructure setup. See, [Infrastructure setup requirements for AWS Transform for mainframe Runtime ](https://docs.aws.amazon.com/m2/latest/userguide/ba-infrastructure-setup.html). @@ -161 +161 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Deploy AWS Blu Age Runtime on Amazon ECS and Amazon EKS +Deploy AWS Transform for mainframe Runtime on Amazon ECS and Amazon EKS @@ -163 +163 @@ Deploy AWS Blu Age Runtime on Amazon ECS and Amazon EKS -Upgrade the AWS Blu Age Runtime on container +Upgrade the AWS Transform for mainframe Runtime on container