AWS Social Messaging
AWSOfficialPublished by AWS
- Skill
- Tool integration
- Cloud and DevOps
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides an interface for interacting with AWS End User Messaging Social to manage WhatsApp Business Account (WABA) operations. It supports the full lifecycle of WhatsApp messaging, including template management, media handling, event destination configuration for delivery tracking, and diagnostic tools for troubleshooting messaging issues via the AWS CLI.
What it does
- Create, update, and delete WhatsApp message templates
- Send utility, marketing, authentication, and freeform messages
- Upload and manage media assets for messages and template headers
- Configure event destinations for real-time delivery and status tracking
- Diagnose messaging issues by checking account and phone number status
When to use it
- When you need to integrate WhatsApp messaging capabilities into your AWS-based workflows
- When managing approved message templates for customer communication
- When setting up automated delivery status notifications via SNS
- When troubleshooting failed message deliveries or template reclassifications
Advantages
- Centralized management of WhatsApp messaging through standard AWS CLI commands
- Supports secure media handling by referencing uploaded media IDs
- Enables real-time monitoring of message delivery and template status changes
- Provides structured diagnostic paths for identifying account or delivery issues
Usage examples
- “List all available WhatsApp message templates for my WABA.”
- The agent will retrieve and display the list of templates, including their current status and category.
- “Upload an image to be used in a WhatsApp template header.”
- The agent will use the provided S3 file location to upload the media and return a media handle for use in template definitions.
- “Configure an SNS topic for tracking WhatsApp message delivery status.”
- The agent will guide you through setting up the event destination for your WABA, ensuring the necessary IAM roles and SNS policies are in place.
- “Troubleshoot why my WhatsApp messages are not being delivered.”
- The agent will check the status of your linked WABA and phone number, and verify if event destinations are configured to provide error logs.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/aws/aws-social-messaging/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip aws-social-messaging.zip -d .agents/skills
Documentation by AWS
AWS End User Messaging Social — WhatsApp
Overview
WhatsApp messaging via AWS End User Messaging Social: template management, sending, media handling, event destinations, and delivery troubleshooting.
Recommended setup: Use the AWS MCP server for sandboxed execution, audit logging, and enterprise controls.
Without AWS MCP: This skill works with any agent that has AWS CLI access. All commands use standard AWS CLI syntax.
Common Tasks
1. Verify Dependencies
Constraints:
The AWS MCP server is recommended for seamless API execution but not required — all commands use standard AWS CLI syntax
You MUST verify the AWS CLI is installed and configured with appropriate credentials
You SHOULD recommend the user assume an IAM role with ephemeral credentials
You MUST inform the user if any required tool is missing and how to install/configure it
You MUST ask the user if they want to proceed despite any missing tools
If the
aws socialmessagingsubcommand is not recognized, the user must update to the latest AWS CLI versionRequired IAM permissions (scope to specific WABA and phone number ARNs):
Templates:
social-messaging:CreateWhatsAppMessageTemplate,social-messaging:GetWhatsAppMessageTemplate,social-messaging:ListWhatsAppMessageTemplates,social-messaging:UpdateWhatsAppMessageTemplate,social-messaging:DeleteWhatsAppMessageTemplate,social-messaging:ListWhatsAppTemplateLibrary,social-messaging:CreateWhatsAppMessageTemplateFromLibrarySending:
social-messaging:SendWhatsAppMessageMedia:
social-messaging:PostWhatsAppMessageMedia,social-messaging:CreateWhatsAppMessageTemplateMedia,social-messaging:GetWhatsAppMessageMedia,social-messaging:DeleteWhatsAppMessageMediaEvents:
social-messaging:PutWhatsAppBusinessAccountEventDestinationsDiagnostics:
social-messaging:GetLinkedWhatsAppBusinessAccount,social-messaging:GetLinkedWhatsAppBusinessAccountPhoneNumber,social-messaging:ListLinkedWhatsAppBusinessAccountsSupporting:
sns:ListSubscriptionsByTopic,iam:PassRole(for event destination role)
2. Manage Templates
Create, update, and delete message templates (utility, marketing, authentication).
create-whatsapp-message-template: base64-encode--template-definition(blob type)create-whatsapp-message-template-from-library: use pre-approved Meta library templateslist-whatsapp-template-library: browse available library templatesget-whatsapp-message-template: retrieve template details by--id(WABA) and--meta-template-idupdate-whatsapp-message-template: modify existing template contentdelete-whatsapp-message-template: requires--template-name(NOT--meta-template-name); always include--delete-all-languageslist-whatsapp-message-templates: response fields aretemplateStatusandtemplateCategory(NOTstatus/category)Templates with
{{N}}parameters MUST include"parameter_format": "positional"(exception: AUTHENTICATION — Meta handles OTP parameters automatically) and"example"Meta reviews all templates (minutes to 24h); MUST NOT send with PENDING/REJECTED
Choosing the wrong category causes reclassification (UTILITY → MARKETING) which changes pricing — see managing-templates.md — Choosing the Right Category for guidance on selecting UTILITY vs MARKETING vs AUTHENTICATION
You MUST confirm the intended category (UTILITY, MARKETING, or AUTHENTICATION) with the user before creating a template — explain the categorization criteria and reclassification risk if the choice is ambiguous
3. Send Messages
Template Messages (no 24h restriction)
Use for: transactional updates (utility), promotions (marketing), verification codes (authentication)
Collect: phone number ID, recipient (E.164 with
+), template name, language, parametersMarketing templates may include image headers
--messageis blob type — MUST base64-encode JSON
Freeform Messages (24h window required)
Use for: customer service replies within 24h of customer's last inbound message
Supports: text, image, document, video, audio — see WhatsApp Cloud API media reference for supported format and size constraints
No API to check window status — user must confirm from logs or event history
Media URLs MUST be publicly accessible HTTPS and remain available for the full 30-day message availability window (Meta can re-fetch anytime). For sensitive content (receipts, invoices, PII), upload via
post-whatsapp-message-mediaand reference by media ID instead — presigned URLs cannot satisfy the 30-day availability requirement
Constraints for all sends:
Before executing any API call, validate parameter formats:
Phone number IDs match
phone-number-id-*patternWABA IDs match
waba-*patternRecipient numbers are E.164 with
+prefix (e.g.,+14155551234), or Business-Scoped User ID (BSUID) via the"recipient"fieldTemplate names contain only lowercase letters, numbers, and underscores
Language codes use Meta's locale format with underscores (e.g.,
en_US,pt_BR)--meta-api-versionisv{Major}.{Minor}format (e.g.,v21.0)
"messaging_product"MUST be"whatsapp"in the JSON body; check Meta's Graph API changelog for the supported Meta Graph API version--messageis blob type — MUST base64-encode the JSON payloadA successful
messageIdmeans queued, not deliveredYou MUST ask for all required parameters upfront in a single prompt
You MUST accept parameters as individual values, JSON objects, or file references
You MUST explain each step before executing
You SHOULD confirm all parameters with the user before executing
You MUST respect the user's decision to abort
You MUST NOT send more than 5 messages per batch without user confirmation
You MUST NOT create or access credentials directly
See sending-messages.md.
4. Manage Media
Upload, retrieve, and delete media for messages and template headers.
post-whatsapp-message-media: upload media, returns reusable media IDcreate-whatsapp-message-template-media: upload media specifically for template headersget-whatsapp-message-media: retrieve media metadata/URL by IDdelete-whatsapp-message-media: remove uploaded media
See managing-media.md.
5. Configure Event Destinations
Set up delivery tracking, template status notifications, and reclassification alerts.
Set up delivery tracking, template status notifications, and reclassification alerts. A WABA can only have one event destination. See configuring-event-destinations.md for prerequisites (IAM role, SNS topic with KMS encryption, HTTPS-only subscription endpoints, condition keys) and full security controls.
6. Troubleshoot Delivery
Diagnostic flow: WABA status → phone number → templates → event destinations → quotas.
get-linked-whatsapp-business-account: registration MUST be COMPLETEget-linked-whatsapp-business-account-phone-number: verify phone number healthlist-linked-whatsapp-business-accounts: list all WABAsTemplate reclassified: detectable via event destinations (real-time) or by listing templates and comparing categories; delete and recreate
24h window expired: use template message instead
Rate limiting: new WABAs have lower limits; increases with quality
Recipient without WhatsApp: silently dropped
See troubleshooting-delivery.md.
Quick Reference — Common Errors
Access denied: verify IAM permissions scoped to WABA/phone number ARNs
Template rejected: body must match category; include
parameter_formatandexampleTemplate reclassified: configure event destinations to detect; delete and recreate
24h window expired: use template message instead of freeform
Send fails:
--origination-phone-number-idis the ID (not phone number); recipient E.164 with+Queued but not delivered: 200 = queued; configure event destinations for status
Media URL inaccessible: must be publicly accessible HTTPS
Security Considerations
Use least-privilege IAM policies scoped to specific
social-messaging:actions and WABA/phone number ARNsUse ephemeral credentials (IAM roles) instead of long-lived access keys
Store secrets in AWS Secrets Manager or Parameter Store — never in code or environment variables
Enable CloudTrail for auditing all
social-messagingAPI calls; encrypt logs with KMS CMKEncrypt SNS topics for event destinations with KMS (callbacks contain recipient metadata)
Encrypt CloudWatch Logs with KMS if monitoring social-messaging activity
Avoid sensitive data in template parameters and freeform message content (they appear in CloudTrail logs)
Validate recipient phone numbers to prevent unauthorized messaging
Verify SNS subscription endpoints are authorized by your team — validate that all subscribed email addresses and systems belong to personnel/systems that should receive sensitive delivery status and recipient metadata before confirming subscriptions. Use HTTPS-only endpoints
Add condition keys (
aws:SourceArn,aws:SourceAccount) to SNS topic policies to prevent confused deputy attacksImplement rate limiting via service quotas and CloudWatch alarms on send rates
Additional Resources
Files
- ATTRIBUTION.mdAdded by AutoGineer943 B
- LICENSELicence file added by AutoGineer9.9 KiB
- NOTICELicence file added by AutoGineer67 B
- SKILL.md11.1 KiB
- references/configuring-event-destinations.md3.9 KiB
- references/managing-media.md2.6 KiB
- references/managing-templates.md7.5 KiB
- references/sending-messages.md6.6 KiB
- references/troubleshooting-delivery.md4.3 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs an MCP server
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- AWS
- Publisher
- AWS (Official)
- Source
- aws/agent-toolkit-for-aws · skills/specialized-skills/customer-communications-skills/aws-social-messaging · commit 0a218f8
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- NOTICE (added by AutoGineer from NOTICE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by AWS or AWS.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download aws-social-messaging.zip