AWS redshift documentation change
Summary
Removed technical detail about concurrency scaling behavior during Zero-ETL integration sync writes
Security assessment
The change removes operational details about concurrency scaling behavior but contains no security context, vulnerabilities, or security feature documentation
Diff
diff --git a/redshift/latest/mgmt/zero-etl.reqs-lims.md b/redshift/latest/mgmt/zero-etl.reqs-lims.md index b08e77322..6dceb1168 100644 --- a//redshift/latest/mgmt/zero-etl.reqs-lims.md +++ b//redshift/latest/mgmt/zero-etl.reqs-lims.md @@ -45 +45 @@ For information about how to add a primary key to Amazon Aurora PostgreSQL, see - * Zero-ETL integration runs in Amazon Redshift using parallel connections. It runs using the credentials of the user who created the database from the integration. When the query runs, concurrency scaling does not kick in for these connections during the sync (writes). Concurrency scaling reads (from Amazon Redshift clients) works for synced objects. + * Zero-ETL integration runs in Amazon Redshift using parallel connections. It runs using the credentials of the user who created the database from the integration.