What Is AWS SES Documentation and How Do I Use It to Get Started?

AWS SES documentation is the set of official AWS reference material plus community guides that explain how to configure and send email through Amazon Simple Email Service. Use the official docs when you need authoritative API details, quotas, and policy; use unofficial resources like Send With SES when you want a step-by-step walkthrough of the setup process, especially for sandbox exit and deliverability topics. The two are complementary: official docs tell you what the service does, community guides tell you what order to do things in.

Official vs. unofficial AWS SES documentation

The Send With SES site describes itself as "the unofficial and simpler documentation site for AWS Simple Email Service," built as a repository of articles and step-by-step guides. That framing is accurate for its role: it does not replace the official reference, but it sequences the setup work.

What the documentation actually covers

Sandbox and production access

New SES accounts start in the sandbox, which restricts who you can send to. As of early 2024, AWS changed the process to get production access: you now need a domain with SPF, DMARC, and DKIM in place before you can request to be moved out of the sandbox. This is the single most important change to understand, because it means DNS configuration comes before the access request, not after.

Email authentication: SPF, DKIM, DMARC

These three records are the prerequisite for production access and for deliverability generally. The documentation covers how to set each one up on your domain. If you are stuck in the sandbox, check these first.

Transactional vs. marketing email

The docs distinguish between the two because they have different sending patterns and reputation implications:

• Transactional email — messages customers expect, such as signups and password resets. These typically have high engagement and help build sending reputation.
• Marketing email — promotional messages to current and potential customers, such as product announcements and offers. These need more careful list management and volume control.

Account warm-up

Warm-up means sending small batches of email initially, then slowly ramping up over time, targeting known recipients who are likely to engage (open, reply). The goal is to establish a positive sending reputation so future mail lands in inboxes rather than spam folders. This applies to any new sending account, not just SES.

Pricing and free tier: what changed

The SES free tier was reduced from 62,000 emails per month to 3,000 emails per month as of August 2023. The Send With SES site argues this was a reasonable move rather than a bad one, and provides a pricing breakdown article explaining the reasoning. If you are planning volume, read the pricing breakdown before you commit to an architecture — the free tier change affects how you estimate cost for anything beyond low-volume sending.

A practical order of operations

1. Read the official SES documentation for the API and quota basics.
2. Configure SPF, DKIM, and DMARC on your sending domain.
3. Request production access (requires step 2 as of early 2024).
4. Decide whether your use case is transactional, marketing, or both.
5. Warm up the account with small, engaged batches before scaling.
6. Check the pricing breakdown to model cost at your expected volume.

When to use which source

• Use official docs when you need exact API parameters, current quotas, error code meanings, or policy language.
• Use community guides when you are following a setup sequence and want context on why each step matters, or when you hit a snag that the reference material does not frame as a workflow.
• Use both for sandbox exit, since that is where policy (official) and process (community) intersect most tightly.

One caveat: unofficial guides can lag behind AWS changes. The early-2024 production access change is a good example of a policy shift that community sites had to update. When a guide and the official docs disagree on a requirement, trust the official docs.