aws-ses-inbound_skill

Overview

This skill configures AWS SES to receive inbound email and forwards messages to an HTTPS webhook via SNS. It automates creating a receipt rule set, adding a receipt rule that publishes incoming mail to an SNS topic, and guiding DNS and subscription steps. The goal is a working inbound pipeline with a confirmed SNS subscription and an active SES rule set.

How this skill works

The skill runs the SES and SNS CLI commands to verify a domain, request DKIM tokens, create an SNS topic, create and activate a receipt rule set, and add a rule that publishes received email to SNS. It instructs you to add DNS records (TXT for verification, three CNAMEs for DKIM, and an MX record) and to confirm the HTTPS subscription by handling SNS SubscriptionConfirmation messages. It checks SES/DKIM verification status and SNS subscription state to signal completion.

When to use it

• You need programmatic inbound email delivery into an AI agent or webhook.
• Building email-to-ticket or email-parsing integrations.
• Routing mail to a serverless processor or webhook for automated workflows.
• Preparing a verified domain and AWS credentials for production inbound mail.
• Migrating inbound email handling to SES/SNS in supported regions.

Best practices

• Use AWS credentials with SES and SNS permissions, or set an aws CLI profile before running commands.
• Only run SES inbound in supported regions: us-east-1, us-west-2, eu-west-1.
• Add TXT, CNAME, and MX records exactly as returned by SES; DNS propagation may take up to 72 hours.
• Ensure your webhook handles SNS SubscriptionConfirmation and verifies SNS message signatures in production.
• Enable ScanEnabled on receipt rules to let SES scan for spam/virus where appropriate.

Example use cases

• AI email agent that parses inbound messages and triggers workflows via webhook.
• Email-to-ticket system that converts incoming mail into support items.
• Inbound parsing service that extracts structured data from raw MIME payloads.
• Secure webhook pipeline for incoming transactional or notification emails.
• Serverless processors (Lambda behind HTTPS) subscribed to SNS for scaled handling.