How I migrated magic-link login from Resend to AWS SES + Lambda five days before launch
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.
- ▪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.
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).
Discussion
0 commentsMore from DEV.to (Top)
