Setting the file. One moment.
Skill 82 · AWS Social Messaging
Subchapter 82.2
references/managing-media.mdMarkdown3 KBView on GitHub
Security: S3 buckets used for media storage should have default encryption enabled (SSE-S3 or SSE-KMS) and enforce
aws:SecureTransportin the bucket policy. Media files may contain sensitive content (receipts, invoices, PII). See .
aws socialmessaging post-whatsapp-message-media \
--origination-phone-number-id "phone-number-id-XXXXXXXXXXXXXXXXXXXX" \
--source-s3-file '{"bucketName":"my-media-bucket","key":"images/receipt.png"}'aws socialmessaging post-whatsapp-message-media \
--origination-phone-number-id "phone-number-id-XXXXXXXXXXXXXXXXXXXX" \
--source-s3-presigned-url '{"url":"https://my-bucket.s3.amazonaws.com/image.png","headers":{}}'Security: When generating presigned URLs, set a short expiration (15–30 minutes) to limit the window of access. See SKILL.md — Security Considerations.
Returns a reusable media ID for sending messages without re-uploading.
aws socialmessaging create-whatsapp-message-template-media \
--id "waba-XXXXXXXXXXXXXXXXXXXX" \
--source-s3-file '{"bucketName":"my-media-bucket","key":"templates/promo-header.jpg"}'Use the returned media handle in template HEADER component’s header_handle field.
aws socialmessaging get-whatsapp-message-media \
--media-id "XXXXXXXXXXXXXXXXXXXX" \
--origination-phone-number-id "phone-number-id-XXXXXXXXXXXXXXXXXXXX"Returns media metadata and a download URL.
Sensitive data: The returned download URL may be logged in CloudTrail and provides temporary access to media content — treat it as sensitive. Similarly,
post-whatsapp-message-mediainput parameters (S3 bucket/key, presigned URLs) appear in CloudTrail logs.
aws socialmessaging delete-whatsapp-message-media \
--media-id "XXXXXXXXXXXXXXXXXXXX" \
--origination-phone-number-id "phone-number-id-XXXXXXXXXXXXXXXXXXXX"Limits per WhatsApp Cloud API media reference (opens in a new tab) — check Meta’s documentation for supported formats and size constraints.
Once uploaded, reference media by ID instead of URL:
{"type":"image","image":{"id":"XXXXXXXXXXXXXXXXXXXX","caption":"Your receipt"}}This avoids requiring publicly accessible URLs for each send.