AWS Glue zero-ETL Integrations Gain Table Property Ownership and Conflict Detection
AWS Glue zero-ETL integrations now feature conflict detection and integration ownership tracking for target table properties. This enhancement prevents multiple integrations from unknowingly targeting the same table in Amazon S3 or SageMaker Lakehouse catalogs. Data teams benefit from predictable control, ensuring pipeline isolation and data lands exactly as intended. This functionality is broadly available across all supported AWS Commercial and GovCloud (US) Regions.
Features (1) ›
- Add table property ownership and conflict detection for zero-ETL integrations
AWS Glue zero-ETL integrations now associate table properties with their owning integration, preventing two integrations from unknowingly targeting the same table. This ensures predictable control and pipeline isolation, guiding users to choose different targets or update existing integrations if conflicts are detected across Amazon S3 Tables and SageMaker Lakehouse catalogs.
https://aws.amazon.com/about-aws/whats-new/2026/09/glue-zero-etl-ownership-conflicts/
Related releases
- AWS Lambda adds direct read configuration for Amazon S3 Files AWS What's New ·
- SageMaker HyperPod adds model caching for faster inference autoscaling AWS What's New ·
- Amazon Bedrock Knowledge Base adds TwelveLabs Marengo 3.0 for multimodal embeddings AWS What's New ·
- AWS Lambda recursive loop detection now available in Europe Sovereign Cloud AWS What's New ·
- AWS Storage Gateway adds FIPS-compliant private connectivity for S3 File Gateway AWS What's New ·
- Amazon API Gateway now supports 1 MB execution logs with configurable delivery destinations AWS What's New ·