AWS Security ChangesHomeSearch

AWS SchemaConversionTool documentation change

Service: SchemaConversionTool · 2025-03-19 · Documentation low

File: SchemaConversionTool/latest/userguide/CHAP_Converting.DW.md

Summary

Updated documentation to reflect Amazon Redshift as the target instead of RDS/Aurora, revised section titles, and updated internal documentation links

Security assessment

Changes focus on service name updates and documentation link formatting without any security-related content or vulnerability mentions

Diff

diff --git a/SchemaConversionTool/latest/userguide/CHAP_Converting.DW.md b/SchemaConversionTool/latest/userguide/CHAP_Converting.DW.md
index d5535f898..e6268abf2 100644
--- a/SchemaConversionTool/latest/userguide/CHAP_Converting.DW.md
+++ b/SchemaConversionTool/latest/userguide/CHAP_Converting.DW.md
@@ -7 +7 @@ Permissions for Amazon RedshiftChoosing optimization strategies and rulesCollect
-# Converting data warehouse schemas to Amazon RDS using AWS SCT
+# Converting data warehouse schemas to Amazon Redshift using AWS SCT
@@ -9 +9 @@ Permissions for Amazon RedshiftChoosing optimization strategies and rulesCollect
-The AWS Schema Conversion Tool (AWS SCT) automates much of the process of converting your data warehouse schema to an Amazon RDS or Aurora database schema. Because the source and target database engines can have many different features and capabilities, AWS SCT attempts to create an equivalent schema in your target database wherever possible. If no direct conversion is possible, AWS SCT provides an assessment report with a list of possible actions for you to take. Using AWS SCT, you can manage keys, map data types and objects, and create manual conversions.
+The AWS Schema Conversion Tool (AWS SCT) automates much of the process of converting your data warehouse schema to an Amazon Redshift database schema. Because the source and target database engines can have many different features and capabilities, AWS SCT attempts to create an equivalent schema in your target database wherever possible. If no direct conversion is possible, AWS SCT provides an assessment report with a list of possible actions for you to take. Using AWS SCT, you can manage keys, map data types and objects, and create manual conversions.
@@ -11 +11 @@ The AWS Schema Conversion Tool (AWS SCT) automates much of the process of conver
-AWS SCT can convert the following data warehouse schemas.
+AWS SCT can convert the following data warehouse schemas to Amazon Redshift.
@@ -36 +36 @@ AWS SCT can convert the following data warehouse schemas.
-For information about converting an online transaction processing (OLTP) database schema, see [Converting database schemas in AWS Schema Conversion Tool](./CHAP_Converting.html). 
+For information about converting an online transaction processing (OLTP) database schema, see [Converting database schemas using AWS SCT](./CHAP_Converting.html). 
@@ -46 +46 @@ You can specify optimization and migration rules in **Settings**. For more infor
-  3. Create a database migration assessment report that details the schema elements that can't be converted automatically. You can use this report to identify where you need to manually create a schema in your target database that is compatible with your source database. For more information about the assessment report, see [Using the assessment report in the AWS Schema Conversion Tool](./CHAP_AssessmentReport.html). 
+  3. Create a database migration assessment report that details the schema elements that can't be converted automatically. You can use this report to identify where you need to manually create a schema in your target database that is compatible with your source database. For more information about the assessment report, see [Creating migration assessment reports with AWS SCT](./CHAP_AssessmentReport.html). 
@@ -92 +92 @@ In the example preceding, replace `user_name` with the name of your user. Then,
-You can apply an extension pack on your target Amazon Redshift database. An extension pack is an add-on module that emulates source database functions that are required when converting objects to Amazon Redshift. For more information, see [Using extension packs with AWS Schema Conversion Tool](./CHAP_ExtensionPack.html).
+You can apply an extension pack on your target Amazon Redshift database. An extension pack is an add-on module that emulates source database functions that are required when converting objects to Amazon Redshift. For more information, see [Using AWS SCT extension packs](./CHAP_ExtensionPack.html).
@@ -292 +292 @@ After you have converted your schema, you can save your project. The schema info
-You can create a database migration assessment report of the items that can't be converted automatically. The assessment report is useful for identifying and resolving schema items that can't be converted automatically. For more information, see [Using the assessment report in the AWS Schema Conversion Tool](./CHAP_AssessmentReport.html). 
+You can create a database migration assessment report of the items that can't be converted automatically. The assessment report is useful for identifying and resolving schema items that can't be converted automatically. For more information, see [Creating migration assessment reports with AWS SCT](./CHAP_AssessmentReport.html). 
@@ -438 +438 @@ You update the schema in your AWS SCT project by choosing **Refresh from databas
-When the AWS Schema Conversion Tool generates converted schema (as shown in Converting your schema using AWS SCT), it doesn't immediately apply the converted schema to the target database. Instead, converted schema are stored locally in your project until you are ready to apply them to the target database. Using this functionality, you can work with schema items that can't be converted automatically to your target database engine. For more information on items that can't be converted automatically, see [Using the assessment report in the AWS Schema Conversion Tool](./CHAP_AssessmentReport.html). 
+When the AWS Schema Conversion Tool generates converted schema (as shown in Converting your schema using AWS SCT), it doesn't immediately apply the converted schema to the target database. Instead, converted schema are stored locally in your project until you are ready to apply them to the target database. Using this functionality, you can work with schema items that can't be converted automatically to your target database engine. For more information on items that can't be converted automatically, see [Creating migration assessment reports with AWS SCT](./CHAP_AssessmentReport.html). 
@@ -511 +511 @@ The extension pack schema is named according to your source database as follows:
-For more information, see [Using extension packs with AWS Schema Conversion Tool](./CHAP_ExtensionPack.html). 
+For more information, see [Using AWS SCT extension packs](./CHAP_ExtensionPack.html). 
@@ -515 +515 @@ For more information, see [Using extension packs with AWS Schema Conversion Tool
-To create custom functions in Amazon Redshift, you use the Python language. Use the AWS SCT extension pack to install python libraries for your Amazon Redshift database. For more information, see [Using extension packs with AWS Schema Conversion Tool](./CHAP_ExtensionPack.html). 
+To create custom functions in Amazon Redshift, you use the Python language. Use the AWS SCT extension pack to install python libraries for your Amazon Redshift database. For more information, see [Using AWS SCT extension packs](./CHAP_ExtensionPack.html). 
@@ -523 +523 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please
-Viewing related transformed objects
+Related transformed objects
@@ -525 +525 @@ Viewing related transformed objects
-Converting Amazon Redshift data
+Optimizing Amazon Redshift