AWS AmazonRDS documentation change
Summary
Removed Topics section headers and made various documentation updates including: simplified IAM permission requirements, added important notes about catalog name length limitations and integration refresh limitations, updated cross-reference links, and added operational notes for CLI/API usage.
Security assessment
Changes focus on documentation structure, operational constraints, and permission clarifications rather than addressing security vulnerabilities. The IAM permission changes simplify explanations but don't introduce new security controls. Added notes about catalog name length and refresh limitations are operational rather than security-related.
Diff
diff --git a/AmazonRDS/latest/AuroraUserGuide/zero-etl.creating.md b/AmazonRDS/latest/AuroraUserGuide/zero-etl.creating.md index b1ab9fd1a..84a53b6ea 100644 --- a//AmazonRDS/latest/AuroraUserGuide/zero-etl.creating.md +++ b//AmazonRDS/latest/AuroraUserGuide/zero-etl.creating.md @@ -11,15 +10,0 @@ When you create an Aurora zero-ETL integration, you specify the source Aurora DB -###### 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 DB cluster an -For instructions to complete each of these steps, see [Getting started with Aurora zero-ETL integrations with Amazon Redshift](./zero-etl.setting-up.html). +For instructions to complete each of these steps, see [Getting started with Aurora 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. + @@ -174,0 +164,4 @@ You can create a zero-ETL integration using the AWS Management Console, the AWS +###### 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. + @@ -185 +178 @@ Modifying DB cluster parameters requires a reboot. Before you can create the int - 7. (Optional) Select **Customize data filtering options** and add data filters to your integration. You can use data filters to define the scope of replication to the target data warehouse. For more information, see [Data filtering for Aurora zero-ETL integrations with Amazon Redshift](./zero-etl.filtering.html). + 7. (Optional) Select **Customize data filtering options** and add data filters to your integration. You can use data filters to define the scope of replication to the target data warehouse. For more information, see [Data filtering for Aurora zero-ETL integrations](./zero-etl.filtering.html). @@ -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