AWS prescriptive-guidance documentation change
Summary
Updated documentation links, fixed apostrophe usage, adjusted table formatting, and minor text edits for consistency
Security assessment
Changes involve formatting, typo corrections, and link updates. No security-related content was added or modified. The changes do not address vulnerabilities or security features.
Diff
diff --git a/prescriptive-guidance/latest/migration-ssis-etl/approach.md b/prescriptive-guidance/latest/migration-ssis-etl/approach.md index 5db475e49..9d9c5cf5b 100644 --- a//prescriptive-guidance/latest/migration-ssis-etl/approach.md +++ b//prescriptive-guidance/latest/migration-ssis-etl/approach.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) @@ -9 +9 @@ -To decide on a migration approach, you use the analysis you performed on existing patterns in the previous phase. Your organization’s future data and analytics needs are equally important considerations. Traditional on-premises ETL tools deal with relational data models and structured data. If you have semi-structured and unstructured data to process, you can use AWS services such as AWS Glue or Amazon EMR for the migration. Other factors that can influence the migration approach include: +To decide on a migration approach, you use the analysis you performed on existing patterns in the previous phase. Your organization's future data and analytics needs are equally important considerations. Traditional on-premises ETL tools deal with relational data models and structured data. If you have semi-structured and unstructured data to process, you can use AWS services such as AWS Glue or Amazon EMR for the migration. Other factors that can influence the migration approach include: @@ -24 +24 @@ You can select from three migration approaches: big bang, phased, and lift and s -**Approach** | **Description** | **Use case** | **Advantages and disadvantages** +Approach| Description| Use case| Advantages and disadvantages @@ -52 +52 @@ Lift and shift | Migrate the current architecture as is to AWS. | - * You don’t have the resources to plan a migration immediately. + * You don't have the resources to plan a migration immediately. @@ -62 +62 @@ Lift and shift | Migrate the current architecture as is to AWS. | -A comparison of data on the source and target systems is fundamental for a successful migration. Because the existing production system gets regular updates from source systems, this comparison might become confusing. For this reason, when you’re determining your migration approach, we recommend that you also decide on your data validation strategy. +A comparison of data on the source and target systems is fundamental for a successful migration. Because the existing production system gets regular updates from source systems, this comparison might become confusing. For this reason, when you're determining your migration approach, we recommend that you also decide on your data validation strategy.