AWS sms-voice documentation change
Summary
Added documentation about Sender ID casing in the console, clarifying that console displays Sender IDs in uppercase but API calls require the original registered casing to avoid delivery failures.
Security assessment
This change addresses a functional issue where incorrect casing in API calls causes delivery failures, not a security vulnerability. It's a documentation clarification about proper API usage to ensure message delivery, with no evidence of security implications.
Diff
diff --git a/sms-voice/latest/userguide/sender-id.md b/sms-voice/latest/userguide/sender-id.md index 9d8ec9424..3348acd9e 100644 --- a//sms-voice/latest/userguide/sender-id.md +++ b//sms-voice/latest/userguide/sender-id.md @@ -84,0 +85,6 @@ When you are creating a Sender ID you should consider the following: +###### Sender ID casing in the console + +The AWS End User Messaging SMS console displays all Sender IDs in uppercase, regardless of the casing used during registration. Sender ID values are case-sensitive at the carrier and aggregator level. Using the wrong casing in API calls can cause delivery failures. + +To verify the registered casing of a Sender ID, check the associated registration record in the **Registrations** section of the console, which preserves the original casing submitted during registration. When specifying a Sender ID in API calls, use the casing shown in your registration record, not the casing shown in the Sender ID list. +