AWS prescriptive-guidance documentation change
Summary
Updated documentation links by adding double slashes in AWS documentation URLs
Security assessment
The changes are purely URL formatting corrections with no security context or implications. No security vulnerabilities, configurations, or features were mentioned in these link updates.
Diff
diff --git a/prescriptive-guidance/latest/migration-replatforming-cots-applications/replatforming-backend-databases.md b/prescriptive-guidance/latest/migration-replatforming-cots-applications/replatforming-backend-databases.md index b4881032e..b52de339a 100644 --- a//prescriptive-guidance/latest/migration-replatforming-cots-applications/replatforming-backend-databases.md +++ b//prescriptive-guidance/latest/migration-replatforming-cots-applications/replatforming-backend-databases.md @@ -17 +17 @@ The following sections explain the replatforming approaches for backend database -We recommend that you use an Aurora database if your COTS application supports open-source databases. Using an open-source database helps reduce licensing costs, and you can also use tools such as [AWS Schema Conversion Tool (AWS SCT)](https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_Welcome.html) and [AWS Database Migration Service (AWS DMS)](https://docs.aws.amazon.com/dms/latest/userguide/Welcome.html) to achieve a cutover with minimal downtime during your migration. +We recommend that you use an Aurora database if your COTS application supports open-source databases. Using an open-source database helps reduce licensing costs, and you can also use tools such as [AWS Schema Conversion Tool (AWS SCT)](https://docs.aws.amazon.com//SchemaConversionTool/latest/userguide/CHAP_Welcome.html) and [AWS Database Migration Service (AWS DMS)](https://docs.aws.amazon.com//dms/latest/userguide/Welcome.html) to achieve a cutover with minimal downtime during your migration. @@ -19 +19 @@ We recommend that you use an Aurora database if your COTS application supports o -If your COTS application doesn't support open-source databases, we recommend replatforming to a commercial database on Amazon Relational Database Service (Amazon RDS) such as [Amazon RDS for Oracle](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_Oracle.html) or [Amazon RDS for Microsoft SQL Server](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_SQLServer.html). You should evaluate the database features used by your application and make sure that they are supported in Amazon RDS before you begin your migration. For more information, see [Limits for Microsoft SQL Server database instances](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_SQLServer.html#SQLServer.Concepts.General.FeatureSupport.Limits) in the Amazon RDS documentation. +If your COTS application doesn't support open-source databases, we recommend replatforming to a commercial database on Amazon Relational Database Service (Amazon RDS) such as [Amazon RDS for Oracle](https://docs.aws.amazon.com//AmazonRDS/latest/UserGuide/CHAP_Oracle.html) or [Amazon RDS for Microsoft SQL Server](https://docs.aws.amazon.com//AmazonRDS/latest/UserGuide/CHAP_SQLServer.html). You should evaluate the database features used by your application and make sure that they are supported in Amazon RDS before you begin your migration. For more information, see [Limits for Microsoft SQL Server database instances](https://docs.aws.amazon.com//AmazonRDS/latest/UserGuide/CHAP_SQLServer.html#SQLServer.Concepts.General.FeatureSupport.Limits) in the Amazon RDS documentation. @@ -23 +23 @@ You can also use your remaining database licensing and run self-managed commerci -Finally, we recommend replatforming security-sensitive, high-performance COTS applications that use SQL Server databases to SQL Server running on Amazon EC2 Linux instances. For more information about this, see [Migrating your on-premises SQL Server Windows workloads to Amazon EC2 Linux](https://aws.amazon.com/blogs/database/migrating-your-on-premises-sql-server-windows-workloads-to-amazon-ec2-linux/). +Finally, we recommend replatforming security-sensitive, high-performance COTS applications that use SQL Server databases to SQL Server running on Amazon EC2 Linux instances. For more information about this, see [Migrating your on-premises SQL Server Windows workloads to Amazon EC2 Linux](https://aws.amazon.com//blogs/database/migrating-your-on-premises-sql-server-windows-workloads-to-amazon-ec2-linux/). @@ -27 +27 @@ Finally, we recommend replatforming security-sensitive, high-performance COTS ap -You can reduce your database licensing costs and increase scalability by replatforming your in-house application's backend databases to AWS managed databases (for example, [Amazon RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_PostgreSQL.html), [Amazon RDS for MySQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_MySQL.html), [Aurora](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_AuroraOverview.html), or [Amazon DynamoDB](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Introduction.html)). +You can reduce your database licensing costs and increase scalability by replatforming your in-house application's backend databases to AWS managed databases (for example, [Amazon RDS for PostgreSQL](https://docs.aws.amazon.com//AmazonRDS/latest/UserGuide/CHAP_PostgreSQL.html), [Amazon RDS for MySQL](https://docs.aws.amazon.com//AmazonRDS/latest/UserGuide/CHAP_MySQL.html), [Aurora](https://docs.aws.amazon.com//AmazonRDS/latest/AuroraUserGuide/CHAP_AuroraOverview.html), or [Amazon DynamoDB](https://docs.aws.amazon.com//amazondynamodb/latest/developerguide/Introduction.html)).