AWS quick documentation change
Summary
Added guidance on ACL verification and best practices for sharing admin-managed knowledge bases to prevent management issues.
Security assessment
Provides documentation on verifying access controls and sharing practices to avoid orphaned resources, which is security-related but does not address a specific security vulnerability or incident.
Diff
diff --git a/quick/latest/userguide/acl-best-practices-kb.md b/quick/latest/userguide/acl-best-practices-kb.md index b875bc48e..d41c6d8d8 100644 --- a//quick/latest/userguide/acl-best-practices-kb.md +++ b//quick/latest/userguide/acl-best-practices-kb.md @@ -14,0 +15,2 @@ For more information about configuring ACLs for a specific data source, see [Ama +To verify document-level access controls and troubleshoot permission issues, see [Check document access (ACL verification)](./sync-reports-observability.html#sync-reports-acl-verification). + @@ -37,0 +40,4 @@ This prevents potential security issues if the email is later reassigned to some +**Share admin-managed knowledge bases with co-owners** + +Admin-managed knowledge bases (service credentials) are often used across teams and organizations. If the original creator leaves the company and no co-owners exist, the knowledge base becomes unmanageable — no one can edit settings, trigger syncs, or update permissions. To avoid this, share admin-managed knowledge bases with at least one additional owner. For more information, see [Sharing knowledge bases and data sources](./sharing-kb-datasources.html). + @@ -82 +88 @@ Knowledge bases -Troubleshooting knowledge bases +Sharing knowledge bases and data sources