AWS SchemaConversionTool documentation change
Summary
Updated documentation links, section headers, and terminology related to AWS SCT extension packs. Changed references from 'Managing Profiles' to 'Storing AWS service profiles', updated installation guide reference to include verification steps, and clarified conversion target for data warehouse schemas.
Security assessment
Changes primarily involve documentation restructuring and clarification of existing processes. While credential management and installation verification are security-adjacent topics, there is no evidence of addressing specific vulnerabilities or introducing new security features. The updates appear to be organizational improvements rather than security-focused modifications.
Diff
diff --git a/SchemaConversionTool/latest/userguide/CHAP_ExtensionPack.md b/SchemaConversionTool/latest/userguide/CHAP_ExtensionPack.md index d26d8bcba..10b1fef32 100644 --- a/SchemaConversionTool/latest/userguide/CHAP_ExtensionPack.md +++ b/SchemaConversionTool/latest/userguide/CHAP_ExtensionPack.md @@ -7 +7 @@ Permissions for using the extension packUsing the extension pack schemaCustom li -# Using extension packs with AWS Schema Conversion Tool +# Using AWS SCT extension packs @@ -161 +161 @@ The extension pack wizard appears. - * If you are uploading a new library, then provide the credentials to connect to your AWS account. Use this step only when you convert OLAP databases or ETL scripts. You can use your AWS Command Line Interface (AWS CLI) credentials if you have the AWS CLI installed. You can also use credentials that you previously stored in a profile in the global application settings and associated with the project. If necessary, choose **Navigate to global settings** to configure of associate a different profile with your AWS SCT project. For more information, see [Managing Profiles in the AWS Schema Conversion Tool](./CHAP_UserInterface.Profiles.html). + * If you are uploading a new library, then provide the credentials to connect to your AWS account. Use this step only when you convert OLAP databases or ETL scripts. You can use your AWS Command Line Interface (AWS CLI) credentials if you have the AWS CLI installed. You can also use credentials that you previously stored in a profile in the global application settings and associated with the project. If necessary, choose **Navigate to global settings** to configure of associate a different profile with your AWS SCT project. For more information, see [Storing AWS service profiles in AWS SCT](./CHAP_UserInterface.html#CHAP_UserInterface.Profiles). @@ -178 +178 @@ When you are done, choose **Finish**. - 1. Specify the Amazon S3 bucket in your AWS service profile. Use this step only when you convert OLAP databases or ETL scripts. For more information, see [Managing Profiles in the AWS Schema Conversion Tool](./CHAP_UserInterface.Profiles.html). + 1. Specify the Amazon S3 bucket in your AWS service profile. Use this step only when you convert OLAP databases or ETL scripts. For more information, see [Storing AWS service profiles in AWS SCT](./CHAP_UserInterface.html#CHAP_UserInterface.Profiles). @@ -210 +210 @@ In the preceding example, replace `111122223333:user/DataExtractionAgentName` wi - 2. Convert your source data warehouse schemas. For more information, see [Converting data warehouse schemas](./CHAP_Converting.DW.html). + 2. Convert your source data warehouse schemas. For more information, see [Converting data warehouse schemas to Amazon Redshift](./CHAP_Converting.DW.html). @@ -255 +255 @@ The extension pack wizard appears. - * If you are installing AWS services, provide the credentials to connect to your AWS account. You can use your AWS CLI credentials if you have the AWS CLI installed. You can also use credentials that you previously stored in a profile in the global application settings and associated with the project. If necessary, choose **Navigate to Project Settings** to associate a different profile with the project. If necessary, choose **Global Settings** to create a new profile. For more information, see [Managing Profiles in the AWS Schema Conversion Tool](./CHAP_UserInterface.Profiles.html). + * If you are installing AWS services, provide the credentials to connect to your AWS account. You can use your AWS CLI credentials if you have the AWS CLI installed. You can also use credentials that you previously stored in a profile in the global application settings and associated with the project. If necessary, choose **Navigate to Project Settings** to associate a different profile with the project. If necessary, choose **Global Settings** to create a new profile. For more information, see [Storing AWS service profiles in AWS SCT](./CHAP_UserInterface.html#CHAP_UserInterface.Profiles). @@ -278 +278 @@ When you are done, choose **Finish**. -To update an extension pack and overwrite the old extension pack components, make sure that you use the latest version of AWS SCT. For more information, see [Installing and Configuring AWS Schema Conversion Tool](./CHAP_Installing.html). +To update an extension pack and overwrite the old extension pack components, make sure that you use the latest version of AWS SCT. For more information, see [Installing, verifying, and updating AWS SCT](./CHAP_Installing.html). @@ -326 +326 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -SQL code in Pro*C +Converting SQL code in Pro*C applications