AWS prescriptive-guidance documentation change
Summary
Updated navigation links, standardized terminology to 'Amazon EC2', changed image path, and updated link to log shipping documentation.
Security assessment
Changes involve cosmetic updates (links, terminology), image relocation, and documentation path adjustments. No security vulnerabilities, configurations, or mitigations are mentioned. Log shipping functionality remains described as before without security enhancements.
Diff
diff --git a/prescriptive-guidance/latest/migration-sql-server/log-shipping.md b/prescriptive-guidance/latest/migration-sql-server/log-shipping.md index 2c36782aa..ed9e68b47 100644 --- a//prescriptive-guidance/latest/migration-sql-server/log-shipping.md +++ b//prescriptive-guidance/latest/migration-sql-server/log-shipping.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Migrating Microsoft SQL Server databases to the AWS Cloud](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Migrating Microsoft SQL Server databases to the AWS Cloud](introduction.html) @@ -9 +9 @@ -You can use log shipping to send transaction log backups from your primary, on-premises SQL Server database to one or more secondary (warm standby) SQL Server databases that are deployed on EC2 instances or Amazon RDS for SQL Server DB instances in the AWS Cloud. To set up log shipping on Amazon RDS for SQL Server, you have to use your own custom scripts. +You can use log shipping to send transaction log backups from your primary, on-premises SQL Server database to one or more secondary (warm standby) SQL Server databases that are deployed on Amazon EC2 instances or Amazon RDS for SQL Server DB instances in the AWS Cloud. To set up log shipping on Amazon RDS for SQL Server, you have to use your own custom scripts. @@ -11 +11 @@ You can use log shipping to send transaction log backups from your primary, on-p -In this scenario, you configure a warm standby SQL Server database on an EC2 instance or Amazon RDS for SQL Server DB instance, and send transaction log backups asynchronously between your on-premises database and the warm standby server in the AWS Cloud. The transaction log backups are then applied to the warm standby database. When all the logs have been applied, you can perform a manual failover and cut over to the cloud. +In this scenario, you configure a warm standby SQL Server database on an Amazon EC2 instance or Amazon RDS for SQL Server DB instance, and send transaction log backups asynchronously between your on-premises database and the warm standby server in the AWS Cloud. The transaction log backups are then applied to the warm standby database. When all the logs have been applied, you can perform a manual failover and cut over to the cloud. @@ -15 +15 @@ This option supports all versions and editions of SQL Server. After you have mig - + @@ -17 +17 @@ This option supports all versions and editions of SQL Server. After you have mig -For more information about using this method to achieve high availability, data protection, and disaster recovery for your SQL Server databases on Amazon EC2, see [Log shipping](./ec2-log-shipping.html) in the _Amazon EC2 for SQL Server_ section. +For more information about using this method to achieve high availability, data protection, and disaster recovery for your SQL Server databases on Amazon EC2, see [Log shipping](./ec2-sql-ha.html#ec2-log-shipping) in the _Amazon EC2 for SQL Server_ section.