aws-ses-inbound

This skill provides a comprehensive automation workflow for setting up Amazon Simple Email Service (SES) to receive inbound emails and automatically forward them to an HTTPS webhook via Amazon Simple Notification Service (SNS). It is designed for engineers and developers building AI-powered email agents, email-to-ticket management systems, or custom inbound email parsing APIs that require reliable, scalable infrastructure.

By automating the complex sequence of AWS infrastructure setup—including identity verification, DKIM token configuration, SNS topic creation, receipt rule sets, and webhook subscription confirmation—this skill reduces manual configuration errors and ensures that email traffic is securely routed from SES to your application backend.

• Configures SES inbound receipt rules to capture incoming mail for specific verified domains.

• Manages SNS topic creation and secure subscription of HTTPS endpoints to receive email payloads.

• Provides clear validation steps for domain ownership and DKIM email authentication.

• Handles the technical requirements for SNS subscription confirmation, including the necessary handshake with the notification endpoint.

• Automates the activation of receipt rule sets to ensure only one active configuration exists for incoming mail.

• Prerequisites: Users must have the AWS CLI installed, configured with appropriate IAM credentials, and possess a domain name with administrative DNS access.

• Constraints: Inbound email features are geographically limited to us-east-1, us-west-2, and eu-west-1 regions; ensure your environment variables are set accordingly.

• Inputs: Requires AWS region, verified domain identity, and a functional HTTPS endpoint capable of handling JSON-encoded SNS notifications.

• Outputs: Provides an active receipt rule set in the AWS SES environment and ensures the SNS subscription status reaches the 'confirmed' state.

• Operational Detail: The skill relies on standard AWS APIs to manage DNS records (TXT/CNAME/MX) and receipt rules. Successful completion requires the user to update their domain's DNS records based on the tokens provided by the workflow, enabling full email authentication and routing.