AWS prescriptive-guidance documentation change

Service: prescriptive-guidance · 2026-07-10 · Documentation low

File: prescriptive-guidance/latest/migration-ssis-etl/best-practices.md

Summary

Updated documentation links, fixed apostrophes, revised image paths, and added threading advice for performance

Security assessment

Changes focus on image path corrections, typo fixes, and performance recommendations. No security-specific content (e.g., encryption, access controls, vulnerabilities) is introduced or modified.

Diff

diff --git a/prescriptive-guidance/latest/migration-ssis-etl/best-practices.md b/prescriptive-guidance/latest/migration-ssis-etl/best-practices.md
index 96c144d0c..c0310898e 100644
--- a//prescriptive-guidance/latest/migration-ssis-etl/best-practices.md
+++ b//prescriptive-guidance/latest/migration-ssis-etl/best-practices.md
@@ -5 +5 @@
-[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Migrating SSIS ETL jobs to AWS](welcome.html)
+[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Migrating SSIS ETL jobs to AWS](introduction.html)
@@ -11 +11 @@ Follow these general best practices when migrating your SSIS jobs to AWS:
-  * If you’re migrating your databases to an AWS managed service such as Amazon Relational Database Service (Amazon RDS), descope [maintenance tasks](https://docs.microsoft.com/en-us/sql/integration-services/control-flow/integration-services-tasks) (such as backup, restore, update statistics, or check database integrity) that are not applicable or managed by AWS.
+  * If you're migrating your databases to an AWS managed service such as Amazon Relational Database Service (Amazon RDS), descope [maintenance tasks](https://docs.microsoft.com/en-us/sql/integration-services/control-flow/integration-services-tasks) (such as backup, restore, update statistics, or check database integrity) that are not applicable or managed by AWS.
@@ -19 +19,4 @@ Follow these general best practices when migrating your SSIS jobs to AWS:
-![SSIS package in XML format](/images/prescriptive-guidance/latest/migration-ssis-etl/images/ssis-xml.png)
+![SSIS package in XML format](/images/prescriptive-guidance/latest/migration-ssis-etl/images/guide-img/ae5b08b7-f641-4524-9650-6ac5a0f71dd9/images/911c221a-c9f5-4a6a-a596-0f57176ac2c7.png)
+
+
+
@@ -23 +26 @@ The following illustration shows a sample XML parser.
-![Sample XML parser for SSIS jobs](/images/prescriptive-guidance/latest/migration-ssis-etl/images/ssis-xml-parser.png)
+![Sample XML parser for SSIS jobs](/images/prescriptive-guidance/latest/migration-ssis-etl/images/guide-img/ae5b08b7-f641-4524-9650-6ac5a0f71dd9/images/fc6be370-c6b5-4a87-805c-cc06d9f7c103.png)
@@ -27 +30 @@ The following illustration shows a sample XML parser.
-  * If you’re building custom libraries, implement threading to run tasks in parallel. This improves job performance.
+  * If you're building custom libraries, implement threading to run tasks in parallel. This improves job performance.