AWS connect documentation change
Summary
Updated references from 'Amazon Q in Connect' to 'Connect AI agents' in encryption context documentation.
Security assessment
This is terminology standardization without changes to encryption mechanisms (BYOK/service-owned keys remain unchanged). No security implications introduced or addressed in the documentation updates.
Diff
diff --git a/connect/latest/adminguide/key-management.md b/connect/latest/adminguide/key-management.md index 57a2274e2..d7e12940e 100644 --- a//connect/latest/adminguide/key-management.md +++ b//connect/latest/adminguide/key-management.md @@ -5 +5 @@ -Amazon Q in ConnectAmazon AppIntegrationsCustomer ProfilesVoice IDOutbound campaigns +Connect AI agentsAmazon AppIntegrationsCustomer ProfilesVoice IDOutbound campaigns @@ -24 +24 @@ For information about AWS KMS keys see [What is AWS Key Management Service?](htt -## Amazon Q in Connect +## Connect AI agents @@ -26 +26 @@ For information about AWS KMS keys see [What is AWS Key Management Service?](htt -Amazon Q in Connect stores knowledge documents that are encrypted at rest in S3 using a BYOK or a service-owned key. The knowledge documents are encrypted at rest in Amazon OpenSearch Service using a service-owned key. Amazon Q in Connect stores agent queries and call transcripts using a BYOK or a service-owned key. +Connect AI agents stores knowledge documents that are encrypted at rest in S3 using a BYOK or a service-owned key. The knowledge documents are encrypted at rest in Amazon OpenSearch Service using a service-owned key. Connect AI agents stores agent queries and call transcripts using a BYOK or a service-owned key. @@ -28 +28 @@ Amazon Q in Connect stores knowledge documents that are encrypted at rest in S3 -The knowledge documents used by Amazon Q in Connect are encrypted by an AWS KMS key. +The knowledge documents used by Connect AI agents are encrypted by an AWS KMS key.