AWS prescriptive-guidance documentation change
Summary
Updated document title, links, and product references; added IAM role requirement for S3 integration; minor grammatical fixes
Security assessment
The change adds explicit guidance about setting up IAM roles for secure S3 bucket access during SQL Server migrations. This addresses potential misconfiguration risks by emphasizing proper permission management, but doesn't fix a specific vulnerability. The update prevents insecure access patterns by requiring least-privilege permissions.
Diff
diff --git a/prescriptive-guidance/latest/migration-sql-server/best-practices.md b/prescriptive-guidance/latest/migration-sql-server/best-practices.md index 1da7b86e2..4dbfad878 100644 --- a//prescriptive-guidance/latest/migration-sql-server/best-practices.md +++ b//prescriptive-guidance/latest/migration-sql-server/best-practices.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 @@ Provisioning your target databaseBacking up from your source databaseTransferrin -# Best practices for migrating to Amazon RDS for SQL Server +# Best practices for migrating to RDS for SQL Server @@ -54 +54 @@ If you have limited downtime, you can use native SQL Server backup/restore with - * If you’re using Direct Connect, which provides high bandwidth connectivity between your on-premises environment and AWS, you can copy your SQL Server backups to Amazon S3 and set up [Amazon S3 integration](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/User.SQLServer.Options.S3-integration.html). + * If you're using AWS Direct Connect, which provides high bandwidth connectivity between your on-premises environment and AWS, you can copy your SQL Server backups to Amazon S3 and set up [Amazon S3 integration](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/User.SQLServer.Options.S3-integration.html). You will have to set up an AWS Identity and Access Management (IAM) role to allow Amazon S3 bucket access to Amazon RDS. @@ -56 +56 @@ If you have limited downtime, you can use native SQL Server backup/restore with - * If you don’t have high bandwidth through Direct Connect, use AWS Snowball Edge to transfer large database backup files. You can also use AWS DMS to transfer the data when replication is required. + * If you don't have high bandwidth through AWS Direct Connect, use AWS Snowball to transfer large database backup files. You can also use AWS DMS to transfer the data when replication is required. @@ -63 +63 @@ If you have limited downtime, you can use native SQL Server backup/restore with - * If you’re migrating a very large database, we recommend that you provision a bigger [Amazon RDS instance type](https://aws.amazon.com/rds/instance-types/) initially, for the duration of the migration, for faster data loads. + * If you're migrating a very large database, we recommend that you provision a bigger [Amazon RDS instance type](https://aws.amazon.com/rds/instance-types/) initially, for the duration of the migration, for faster data loads. @@ -112 +112 @@ For additional validation during the proof-of-concept (POC) phase, we recommend - * Test database failover, recovery, and restoration to make sure that you’re meeting RPO and RTO requirements. + * Test database failover, recovery, and restoration to make sure that you're meeting RPO and RTO requirements. @@ -127 +127 @@ When your database is on AWS, make sure that you are following best practices in - * Set up alerts by using SNS topics. + * Set up alerts by using Amazon SNS topics. @@ -144 +144 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -AWS Launch Wizard +AWS Launch Wizard for SQL Server