aws-ses
Send transactional and marketing emails with Amazon SES. Verify domains and identities, create reusable email templates, configure receipt rules for incoming mail, and handle bounces and complaints with SNS notifications.
What this skill does
# AWS SES Amazon Simple Email Service (SES) is a cost-effective email platform for sending transactional, marketing, and notification emails. It also receives incoming email and integrates with S3, SNS, and Lambda for processing. ## Core Concepts - **Verified Identity** — domain or email address authorized to send - **Configuration Set** — tracking settings for opens, clicks, bounces - **Template** — reusable email template with variable substitution - **Receipt Rule** — rules for processing incoming emails - **Suppression List** — addresses that bounced or complained - **Sending Quota** — rate limits based on account reputation ## Domain Verification ```bash # Verify a domain (creates DKIM records) aws sesv2 create-email-identity --email-identity example.com ``` ```bash # Get DKIM tokens to add as DNS CNAME records aws sesv2 get-email-identity --email-identity example.com \ --query 'DkimAttributes.Tokens' ``` ```bash # Verify a single email address (for testing) aws sesv2 create-email-identity --email-identity [email protected] ``` ```bash # List verified identities aws sesv2 list-email-identities --query 'EmailIdentities[].IdentityName' ``` ## Sending Email ```bash # Send a simple email aws sesv2 send-email \ --from-email-address "[email protected]" \ --destination '{"ToAddresses":["[email protected]"]}' \ --content '{ "Simple": { "Subject": {"Data": "Order Confirmation #12345"}, "Body": { "Html": {"Data": "<h1>Thank you!</h1><p>Your order has been confirmed.</p>"}, "Text": {"Data": "Thank you! Your order has been confirmed."} } } }' \ --configuration-set-name prod-tracking ``` ```python # Send email with boto3 import boto3 ses = boto3.client('sesv2') ses.send_email( FromEmailAddress='[email protected]', Destination={ 'ToAddresses': ['[email protected]'], 'BccAddresses': ['[email protected]'] }, Content={ 'Simple': { 'Subject': {'Data': 'Your Invoice'}, 'Body': { 'Html': {'Data': '<h1>Invoice #INV-001</h1><p>Amount: $99.99</p>'}, 'Text': {'Data': 'Invoice #INV-001\nAmount: $99.99'} } } }, ConfigurationSetName='prod-tracking' ) ``` ## Email Templates ```bash # Create a template aws sesv2 create-email-template \ --template-name order-confirmation \ --template-content '{ "Subject": "Order Confirmation #{{orderNumber}}", "Html": "<h1>Hi {{customerName}},</h1><p>Your order #{{orderNumber}} for {{itemName}} has been confirmed.</p><p>Total: ${{total}}</p>", "Text": "Hi {{customerName}},\nYour order #{{orderNumber}} for {{itemName}} has been confirmed.\nTotal: ${{total}}" }' ``` ```bash # Send using a template aws sesv2 send-email \ --from-email-address "[email protected]" \ --destination '{"ToAddresses":["[email protected]"]}' \ --content '{ "Template": { "TemplateName": "order-confirmation", "TemplateData": "{\"orderNumber\":\"12345\",\"customerName\":\"Alice\",\"itemName\":\"Widget Pro\",\"total\":\"99.99\"}" } }' ``` ```python # Bulk templated sending with boto3 import boto3 ses = boto3.client('sesv2') ses.send_bulk_email( FromEmailAddress='[email protected]', DefaultContent={ 'Template': { 'TemplateName': 'weekly-newsletter', 'TemplateData': '{"week":"Jan 15"}' } }, BulkEmailEntries=[ { 'Destination': {'ToAddresses': ['[email protected]']}, 'ReplacementEmailContent': { 'ReplacementTemplate': { 'ReplacementTemplateData': '{"name":"Alice","recommendations":"Widget A, Widget B"}' } } }, { 'Destination': {'ToAddresses': ['[email protected]']}, 'ReplacementEmailContent': { 'ReplacementTemplate': { 'ReplacementTemplateData': '{"name":"Bob","recommendations":"Gadget X, Gadget Y"}' } } } ], ConfigurationSetName='marketing-tracking' ) ``` ## Bounce and Complaint Handling ```bash # Create a configuration set with event destinations aws sesv2 create-configuration-set --configuration-set-name prod-tracking # Add SNS destination for bounces and complaints aws sesv2 create-configuration-set-event-destination \ --configuration-set-name prod-tracking \ --event-destination-name bounce-handler \ --event-destination '{ "Enabled": true, "MatchingEventTypes": ["BOUNCE", "COMPLAINT"], "SnsDestination": { "TopicArn": "arn:aws:sns:us-east-1:123456789:ses-bounces" } }' ``` ```python # Lambda handler for bounce/complaint SNS notifications import json def handler(event, context): for record in event['Records']: message = json.loads(record['Sns']['Message']) notification_type = message['notificationType'] if notification_type == 'Bounce': bounce = message['bounce'] for recipient in bounce['bouncedRecipients']: email = recipient['emailAddress'] bounce_type = bounce['bounceType'] # Permanent or Transient if bounce_type == 'Permanent': suppress_email(email) elif notification_type == 'Complaint': complaint = message['complaint'] for recipient in complaint['complainedRecipients']: unsubscribe_email(recipient['emailAddress']) ``` ## Receiving Email ```bash # Create a receipt rule set aws ses create-receipt-rule-set --rule-set-name inbound-rules aws ses set-active-receipt-rule-set --rule-set-name inbound-rules ``` ```bash # Create rule to store incoming email in S3 and trigger Lambda aws ses create-receipt-rule \ --rule-set-name inbound-rules \ --rule '{ "Name": "process-support-emails", "Enabled": true, "Recipients": ["[email protected]"], "Actions": [ {"S3Action": {"BucketName": "incoming-email", "ObjectKeyPrefix": "support/"}}, {"LambdaAction": {"FunctionArn": "arn:aws:lambda:us-east-1:123456789:function:process-support-email"}} ] }' ``` ## Monitoring ```bash # Check sending quota and statistics aws sesv2 get-account --query '{SendQuota:SendQuota,SendingEnabled:SendingEnabled}' ``` ```bash # Get sending statistics aws ses get-send-statistics --query 'SendDataPoints[-5:]' ``` ## Best Practices - Always verify domains with DKIM for better deliverability - Set up bounce and complaint handling before sending at scale - Use configuration sets to track delivery metrics - Send from a subdomain (mail.example.com) to protect main domain reputation - Include unsubscribe headers in marketing emails (required by law) - Warm up new accounts gradually — start with small volumes - Use the suppression list API to respect bounces and complaints - Test with the SES mailbox simulator before going to production
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.