<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Aws on jed.codes</title><link>https://jed.codes/tags/aws/</link><description>Recent content in Aws on jed.codes</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 04 Jul 2026 11:00:23 -0700</lastBuildDate><atom:link href="https://jed.codes/tags/aws/index.xml" rel="self" type="application/rss+xml"/><item><title>Setting Up SSO for Your Personal AWS Account</title><link>https://jed.codes/posts/setting-up-sso-for-your-personal-aws-account/</link><pubDate>Sat, 04 Jul 2026 11:00:23 -0700</pubDate><guid>https://jed.codes/posts/setting-up-sso-for-your-personal-aws-account/</guid><description>&lt;p&gt;I do a fair bit of my personal work in AWS using serverless services. I love deferring long-running services in favor of pay-for-what-you-use pricing; it makes a ton of sense to me, and many of my applications cost less than $1/mo. A gotcha I hear from folks: managing multiple projects under a single AWS account gets challenging, both from a &amp;ldquo;total cost of ownership&amp;rdquo; standpoint and when you want to constrain access to just one project. Having a &lt;strong&gt;Single Sign On (SSO) AWS login&lt;/strong&gt; with multiple profiles is a stepping stone to a simpler AWS experience.&lt;/p&gt;</description></item></channel></rss>