AWS SchemaConversionTool documentation change
Summary
Updated document title from 'New Features' to 'Document history' and corrected multiple internal documentation links. Fixed service name references (changed 'Amazon RDS' to 'Amazon Redshift' in several entries). Improved link text consistency for migration guides.
Security assessment
Changes focus on documentation structure, link corrections, and service name accuracy. The FIPS endpoint references remain unchanged except for link paths, which were already security-related but not newly added. No evidence of addressing vulnerabilities or new security content.
Diff
diff --git a/SchemaConversionTool/latest/userguide/WhatsNew.md b/SchemaConversionTool/latest/userguide/WhatsNew.md index c879a0543..72d189781 100644 --- a/SchemaConversionTool/latest/userguide/WhatsNew.md +++ b/SchemaConversionTool/latest/userguide/WhatsNew.md @@ -7 +7 @@ Earlier updates -# New Features in the AWS Schema Conversion Tool +# Document history @@ -76,2 +76,2 @@ Version | Change | Description | Date changed -1.0.608 | FIPS endpoint support for Amazon S3 | You can now request AWS SCT to connect to Amazon S3 and Amazon Redshift by using FIPS endpoints to comply with Federal Information Processing Standard security requirements. For more information, see [Storing AWS credentials](./CHAP_UserInterface.Profiles.html#CHAP_UserInterface.Profiles.Storing). | November 17, 2017 -1.0.607 | FIPS endpoint support for Amazon S3 | You can now request AWS SCT to connect to Amazon S3 and Amazon Redshift by using FIPS endpoints to comply with Federal Information Processing Standard security requirements. For more information, see [Storing AWS credentials](./CHAP_UserInterface.Profiles.html#CHAP_UserInterface.Profiles.Storing). | October 30, 2017 +1.0.608 | FIPS endpoint support for Amazon S3 | You can now request AWS SCT to connect to Amazon S3 and Amazon Redshift by using FIPS endpoints to comply with Federal Information Processing Standard security requirements. For more information, see [Storing AWS credentials](./CHAP_UserInterface.html#CHAP_UserInterface.Profiles.Storing). | November 17, 2017 +1.0.607 | FIPS endpoint support for Amazon S3 | You can now request AWS SCT to connect to Amazon S3 and Amazon Redshift by using FIPS endpoints to comply with Federal Information Processing Standard security requirements. For more information, see [Storing AWS credentials](./CHAP_UserInterface.html#CHAP_UserInterface.Profiles.Storing). | October 30, 2017 @@ -82,2 +82,2 @@ Version | Change | Description | Date changed -1.0.603 | AWS SCT supports additional data warehouse versions | You can now use the AWS Schema Conversion Tool to convert your Teradata 13 and Oracle Data Warehouse 10 schemas to equivalent Amazon Redshift schemas. For more information, see [Converting data warehouse schemas to Amazon RDS using AWS SCT](./CHAP_Converting.DW.html). | June 16, 2017 -1.0.602 | Data extraction agents support additional data warehouses | You can now use data extraction agents to extract data from your Microsoft SQL Server data warehouses. For more information, see [Migrating data from on-premises data warehouse to Amazon Redshift with AWS Schema Conversion Tool](./agents.html). | May 11, 2017 +1.0.603 | AWS SCT supports additional data warehouse versions | You can now use the AWS Schema Conversion Tool to convert your Teradata 13 and Oracle Data Warehouse 10 schemas to equivalent Amazon Redshift schemas. For more information, see [Converting data warehouse schemas to Amazon Redshift using AWS SCT](./CHAP_Converting.DW.html). | June 16, 2017 +1.0.602 | Data extraction agents support additional data warehouses | You can now use data extraction agents to extract data from your Microsoft SQL Server data warehouses. For more information, see [Migrating data from an on-premises data warehouse to Amazon Redshift](./agents.html). | May 11, 2017 @@ -85,2 +85,2 @@ Version | Change | Description | Date changed -1.0.601 | AWS SCT supports additional data warehouses | You can now use the AWS Schema Conversion Tool to convert your Vertica and Microsoft SQL Server schemas to equivalent Amazon Redshift schemas. For more information, see [Converting data warehouse schemas to Amazon RDS using AWS SCT](./CHAP_Converting.DW.html). | April 18, 2017 -1.0.601 | Data extraction agents support additional data warehouses | You can now use data extraction agents to extract data from your Greenplum, Netezza, and Vertica data warehouses. For more information, see [Migrating data from on-premises data warehouse to Amazon Redshift with AWS Schema Conversion Tool](./agents.html). | April 18, 2017 +1.0.601 | AWS SCT supports additional data warehouses | You can now use the AWS Schema Conversion Tool to convert your Vertica and Microsoft SQL Server schemas to equivalent Amazon Redshift schemas. For more information, see [Converting data warehouse schemas to Amazon Redshift using AWS SCT](./CHAP_Converting.DW.html). | April 18, 2017 +1.0.601 | Data extraction agents support additional data warehouses | You can now use data extraction agents to extract data from your Greenplum, Netezza, and Vertica data warehouses. For more information, see [Migrating data from an on-premises data warehouse to Amazon Redshift](./agents.html). | April 18, 2017 @@ -89 +89 @@ Version | Change | Description | Date changed -1.0.600 | Data Extraction Agents | You can now install data extraction agents that extract data from your data warehouse and prepare it for use with Amazon Redshift. You can use the AWS Schema Conversion Tool to register the agents and create data extraction tasks for them. For more information, see [Migrating data from on-premises data warehouse to Amazon Redshift with AWS Schema Conversion Tool](./agents.html). | February 16, 2017 +1.0.600 | Data Extraction Agents | You can now install data extraction agents that extract data from your data warehouse and prepare it for use with Amazon Redshift. You can use the AWS Schema Conversion Tool to register the agents and create data extraction tasks for them. For more information, see [Migrating data from an on-premises data warehouse to Amazon Redshift](./agents.html). | February 16, 2017 @@ -91,5 +91,5 @@ Version | Change | Description | Date changed -1.0.502 | Integration with AWS DMS | You can now use the AWS Schema Conversion Tool to create AWS DMS endpoints and tasks. You can run and monitor the tasks from AWS SCT. For more information, see [Integrating AWS Database Migration Service with AWS Schema Conversion Tool](./CHAP_DMSIntegration.html). | December 20, 2016 -1.0.502 | Amazon Aurora with PostgreSQL compatibility as a target database | The AWS Schema Conversion Tool now supports Amazon Aurora with PostgreSQL compatibility as a target database. For more information, see [Converting database schemas in AWS Schema Conversion Tool](./CHAP_Converting.html). | December 20, 2016 -1.0.502 | Support for profiles | You can now store different profiles in the AWS Schema Conversion Tool and easily switch between them. For more information, see [Managing Profiles in the AWS Schema Conversion Tool](./CHAP_UserInterface.Profiles.html). | December 20, 2016 -1.0.501 | Support for Greenplum Database and Netezza | You can now use the AWS Schema Conversion Tool to convert your data warehouse schemas from Greenplum Database and Netezza to Amazon Redshift. For more information, see [Converting data warehouse schemas to Amazon RDS using AWS SCT](./CHAP_Converting.DW.html). | November 17, 2016 -1.0.501 | Redshift optimization | You can now use the AWS Schema Conversion Tool to optimize your Amazon Redshift databases. For more information, see [Converting data from Amazon Redshift using AWS Schema Conversion Tool](./CHAP_Converting.DW.RedshiftOpt.html). | November 17, 2016 +1.0.502 | Integration with AWS DMS | You can now use the AWS Schema Conversion Tool to create AWS DMS endpoints and tasks. You can run and monitor the tasks from AWS SCT. For more information, see [Using AWS SCT with AWS DMS](./CHAP_DMSIntegration.html). | December 20, 2016 +1.0.502 | Amazon Aurora with PostgreSQL compatibility as a target database | The AWS Schema Conversion Tool now supports Amazon Aurora with PostgreSQL compatibility as a target database. For more information, see [Converting database schemas using AWS SCT](./CHAP_Converting.html). | December 20, 2016 +1.0.502 | Support for profiles | You can now store different profiles in the AWS Schema Conversion Tool and easily switch between them. For more information, see [Storing AWS service profiles in AWS SCT](./CHAP_UserInterface.html#CHAP_UserInterface.Profiles). | December 20, 2016 +1.0.501 | Support for Greenplum Database and Netezza | You can now use the AWS Schema Conversion Tool to convert your data warehouse schemas from Greenplum Database and Netezza to Amazon Redshift. For more information, see [Converting data warehouse schemas to Amazon Redshift using AWS SCT](./CHAP_Converting.DW.html). | November 17, 2016 +1.0.501 | Redshift optimization | You can now use the AWS Schema Conversion Tool to optimize your Amazon Redshift databases. For more information, see [Optimizing Amazon Redshift by using AWS SCT](./CHAP_Converting.DW.RedshiftOpt.html). | November 17, 2016 @@ -97,2 +97,2 @@ Version | Change | Description | Date changed -1.0.500 | Move to cloud | You can now use the AWS Schema Conversion Tool to copy your existing on-premises database schema to an Amazon RDS DB instance running the same engine. You can use this feature to analyze potential cost savings of moving to the cloud and of changing your license type. For more information, see [Using the assessment report in the AWS Schema Conversion Tool](./CHAP_AssessmentReport.html). | October 4, 2016 -1.0.400 | Data warehouse schema conversions | You can now use the AWS Schema Conversion Tool to convert your data warehouse schemas from Oracle and Teradata to Amazon Redshift. For more information, see [Converting data warehouse schemas to Amazon RDS using AWS SCT](./CHAP_Converting.DW.html). | July 13, 2016 +1.0.500 | Move to cloud | You can now use the AWS Schema Conversion Tool to copy your existing on-premises database schema to an Amazon RDS DB instance running the same engine. You can use this feature to analyze potential cost savings of moving to the cloud and of changing your license type. For more information, see [Creating migration assessment reports with AWS SCT](./CHAP_AssessmentReport.html). | October 4, 2016 +1.0.400 | Data warehouse schema conversions | You can now use the AWS Schema Conversion Tool to convert your data warehouse schemas from Oracle and Teradata to Amazon Redshift. For more information, see [Converting data warehouse schemas to Amazon Redshift using AWS SCT](./CHAP_Converting.DW.html). | July 13, 2016