AWS SchemaConversionTool documentation change
Summary
Updated section titles, CLI references, and documentation links. Improved consistency in source database terminology.
Security assessment
Modifications are editorial improvements and link corrections. No security advisories or security feature additions detected.
Diff
diff --git a/SchemaConversionTool/latest/userguide/CHAP_Source.Oozie.md b/SchemaConversionTool/latest/userguide/CHAP_Source.Oozie.md index f481fc5c0..2bda18b26 100644 --- a/SchemaConversionTool/latest/userguide/CHAP_Source.Oozie.md +++ b/SchemaConversionTool/latest/userguide/CHAP_Source.Oozie.md @@ -7 +7 @@ PrerequisitesConnecting to Apache Oozie as a sourcePermissions for AWS LambdaCon -# Connecting to Apache Oozie workflows with the AWS Schema Conversion Tool +# Using Apache Oozie as a source for AWS SCT @@ -9 +9 @@ PrerequisitesConnecting to Apache Oozie as a sourcePermissions for AWS LambdaCon -You can use the AWS SCT command line interface (CLI) to convert Apache Oozie workflows to AWS Step Functions. After you migrate your Apache Hadoop workloads to Amazon EMR, you can use a native service in the AWS Cloud to orchestrate your jobs. For more information, see [Connecting to Apache Hadoop](./CHAP_Source.Hadoop.html). +You can use the AWS SCT command line interface (CLI) to convert Apache Oozie workflows to AWS Step Functions. After you migrate your Apache Hadoop workloads to Amazon EMR, you can use a native service in the AWS Cloud to orchestrate your jobs. For more information, see [Using Apache Hadoop as a source](./CHAP_Source.Hadoop.html). @@ -13 +13 @@ AWS SCT converts your Oozie workflows to AWS Step Functions and uses AWS Lambda -To convert Apache Oozie workflows, make sure that you use AWS SCT version 1.0.671 or higher. Also, familiarize yourself with the command line interface of AWS SCT. For more information, see [CLI Reference for AWS Schema Conversion Tool](./CHAP_Reference.html). +To convert Apache Oozie workflows, make sure that you use AWS SCT version 1.0.671 or higher. Also, familiarize yourself with the command line interface of AWS SCT. For more information, see [AWS SCT CLI Reference](./CHAP_Reference.html). @@ -25 +25 @@ The following prerequisites are required to connect to Apache Oozie with the AWS - * Store your AWS credentials and the information about your Amazon S3 bucket in the AWS service profile in the global application settings. Then, AWS SCT uses this AWS service profile to work with your AWS resources. For more information, see [Managing Profiles in the AWS Schema Conversion Tool](./CHAP_UserInterface.Profiles.html). + * Store your AWS credentials and the information about your Amazon S3 bucket in the AWS service profile in the global application settings. Then, AWS SCT uses this AWS service profile to work with your AWS resources. For more information, see [Storing AWS service profiles in AWS SCT](./CHAP_UserInterface.html#CHAP_UserInterface.Profiles). @@ -208 +208 @@ The following code example connects to the `AWS_STEP_FUNCTIONS` target object us - 4. Save your CLI script. Next, add mapping rules and migration commands. For more information, see [Converting Oozie workflows;](./big-data-oozie.html). + 4. Save your CLI script. Next, add mapping rules and migration commands. For more information, see [Converting Apache Oozie to AWS Step Functions](./big-data-oozie.html). @@ -219 +219 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Connecting to Apache Hadoop +Using Apache Hadoop as a source @@ -221 +221 @@ Connecting to Apache Hadoop -Connecting to Azure SQL +Using Azure SQL Database as a source