AWS AmazonRDS documentation change
Summary
Added troubleshooting section for Amazon SageMaker lakehouse integrations and clarified that resync/refresh operations are unavailable for them
Security assessment
The changes add procedural guidance for SageMaker integrations but contain no security vulnerability fixes or security feature documentation. Focuses on operational troubleshooting steps rather than security controls.
Diff
diff --git a/AmazonRDS/latest/UserGuide/zero-etl.troubleshooting.md b/AmazonRDS/latest/UserGuide/zero-etl.troubleshooting.md index 895071864..20cc0353a 100644 --- a//AmazonRDS/latest/UserGuide/zero-etl.troubleshooting.md +++ b//AmazonRDS/latest/UserGuide/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 resync +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 integrations @@ -7 +7 @@ I can't create a zero-ETL integrationMy integration is stuck in a state of Synci -# Troubleshooting Amazon RDS zero-ETL integrations with Amazon Redshift +# Troubleshooting Amazon RDS 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 Amazon RDS zero-ETL integrations with Amazon Redshift. +Use the following information to troubleshoot common issues with Amazon RDS 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 Amazon RDS zero + * Integration failed issues for Amazon SageMaker lakehouse zero-ETL integrations + @@ -30 +36 @@ 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 DB engines for Amazon RDS zero-ETL integrations with Amazon Redshift](./Concepts.RDS_Fea_Regions_DB-eng.Feature.ZeroETL.html). + * Your source database must be running a supported DB engine version. For a list of supported versions, see [Supported Regions and DB engines for Amazon RDS zero-ETL integrations](./Concepts.RDS_Fea_Regions_DB-eng.Feature.ZeroETL.html). @@ -106,0 +113,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. +