AWS m2 documentation change
Summary
Updated product name references from 'AWS Blu Age' to 'AWS Transform for mainframe' throughout documentation
Security assessment
Changes are purely branding/product name updates without modifying technical functionality, security configurations, or addressing vulnerabilities. All security-related aspects (secrets managers, Redis cache configuration) remain referenced but unchanged.
Diff
diff --git a/m2/latest/userguide/ba-shared-blusam.md b/m2/latest/userguide/ba-shared-blusam.md index 410f90168..12a19c491 100644 --- a//m2/latest/userguide/ba-shared-blusam.md +++ b//m2/latest/userguide/ba-shared-blusam.md @@ -9 +9 @@ AWS Mainframe Modernization Service (Managed Runtime Environment experience) is -# AWS Blu Age Blusam +# AWS Transform for mainframe Blusam @@ -32 +32 @@ There are four data set organizations: -When modernizing legacy applications, using AWS Blu Age refactoring approach, modernized applications are no longer intended to access VSAM stored data, while preserving the data access logic. The Blusam component is the answer: it allows importing data from legacy VSAM data sets exports, provides an API for the modernized application to manipulate them along with a dedicated administration web application. See [AWS Blu Age Blusam Administration Console](./ba-shared-bac-userguide.html). +When modernizing legacy applications, using AWS Transform for mainframe refactoring approach, modernized applications are no longer intended to access VSAM stored data, while preserving the data access logic. The Blusam component is the answer: it allows importing data from legacy VSAM data sets exports, provides an API for the modernized application to manipulate them along with a dedicated administration web application. See [AWS Transform for mainframe Blusam Administration Console](./ba-shared-bac-userguide.html). @@ -243 +243 @@ Importing LargeKSDS and LargeESDS on Mainframe Modernization managed environment -On AWS Blu Age Runtime on Amazon EC2: +On AWS Transform for mainframe Runtime on Amazon EC2: @@ -245 +245 @@ On AWS Blu Age Runtime on Amazon EC2: - * Import data set by using the [AWS Blu Age Blusam Administration Console](./ba-shared-bac-userguide.html). + * Import data set by using the [AWS Transform for mainframe Blusam Administration Console](./ba-shared-bac-userguide.html). @@ -495 +495 @@ Blusam has to be configured on two aspects: -For information about how to configure access to Blusam storage and caches using either secrets managers or datasources, see [Set up configuration for AWS Blu Age Runtime](./ba-runtime-config.html). +For information about how to configure access to Blusam storage and caches using either secrets managers or datasources, see [Set up configuration for AWS Transform for mainframe Runtime](./ba-runtime-config.html). @@ -546 +546 @@ The Blusam engine configuration properties are regrouped under the bluesam key p -Whenever Redis is used as cache mechanism, either for data or locks (see below), access to the Redis instances is to be configured. For details, see [Available Redis cache properties in AWS Blu Age Runtime](./ba-runtime-redis-configuration.html). +Whenever Redis is used as cache mechanism, either for data or locks (see below), access to the Redis instances is to be configured. For details, see [Available Redis cache properties in AWS Transform for mainframe Runtime](./ba-runtime-redis-configuration.html). @@ -718 +718 @@ You can set default file configurations in the `ds-config.yml` file, located at -The Blusam Administration Console (BAC) is a web-application, used to administrate the Blusam storage. For information about the BAC, see [AWS Blu Age Blusam Administration Console](./ba-shared-bac-userguide.html). +The Blusam Administration Console (BAC) is a web-application, used to administrate the Blusam storage. For information about the BAC, see [AWS Transform for mainframe Blusam Administration Console](./ba-shared-bac-userguide.html).