AWS AmazonRDS documentation change
Summary
Updated documentation to generalize references from 'Amazon Redshift' to 'supported data warehouse' terminology
Security assessment
Changes only update terminology to remove Amazon Redshift-specific references without altering security-related content. The existing security note about immutable AWS KMS keys remains unchanged. No evidence of addressing vulnerabilities or adding security controls.
Diff
diff --git a/AmazonRDS/latest/AuroraUserGuide/zero-etl.modifying.md b/AmazonRDS/latest/AuroraUserGuide/zero-etl.modifying.md index ead58a0e6..5f3a914d2 100644 --- a//AmazonRDS/latest/AuroraUserGuide/zero-etl.modifying.md +++ b//AmazonRDS/latest/AuroraUserGuide/zero-etl.modifying.md @@ -5 +5 @@ -# Modifying Aurora zero-ETL integrations with Amazon Redshift +# Modifying Aurora zero-ETL integrations @@ -7 +7 @@ -You can modify only the name, description, and data filtering options for a zero-ETL integration with Amazon Redshift. You can't modify the AWS KMS key used to encrypt the integration, or the source or target databases. +You can modify only the name, description, and data filtering options for a zero-ETL integration in a supported data warehouse. You can't modify the AWS KMS key used to encrypt the integration, or the source or target databases. @@ -9 +9 @@ You can modify only the name, description, and data filtering options for a zero -If you add a data filter to an existing integration, Aurora reevaluates the filter as if it always existed. It removes any data that is currently in the target Amazon Redshift data warehouse that doesn't match the new filtering criteria. If you _remove_ a data filter from an integration, it replicates any data that previously didn't match the filtering criteria (but now does) into the target data warehouse. For more information, see [Data filtering for Aurora zero-ETL integrations with Amazon Redshift](./zero-etl.filtering.html). +If you add a data filter to an existing integration, Aurora reevaluates the filter as if it always existed. It removes any data that is currently in the target data warehouse that doesn't match the new filtering criteria. If you _remove_ a data filter from an integration, it replicates any data that previously didn't match the filtering criteria (but now does) into the target data warehouse. For more information, see [Data filtering for Aurora zero-ETL integrations](./zero-etl.filtering.html). @@ -32 +32 @@ To modify a zero-ETL integration using the AWS CLI, call the [modify-integration - * `--data-filter` – Specify data filtering options for the integration. For more information, see [Data filtering for Aurora zero-ETL integrations with Amazon Redshift](./zero-etl.filtering.html). + * `--data-filter` – Specify data filtering options for the integration. For more information, see [Data filtering for Aurora zero-ETL integrations](./zero-etl.filtering.html).