Quickstart

Connect AWSCopy Anchor Link

Sign up at app.stamp0.com. Onboarding asks for the SES region to send from (for example us-east-1) and generates a CloudFormation Quick Create link. Open it while signed in to your AWS account, tick the IAM acknowledgement, and choose Create stack.

When the stack reaches CREATE_COMPLETE (one to two minutes), copy its RoleArn output from the stack's Outputs tab, paste it into Stamp0 and choose Verify connection. Stamp0 assumes the role and shows your SES sandbox status and sending quota. Connect AWS explains what the stack creates and what the role may do.

Add your domainCopy Anchor Link

Under Domains, add the domain you send from, such as acme.co. Stamp0 creates the SES identity in your account and lists the DNS records: three DKIM CNAMEs, the MAIL FROM MX and TXT on send.acme.co, and a DMARC TXT. If the domain's hosted zone is on Route 53 in the same account and the stack allows it, Stamp0 publishes them for you. Verification usually completes within minutes. See Domains.

Create an API keyCopy Anchor Link

Under Developers → API keys, create a key. A Sending access key can only send, which is all your app needs. The token starts with s0_ and is shown once; store it as STAMP0_API_KEY.

Send an emailCopy Anchor Link

Stamp0 serves Resend's API at https://api.stamp0.com, so the official Resend SDKs work with that base URL.

npm install resend

import { Resend } from 'resend';

const stamp0 = new Resend(process.env.STAMP0_API_KEY, {
  baseUrl: 'https://api.stamp0.com',
});

const { data, error } = await stamp0.emails.send({
  from: 'Acme <hello@acme.co>',
  to: 'you@example.com',
  subject: 'Hello from my own AWS',
  html: '<p>Sent through SES, via Stamp0.</p>',
});

The response is { "id": "em_…" }. Open Emails → Activity to watch it move from queued to sent and delivered.