AWS connect documentation change
Summary
Updated documentation for outbound campaigns setup process, including clarified pre-authorization requirements for mass notifications, UI navigation changes, and encryption configuration steps
Security assessment
Changes focus on procedural clarifications and UI updates rather than addressing vulnerabilities. While encryption settings are mentioned, this is standard configuration documentation rather than new security content
Diff
diff --git a/connect/latest/adminguide/enable-outbound-campaigns.md b/connect/latest/adminguide/enable-outbound-campaigns.md index 7696eabd8..53010cb1b 100644 --- a//connect/latest/adminguide/enable-outbound-campaigns.md +++ b//connect/latest/adminguide/enable-outbound-campaigns.md @@ -5 +5 @@ -Before you beginCreate an AWS KMS keyConfigure outbound campaignsBest practices for ring duration and caller ID +Important things to knowBefore you beginCreate an AWS KMS keyConfigure outbound campaignsBest practices for ring duration and caller ID @@ -11 +11 @@ This topic explains how to set up Amazon Connect outbound campaigns, a feature o -###### Important +## Important things to know @@ -15 +15,5 @@ This topic explains how to set up Amazon Connect outbound campaigns, a feature o - * To use Amazon Connect outbound campaigns for event-driven mass notifications, such as severe weather warnings, evacuation notices, disaster response communications, or utility disruptions impacting many thousands of customers, requires pre-authorization. While we may support these use-cases, they require additional technical validation due to their unique nature and implications, such as the impact on carrier networks for voice or SMS communications. If you need to implement such mass notification scenarios, you can submit a detailed description of your requirements through the quota increase request process in the [Amazon Connect service quotas section](https://docs.aws.amazon.com/general/latest/gr/connect_region.html#limits_amazon_connect) of the AWS General Reference guide. Additional charges may apply based on your location and anticipated notification volumes. This review process helps ensure the reliable delivery of these critical messages while maintaining service quality for all customers. + * You must obtain pre-authorization by creating an AWS Support ticket to use Amazon Connect outbound campaigns for event-driven mass notifications, such as severe weather warnings, evacuation notices, disaster response communications, or utility disruptions that impact several thousand of customers. + +This review process helps ensure the reliable delivery of these critical messages while maintaining service quality for all customers. While we may support these use-cases, they require additional technical validation due to their unique nature and implications, such as the impact on carrier networks for voice or SMS communications. + +Follow the instructions in [Requesting a quota increase](https://docs.aws.amazon.com/servicequotas/latest/userguide/request-quota-increase.html) in the _Service Quotas User Guide_ to open a ticket that contains a detailed description of your requirements. Additional charges may apply based on your location and anticipated notification volumes. @@ -53 +57 @@ To switch the KMS key that is associated with outbound campaigns, first you need - 3. In the navigation pane, choose **Channels and communications**. + 3. In the navigation pane, choose **Channels and communications** , **Outbound campaigns**. @@ -55 +59 @@ To switch the KMS key that is associated with outbound campaigns, first you need - 4. To enable outbound campaigns, choose **Enable outbound campaigns**. If you don't see this option, then check whether [ outbound campaigns is available in your AWS Region](./regions.html#campaigns_region). + 4. On the **Outbound campaigns** page, choose **Enable**. If you don't see this option, then check whether [outbound campaigns is available in your AWS Region](./regions.html#campaigns_region). @@ -57 +61 @@ To switch the KMS key that is associated with outbound campaigns, first you need - 5. Under **Encryption settings** , enter your own AWS KMS key or choose **Create an AWS KMS key**. + 5. Under **Encryption** , enter your own AWS KMS key or choose **Create an AWS KMS key**. @@ -77 +81 @@ In the following example, the name of the key starts with **bcb6fdd** : - * Return to the tab in your browser for the Amazon Connect console, **Telephony** page. Click or tap in the **AWS KMS key** for the key you created to appear in a dropdown list. Choose the key you created. + * Return to the tab in your browser for the Amazon Connect console, **Enable outbound campaigns** page. Click or tap in the **AWS KMS key** for the key you created to appear in a dropdown list. Choose the key you created. @@ -81 +85 @@ Show moreShow less - 6. Choose **Save**. + 6. Choose **Enable outbound campaigns**.