AWS AmazonRDS documentation change
Summary
Removed topics list, updated documentation links, added operational notes about refresh/resync limitations and catalog name length restrictions. Modified permissions description.
Security assessment
Changes focus on operational guidance and documentation structure updates. Added notes about refresh limitations and catalog naming are functional constraints rather than security issues. Permission changes maintain existing security posture without introducing new security considerations.
Diff
diff --git a/AmazonRDS/latest/UserGuide/zero-etl.creating.md b/AmazonRDS/latest/UserGuide/zero-etl.creating.md index b3941f216..27b33182e 100644 --- a//AmazonRDS/latest/UserGuide/zero-etl.creating.md +++ b//AmazonRDS/latest/UserGuide/zero-etl.creating.md @@ -11,15 +10,0 @@ When you create an Amazon RDS zero-ETL integration, you specify the source RDS d -###### Topics - - * Prerequisites - - * Required permissions - - * Creating zero-ETL integrations - - * Encrypting integrations with a customer managed key - - * Next steps - - - - @@ -30 +15 @@ Before you create a zero-ETL integration, you must create a source database and -For instructions to complete each of these steps, see [Getting started with Amazon RDS zero-ETL integrations with Amazon Redshift](./zero-etl.setting-up.html). +For instructions to complete each of these steps, see [Getting started with Amazon RDS zero-ETL integrations](./zero-etl.setting-up.html). @@ -40 +25 @@ Certain IAM permissions are required to create a zero-ETL integration. At minimu - * Create inbound integrations into the target data warehouse. You don't need this permission if the same account owns the Amazon Redshift data warehouse and this account is an authorized principal for that data warehouse. For information about adding authorized principals, see [Configure authorization for your Amazon Redshift data warehouse](https://docs.aws.amazon.com/redshift/latest/mgmt/zero-etl-using.setting-up.html#zero-etl-using.redshift-iam). + * Create inbound integrations into the target data warehouse. @@ -45 +30 @@ Certain IAM permissions are required to create a zero-ETL integration. At minimu -The following sample policy demonstrates the [least privilege permissions](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#grant-least-privilege) required to create and manage integrations. You might not need these exact permissions if your user or role has broader permissions, such as an `AdministratorAccess` managed policy. +The following sample policies demonstrate the [least privilege permissions](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#grant-least-privilege) required to create and manage integrations. You might not need these exact permissions if your user or role has broader permissions, such as an `AdministratorAccess` managed policy. @@ -164,0 +150,4 @@ You can create a zero-ETL integration using the AWS Management Console, the AWS +###### Important + +zero-ETL integrations do not support refresh or resync operations. If you encounter issues with an integration after creation, you must delete the integration and create a new one. + @@ -176,0 +166,4 @@ By default, RDS for MySQL immediately purges binary log files. Because zero-ETL +###### Important + +Catalog names are limited to 19 characters in length. Ensure your integration identifier meets this requirement if it will be used as a catalog name. + @@ -235,0 +229,4 @@ To create a zero-ETL integration using the AWS CLI, use the [create-integration] +###### Note + +Remember that catalog names are limited to 19 characters. Choose your integration name accordingly if it will be used as a catalog name. + @@ -262,0 +260,4 @@ To create a zero-ETL integration by using the Amazon RDS API, use the [`CreateIn +###### Note + +Catalog names are limited to 19 characters. Ensure your IntegrationName parameter meets this requirement if it will be used as a catalog name. + @@ -368 +369 @@ Getting started with zero-ETL integrations -Data filtering for zero-ETL integrations +Creating zero-ETL integrations with an Amazon SageMaker lakehouse