How I migrated magic-link login from Resend to AWS SES + Lambda five days before launch

May 25, 2026 · 7:59 AM UTC ·8 min read · 0 reactions · 0 comments · 29 views

TL;DR · WeSearch summary

The author migrated the magic-link login system for their URL shortener, toui.io, from Resend to AWS SES and Lambda just five days before launch. This decision was driven by cost considerations, as AWS offered a more scalable and economical solution for their projected email volume. The migration process was completed in one afternoon, allowing for a more robust and flexible email service.

Key facts

▪The author initially implemented passwordless email login using Resend eleven days before the launch.
▪Cost projections indicated that AWS SES would be significantly cheaper than Resend for the expected email volume.
▪The migration to AWS involved creating a separate stack that included API Gateway, DynamoDB, and SES.

About this source

DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.

All DEV.to (Top) coverage →

Original article

DEV.to (Top)

Read full at DEV.to (Top) →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	DEV.to (Top)
Canonical URL	https://dev.to/thebrecht/how-i-migrated-magic-link-login-from-resend-to-aws-ses-lambda-five-days-before-launch-5f56
Publication time	Mon, 25 May 2026 07:59:56 +0000
Retrieval time	2026-05-25T08:07:36.528Z
Last seen	2026-05-25T08:07:36.528Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	7eb_kbLi8ZJt
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 1355576) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } thebrecht Posted on May 25 How I migrated magic-link login from Resend to AWS SES + Lambda five days before launch #aws #serverless #saas #webdev I run toui.io, a URL shortener I shipped to the public on April 7, 2026. Eleven days before launch I had passwordless email login working on Resend. Five days before launch I tore it out and rebuilt the same flow on AWS — Lambda + DynamoDB + SES + API Gateway, packaged as a SAM stack. The whole migration took one afternoon.

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed

Discussion

0 comments