AWS AmazonRDS documentation change
Summary
Updated service name from 'QuickSight' to 'Quick Suite' and added a limitation prohibiting zero-ETL integrations with databases using magnetic storage
Security assessment
The change adds a technical limitation about magnetic storage compatibility but provides no evidence of addressing a security vulnerability. The QuickSight/Quick Suite change appears to be a branding update.
Diff
diff --git a/AmazonRDS/latest/UserGuide/zero-etl.md b/AmazonRDS/latest/UserGuide/zero-etl.md index b64a29a7c..ddbb493aa 100644 --- a//AmazonRDS/latest/UserGuide/zero-etl.md +++ b//AmazonRDS/latest/UserGuide/zero-etl.md @@ -11 +11 @@ An Amazon RDS zero-ETL integration with Amazon Redshift and Amazon SageMaker AI -A zero-ETL integration makes the data in your RDS database available in Amazon Redshift or an Amazon SageMaker AI lakehouse in near real-time. Once that data is in the target data warehouse or data lake, you can power your analytics, ML, and AI workloads using the built-in capabilities, such as machine learning, materialized views, data sharing, federated access to multiple data stores and data lakes, and integrations with Amazon SageMaker AI, QuickSight, and other AWS services. +A zero-ETL integration makes the data in your RDS database available in Amazon Redshift or an Amazon SageMaker AI lakehouse in near real-time. Once that data is in the target data warehouse or data lake, you can power your analytics, ML, and AI workloads using the built-in capabilities, such as machine learning, materialized views, data sharing, federated access to multiple data stores and data lakes, and integrations with Amazon SageMaker AI, Quick Suite, and other AWS services. @@ -159,0 +160,2 @@ The following limitations apply to RDS zero-ETL integrations. + * You can't create an integration for a source database that uses magnetic storage. +