AWS aurora-dsql documentation change
Summary
Added clarification about witness Region impairment having no availability impact but potential latency increase during recovery
Security assessment
The change explains operational behavior during witness Region impairment but does not address security vulnerabilities or introduce security controls
Diff
diff --git a/aurora-dsql/latest/userguide/disaster-recovery-resiliency.md b/aurora-dsql/latest/userguide/disaster-recovery-resiliency.md index bf71b5000..cf97b11fd 100644 --- a//aurora-dsql/latest/userguide/disaster-recovery-resiliency.md +++ b//aurora-dsql/latest/userguide/disaster-recovery-resiliency.md @@ -23 +23 @@ By design, Aurora DSQL commits all write transactions to a distributed transacti -A designated witness Region supports transaction log-only writes and doesn't consume storage. Witness Regions don't have an endpoint. This means that witness Regions store only encrypted transaction logs, require no administration or configuration, and aren't accessible by users. +A designated witness Region supports transaction log-only writes and doesn't consume storage. Witness Regions don't have an endpoint. This means that witness Regions store only encrypted transaction logs, require no administration or configuration, and aren't accessible by users. If the witness Region becomes impaired, there is no impact to cluster availability. Write transactions might experience a small increase in latency until the witness Region recovers.