AWS connect documentation change
Summary
Updated interface screenshots and captions to show KMS encryption configuration, error handling, and setup process for outbound campaigns
Security assessment
Added documentation about KMS encryption configuration options for outbound campaigns data, which is a security feature. No evidence of addressing a specific vulnerability.
Diff
diff --git a/connect/latest/adminguide/enable-outbound-campaigns-customer-profiles.md b/connect/latest/adminguide/enable-outbound-campaigns-customer-profiles.md index 1055cf6d9..92b5d30b3 100644 --- a//connect/latest/adminguide/enable-outbound-campaigns-customer-profiles.md +++ b//connect/latest/adminguide/enable-outbound-campaigns-customer-profiles.md @@ -38 +38 @@ Existing customers enable outbound campaignsHow to delete Outbound campaigns con - + @@ -45 +45 @@ Existing customers enable outbound campaignsHow to delete Outbound campaigns con - + @@ -58 +58 @@ The KMS configuration will only be used for the outbound campaigns configuration - + @@ -65 +65 @@ The KMS configuration will only be used for the outbound campaigns configuration - + @@ -95 +95 @@ The KMS configuration will only be used for the outbound campaigns configuration - + @@ -102 +102 @@ The KMS configuration will only be used for the outbound campaigns configuration - + @@ -123 +123 @@ When creating instance if you see a warning banner, you are either missing some - + @@ -127,2 +127,2 @@ When creating instance if you see a warning banner, you are either missing some -Already associated with another customer profiles domain, cannot be associated with multiple domains. | An Outbound campaign can only be associated to one customer profile or one knowledge base at a time. | You can either use the associated Customer Profiles domain, go back to the Customer Profiles domain page, and re-associate the domain, or you can find out which domain is associated by using the `connect-campaign:ListConnectInstanceIntegrations` API to find the Customer Profiles domain Arn. If needed, you can delete the integration between Outbound campaigns and Customer Profiles and re-associate it by deleting the integration by using the `connect-campaigns:DeleteConnectInstanceIntegration` API. |  -Outbound campaigns has been created. However, some features may not work as expected. Please check your settings and try again. | A resource failed to configure correctly. However, some resources succeeded. The error message will help indicate to the customer what went wrong. | Follow the instructions on the warn/error banner. |  +Already associated with another customer profiles domain, cannot be associated with multiple domains. | An Outbound campaign can only be associated to one customer profile or one knowledge base at a time. | You can either use the associated Customer Profiles domain, go back to the Customer Profiles domain page, and re-associate the domain, or you can find out which domain is associated by using the `connect-campaign:ListConnectInstanceIntegrations` API to find the Customer Profiles domain Arn. If needed, you can delete the integration between Outbound campaigns and Customer Profiles and re-associate it by deleting the integration by using the `connect-campaigns:DeleteConnectInstanceIntegration` API. |  +Outbound campaigns has been created. However, some features may not work as expected. Please check your settings and try again. | A resource failed to configure correctly. However, some resources succeeded. The error message will help indicate to the customer what went wrong. | Follow the instructions on the warn/error banner. | 