AWS sms-voice medium security documentation change
Summary
Consolidated sandbox documentation by removing voice-specific sections and updating production access request process. Added detailed requirements for support case submission including message types, opt-in processes, and template validation.
Security assessment
The changes enforce stricter production access controls by requiring detailed use case descriptions, message type specifications, and opt-in process documentation. This helps prevent SMS/MMS abuse and aligns with anti-spam regulations. The removal of separate voice sandbox procedures suggests security standardization across channels. Specific security evidence includes added validation of message templates and explicit requirements for customer consent mechanisms.
Diff
diff --git a/sms-voice/latest/userguide/sandbox.md b/sms-voice/latest/userguide/sandbox.md index f3770c152..528468dcc 100644 --- a//sms-voice/latest/userguide/sandbox.md +++ b//sms-voice/latest/userguide/sandbox.md @@ -5 +5 @@ -SMS/MMS sandboxMoving from the SMS/MMS sandboxVoice sandboxMoving from the voice sandbox to production +SMS/MMS sandboxMoving from the SMS/MMS sandboxVoice sandbox @@ -19,2 +18,0 @@ New AWS End User Messaging SMS accounts are placed into an SMS/MMS or voice sand - * Moving from the voice sandbox to production - @@ -49 +47 @@ Message and data rates apply for messages that you receive. We send one message -You can remove these restrictions by requesting production access. For more information, see Moving from the AWS End User Messaging SMS SMS/MMS sandbox to production. +You can remove these restrictions by requesting production access. For more information, see Moving from the AWS End User Messaging SMS MMS and Voice sandbox to production. @@ -53 +51 @@ You can remove these restrictions by requesting production access. For more info -If your account is observed to be sending suspicious SMS/MMS traffic, your account's ability to send messages may be paused. If this occurs, please follow the steps in Moving from the AWS End User Messaging SMS SMS/MMS sandbox to production to gain production access. +If your account is observed to be sending suspicious SMS/MMS traffic, your account's ability to send messages may be paused. If this occurs, please follow the steps in Moving from the AWS End User Messaging SMS MMS and Voice sandbox to production to gain production access. @@ -55 +53 @@ If your account is observed to be sending suspicious SMS/MMS traffic, your accou -## Moving from the AWS End User Messaging SMS SMS/MMS sandbox to production +## Moving from the AWS End User Messaging SMS MMS and Voice sandbox to production @@ -69,13 +67 @@ Complete all fields in the support case, even if they are labeled as optional. - 2. On the **Service Quota increase** page, complete the following: - - * For **Service** , choose **AWS End User Messaging SMS (Pinpoint)**. - - * For **Provide a link to the site or app which will be sending SMS messages** , provide information about the website, application, or service that will send SMS/MMS messages. - - * For **What type of messages do you plan to send** , choose the type of message that you plan to send by using your long code: - - * **One Time Password** – Messages that provide passwords that your customers use to authenticate with your website or application. - - * **Promotional** – Noncritical messages that promote your business or service, such as special offers or announcements. - - * **Transactional** – Important informational messages that support customer transactions, such as order confirmations or account alerts. Transactional messages must not contain promotional or marketing content. + 2. On the **Create Case** page, complete the following: @@ -83 +69 @@ Complete all fields in the support case, even if they are labeled as optional. - * For **Which AWS Region will you be sending messages from** , choose the AWS Region that you will be sending messages from. + * Select **Account and Billing**. @@ -85 +71 @@ Complete all fields in the support case, even if they are labeled as optional. - * For **Which countries do you plan to send messages to** , enter the country or region that you want to purchase short codes in. + * For **Service** , choose **Service Quotas**. @@ -87 +73 @@ Complete all fields in the support case, even if they are labeled as optional. - * In the **How do your customers opt to receive messages from you** , provide details about your opt-in process. + * For **Category** choose either **AWS End User Messaging SMS (Pinpoint)** or **AWS End User Messaging Voice (Pinpoint)** , depending on your request. @@ -89 +75 @@ Complete all fields in the support case, even if they are labeled as optional. - * In the **Please provide the message template that you plan to use to send messages to your customers** field, include the template that you will be using. + * For **Severity** , choose **General Limits**. @@ -105 +91,17 @@ The AWS Regions is required in the **Requests** section. Even if you provided th - 4. Under **Case description** , for **Use case description** , enter any relevant details about this request. + 4. Under **Description** , for **Use case description** , enter any relevant details about this request. Include answers to the following: + + * For **Provide a link to the site or app which will be sending SMS messages** , provide information about the website, application, or service that will send SMS/MMS messages. + + * For **What type of messages do you plan to send** , choose the type of message that you plan to send by using your long code: + + * **One Time Password** – Messages that provide passwords that your customers use to authenticate with your website or application. + + * **Promotional** – Noncritical messages that promote your business or service, such as special offers or announcements. + + * **Transactional** – Important informational messages that support customer transactions, such as order confirmations or account alerts. Transactional messages must not contain promotional or marketing content. + + * For **Which countries do you plan to send messages to** , enter the country or region that you want to purchase short codes in. + + * In the **How do your customers opt to receive messages from you** , provide details about your opt-in process. + + * In the **Please provide the message template that you plan to use to send messages to your customers** field, include the template that you will be using. @@ -109 +111 @@ The AWS Regions is required in the **Requests** section. Even if you provided th - 6. Under **Contact options** , for **Preferred contact language** , choose whether you want to receive communications for this case in **English** or **Japanese**. + 6. Choose **Next Step: Solve now or Contact us**. For **Preferred contact language** , choose whether you want to receive communications for this case in **English** or **Japanese**. @@ -143,59 +144,0 @@ Before you request production access, you must send at least one voice message f -## Moving from the voice sandbox to production - -When you first start using the voice channel, your account is in the _sandbox_. - -To remove these quotas from your account, you can request to have your account removed from the sandbox. When your account is removed from the sandbox, it has _production access_. - -###### Note - -Before you request production access, you must send at least one voice message from your AWS End User Messaging SMS account. - -While in the sandbox, you are required to verify the destination numbers you're sending messages to. For more information on how to add a verified destination phone number, see [Add a verified destination phone number](./verify-destination-phone-number.html). - -###### To request production access - - 1. Create an AWS Support case at [https://support.console.aws.amazon.com/support/home#/case/create?issueType=service-limit-increase](https://console.aws.amazon.com/support/home#/case/create?issueType=service-limit-increase). - - 2. For **Service** , choose **AWS End User Messaging Voice (Pinpoint)**. - - 3. (Optional) Answer the following information: - - * **What's the maximum number of voice messages that you plan to send per day?** - - * **What will be the average length of each call that you send?** - - * **How do you obtain the phone numbers that you plan to send voice messages to?** - - * **How many dedicated phone numbers will you use to send your messages? Why did you choose this number?** - - * **How many calls do you expect to make from each phone number? (1 to X) messages per (day/week/month/other)** - - * **How do you obtain consent to send voice messages to your customers?** - - * **How can customers opt out of receiving messages from you? How will you process these requests?** - - 4. Under **Requests** , for **Region** , choose the AWS Region that you use to send voice messages. - - 5. For **Quota** , verify that **Production Access** is selected. - - 6. For **New quota value** , enter 1. - - 7. Under **Case description** , for **Use case description** , provide the following details: - - * The website or app of the company or service that will send voice messages. - - * The service that's provided by your website or app, and how your voice messages contribute to that service. - - 8. Under **Contact options** , for **Preferred contact language** , choose whether you want to receive communications for this case in **English** or **Japanese**. - - 9. When you finish, choose **Submit**. - - - - -The AWS Support team provides an initial response to your request within 24 hours. - -To prevent our systems from being used to send unsolicited or malicious content, AWS Support must consider each request carefully. If we’re able to do so, we'll grant your request within this 24-hour period. However, if we need to obtain additional information from you, it might take longer to resolve your request. - -We might not be able to grant your request if your use case doesn’t align with AWS Support policies. -