AWS redshift medium security documentation change
Summary
Updated event notification messages for Zero-ETL integrations, including improved guidance for authorization failures involving KMS keys
Security assessment
The change to event REDSHIFT-INTEGRATION-EVENT-0008 adds specific guidance to check KMS key permissions when using customer-managed keys. This addresses a potential security misconfiguration scenario where revoked permissions could lead to authorization failures, making it security-related.
Diff
diff --git a/redshift/latest/mgmt/integration-event-notifications.md b/redshift/latest/mgmt/integration-event-notifications.md index 66e5161a4..2ce059e86 100644 --- a//redshift/latest/mgmt/integration-event-notifications.md +++ b//redshift/latest/mgmt/integration-event-notifications.md @@ -28,9 +28,9 @@ Amazon Redshift Category | External Event ID | Event Severity | Message Descript -Monitoring | REDSHIFT-INTEGRATION-EVENT-0000 | INFO | Zero-ETL integration <integration name> has been created and is now ACTIVE. -Monitoring | REDSHIFT-INTEGRATION-EVENT-0001 | INFO | Zero-ETL integration <integration name> was deleted at <time in UTC>. -Monitoring | REDSHIFT-INTEGRATION-EVENT-0002 | INFO | Initiated deletion of zero-ETL integration <integration name> at <time in UTC>. -Monitoring | REDSHIFT-INTEGRATION-EVENT-0003 | INFO | Zero-ETL integration <integration name> is syncing transactional data to the target data warehouse. -Monitoring | REDSHIFT-INTEGRATION-EVENT-0004 | WARNING | One or more tables doesn't have a primary key and can't be synchronized. Take a backup on Amazon RDS, drop these tables, and recreate them following the Amazon Redshift best practices for designing tables. -Monitoring | REDSHIFT-INTEGRATION-EVENT-0005 | WARNING | One or more tables can't be synchronized because they contain unsupported data types or lengths. Fix the tables and try again. For unsupported data types, see [Unsupported data types](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/zero-etl.html#zero-etl.limitations.data-types). -Monitoring | REDSHIFT-INTEGRATION-EVENT-0006 | ERROR | Unable to create integration. Delete and recreate the integration. -Monitoring | REDSHIFT-INTEGRATION-EVENT-0007 | ERROR | Unable to load data due to an internal failure. Delete and recreate the integration. -Monitoring | REDSHIFT-INTEGRATION-EVENT-0008 | ERROR | Authorization failed because permissions have been revoked from the source Aurora DB cluster. Delete and recreate the integration. +Monitoring | REDSHIFT-INTEGRATION-EVENT-0000 | INFO | Your zero-ETL Integration <integration name> has been created and became ACTIVE at <time in UTC>. +Monitoring | REDSHIFT-INTEGRATION-EVENT-0001 | INFO | Your zero-ETL Integration <integration name> has been deleted at <time in UTC>. +Monitoring | REDSHIFT-INTEGRATION-EVENT-0002 | INFO | Your zero-ETL Integration <integration name> has initiated deletion at <time in UTC>. +Monitoring | REDSHIFT-INTEGRATION-EVENT-0003 | INFO | Your zero-ETL Integration <integration name> is synchronizing transactional data to the Amazon Redshift data warehouse. +Monitoring | REDSHIFT-INTEGRATION-EVENT-0004 | WARNING | Amazon Redshift cannot replicate the table because the table is missing a primary key. Add primary key(s) to the source table and the table will resynchronize automatically. +Monitoring | REDSHIFT-INTEGRATION-EVENT-0005 | WARNING | Amazon Redshift cannot replicate the table because one or more columns use an unsupported data type. Modify your integration to exclude this table in the filter, or drop column(s) from source table and run 'ALTER DATABASE <Redshift database name> INTEGRATION REFRESH TABLE <schema name>.<table name>' to synchronize this table. +Monitoring | REDSHIFT-INTEGRATION-EVENT-0006 | ERROR | Unable to create integration. Delete and recreate the integration. If the error persists, contact AWS Support. +Monitoring | REDSHIFT-INTEGRATION-EVENT-0007 | ERROR | Unable to load data due to an internal error. Delete and recreate the integration. If the error persists, contact AWS Support. +Monitoring | REDSHIFT-INTEGRATION-EVENT-0008 | ERROR | Authorization failed because permissions have been revoked from the source DB cluster. Check the KMS key permission if you're using a customer-managed key (CMK) to encrypt the integration. Then, delete and recreate the integration. @@ -39,4 +39,3 @@ Monitoring | REDSHIFT-INTEGRATION-EVENT-0012 | ERROR | A restore from recovery p -Monitoring | REDSHIFT-INTEGRATION-EVENT-0013 | INFO | Zero-ETL integration <integration name> is now ACTIVE. -Monitoring | REDSHIFT-INTEGRATION-EVENT-0014 | ERROR | Integration <integration name> failed because it could not be modified due to an internal error. Delete and recreate the integration. If the error persists, contact AWS Support. -Operation | REDSHIFT-INTEGRATION-EVENT-0015 | INFO | A DDL change <DDL Change> has been applied to table <schema.name>. -Operation | REDSHIFT-INTEGRATION-EVENT-0016 | INFO | Your zero-ETL integration <integration name> is processing a modification request with the following arguments: <copy of request arguments>. +Monitoring | REDSHIFT-INTEGRATION-EVENT-0013 | INFO | Your zero-ETL Integration <integration name> is now ACTIVE. +Monitoring | REDSHIFT-INTEGRATION-EVENT-0014 | ERROR | Your integration <integration name> is in FAILED state because we are unable to modify it due to an internal error. Delete and recreate the integration. If the error persists, contact AWS Support. +Operation | REDSHIFT-INTEGRATION-EVENT-0016 | INFO | Your zero-ETL integration <integration name> is processing a modification request. @@ -44,2 +43,2 @@ Operation | REDSHIFT-INTEGRATION-EVENT-0017 | INFO | Your modification to zero-E -Operation | REDSHIFT-INTEGRATION-EVENT-0018 | WARNING | Target Amazon Redshift cluster is being paused. Wait for the cluster to be paused and then resume it to continue streaming data. -Operation | REDSHIFT-INTEGRATION-EVENT-0019 | WARNING | Target Amazon Redshift cluster is being paused. Resume the cluster to continue streaming data. +Operation | REDSHIFT-INTEGRATION-EVENT-0018 | WARNING | Target Amazon Redshift cluster is being paused. Wait for the cluster to be paused and then resume the cluster to continue streaming data. +Operation | REDSHIFT-INTEGRATION-EVENT-0019 | WARNING | Target Amazon Redshift cluster is paused. The cluster must be resumed in order to continue streaming data.