AWS SchemaConversionTool documentation change
Summary
Updated documentation titles, link references, and terminology related to Hadoop migration processes. Changed section references and updated conversion examples (e.g., Oozie to Step Functions).
Security assessment
Changes appear to be documentation improvements for clarity and accuracy without any security-related content or vulnerability mentions. Updates focus on branding, link structure, and migration target examples.
Diff
diff --git a/SchemaConversionTool/latest/userguide/big-data-hadoop.md b/SchemaConversionTool/latest/userguide/big-data-hadoop.md index 17a79320a..0f35e2a90 100644 --- a/SchemaConversionTool/latest/userguide/big-data-hadoop.md +++ b/SchemaConversionTool/latest/userguide/big-data-hadoop.md @@ -7 +7 @@ OverviewStep 1: Connect to your Hadoop clustersStep 2: Set up the mapping rulesS -# Migrating Hadoop workloads to Amazon EMR with AWS Schema Conversion Tool +# Migrating Apache Hadoop to Amazon EMR with the AWS Schema Conversion Tool @@ -9 +9 @@ OverviewStep 1: Connect to your Hadoop clustersStep 2: Set up the mapping rulesS -To migrate Apache Hadoop clusters, make sure that you use AWS SCT version 1.0.670 or higher. Also, familiarize yourself with the command line interface (CLI) of AWS SCT. For more information, see [CLI Reference for AWS Schema Conversion Tool](./CHAP_Reference.html). +To migrate Apache Hadoop clusters, make sure that you use AWS SCT version 1.0.670 or higher. Also, familiarize yourself with the command line interface (CLI) of AWS SCT. For more information, see [AWS SCT CLI Reference](./CHAP_Reference.html). @@ -69 +69 @@ In this step, you use the following AWS SCT CLI commands. -For examples of using these AWS SCT CLI commands, see [Connecting to Apache Hadoop](./CHAP_Source.Hadoop.html). +For examples of using these AWS SCT CLI commands, see [Using Apache Hadoop as a source](./CHAP_Source.Hadoop.html). @@ -75 +75 @@ When you run the command that connects to a source or target cluster, AWS SCT tr -After you connect to your source and target clusters, set up the mapping rules. A mapping rule defines the migration target for a source cluster. Make sure that you set up mapping rules for all source clusters that you added in your AWS SCT project. For more information about mapping rules, see [Mapping data types in the AWS Schema Conversion Tool](./CHAP_Mapping.html). +After you connect to your source and target clusters, set up the mapping rules. A mapping rule defines the migration target for a source cluster. Make sure that you set up mapping rules for all source clusters that you added in your AWS SCT project. For more information about mapping rules, see [Creating mapping rules in AWS SCT](./CHAP_Mapping.html). @@ -121 +121 @@ For more information about the `AddServerMapping` and `DeleteServerMapping` comm -Before you start the migration, we recommend to create an assessment report. This report summarizes all of the migration tasks and details the action items that will emerge during the migration. To make sure that your migration doesn't fail, view this report and address the action items before the migration. For more information, see [Assessment report](./CHAP_AssessmentReport.html). +Before you start the migration, we recommend to create an assessment report. This report summarizes all of the migration tasks and details the action items that will emerge during the migration. To make sure that your migration doesn't fail, view this report and address the action items before the migration. For more information, see [Migration assessment reports](./CHAP_AssessmentReport.html). @@ -275 +275 @@ The following code example connects to the target Amazon EMR cluster. -In the preceding example, replace `hadoop_address` with the IP address of your Hadoop cluster. If needed, configure the value of the port variable. Next, replace `hadoop_user` and `hadoop_password` with the name of your Hadoop user and the password for this user. For `path\name`, enter the name and path to the PEM file for your source Hadoop cluster. For more information about adding your source and target clusters, see [Connecting to Apache Hadoop databases with the AWS Schema Conversion Tool](./CHAP_Source.Hadoop.html). +In the preceding example, replace `hadoop_address` with the IP address of your Hadoop cluster. If needed, configure the value of the port variable. Next, replace `hadoop_user` and `hadoop_password` with the name of your Hadoop user and the password for this user. For `path\name`, enter the name and path to the PEM file for your source Hadoop cluster. For more information about adding your source and target clusters, see [Using Apache Hadoop as a source for AWS SCT](./CHAP_Source.Hadoop.html). @@ -287 +287 @@ Migrating big data frameworks -Converting Oozie workflows; +Converting Apache Oozie to AWS Step Functions