AWS AmazonRDS documentation change
Summary
Added troubleshooting guidance for Amazon SageMaker lakehouse zero-ETL integrations, clarified monitoring destinations, and explicitly stated that resync/refresh operations are unavailable for SageMaker integrations requiring recreation
Security assessment
Changes focus on operational procedures and troubleshooting steps for integration failures. No security vulnerabilities, access controls, or encryption methods are mentioned. The added content addresses failure recovery processes rather than security aspects
Diff
diff --git a/AmazonRDS/latest/AuroraUserGuide/zero-etl.troubleshooting.md b/AmazonRDS/latest/AuroraUserGuide/zero-etl.troubleshooting.md index 21cc820fd..175966b0e 100644 --- a//AmazonRDS/latest/AuroraUserGuide/zero-etl.troubleshooting.md +++ b//AmazonRDS/latest/AuroraUserGuide/zero-etl.troubleshooting.md @@ -5 +5 @@ -I can't create a zero-ETL integrationMy integration is stuck in a state of SyncingMy tables aren't replicating to Amazon RedshiftOne or more of my Amazon Redshift tables requires a resyncDDL operations that aren't complete appear in Amazon Redshift +I can't create a zero-ETL integrationMy integration is stuck in a state of SyncingMy tables aren't replicating to Amazon RedshiftOne or more of my Amazon Redshift tables requires a resyncIntegration failed issues for Amazon SageMaker lakehouse zero-ETL integrationsDDL operations that aren't complete appear in Amazon Redshift @@ -7 +7 @@ I can't create a zero-ETL integrationMy integration is stuck in a state of Synci -# Troubleshooting Aurora zero-ETL integrations with Amazon Redshift +# Troubleshooting Aurora zero-ETL integrations @@ -9 +9 @@ I can't create a zero-ETL integrationMy integration is stuck in a state of Synci -You can check the state of a zero-ETL integration by querying the [SVV_INTEGRATION](https://docs.aws.amazon.com/redshift/latest/dg/r_SVV_INTEGRATION.html) system table in Amazon Redshift. If the `state` column has a value of `ErrorState`, it means something's wrong. For more information, see [Monitoring integrations using system tables](./zero-etl.describingmonitoring.html#zero-etl.monitoring). +You can check the state of a zero-ETL integration by querying the [SVV_INTEGRATION](https://docs.aws.amazon.com/redshift/latest/dg/r_SVV_INTEGRATION.html) system table in the analytics destination. If the `state` column has a value of `ErrorState`, it means something's wrong. For more information, see [Monitoring integrations using system tables for Amazon Redshift](./zero-etl.describingmonitoring.html#zero-etl.monitoring). @@ -11 +11,5 @@ You can check the state of a zero-ETL integration by querying the [SVV_INTEGRATI -Use the following information to troubleshoot common issues with Aurora zero-ETL integrations with Amazon Redshift. +Use the following information to troubleshoot common issues with Aurora zero-ETL integrations. + +###### Important + +Resync and refresh operations are not available for zero-ETL integrations with an Amazon SageMaker lakehouse. If there are issues with an integration, you must delete the integration and create a new integration. You cannot refresh or resync an existing integration. @@ -22,0 +27,2 @@ Use the following information to troubleshoot common issues with Aurora zero-ETL + * Integration failed issues for Amazon SageMaker lakehouse zero-ETL integrations + @@ -32 +38 @@ If you can't create a zero-ETL integration, make sure that the following are cor - * Your source database must be running a supported DB engine version. For a list of supported versions, see [Supported Regions and Aurora DB engines for zero-ETL integrations with Amazon Redshift](./Concepts.Aurora_Fea_Regions_DB-eng.Feature.Zero-ETL.html). + * Your source database must be running a supported DB engine version. For a list of supported versions, see [Supported Regions and Aurora DB engines for zero-ETL integrations](./Concepts.Aurora_Fea_Regions_DB-eng.Feature.Zero-ETL.html). @@ -115,0 +122,17 @@ Performing multiple column operations within a single command | +## Integration failed issues for Amazon SageMaker lakehouse zero-ETL integrations + +If you encounter issues with an existing zero-ETL integration with an Amazon SageMaker lakehouse, the only resolution is to delete the integration and create a new one. Unlike other AWS services, zero-ETL integrations do not support refresh or resync operations. + +To resolve integration issues: + + 1. Delete the problematic zero-ETL integration using the console, CLI, or API. + + 2. Verify that the source database and target data warehouse configurations are correct. + + 3. Create a new zero-ETL integration with the same or updated configuration. + + + + +This process will result in a complete re-initialization of the data pipeline, which may take time depending on the size of your source database. +