<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Control-Tower on ferkakta.dev</title><link>https://ferkakta.dev/tags/control-tower/</link><description>Recent content in Control-Tower on ferkakta.dev</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright fizz.</copyright><lastBuildDate>Tue, 24 Mar 2026 21:00:00 -0600</lastBuildDate><atom:link href="https://ferkakta.dev/tags/control-tower/index.xml" rel="self" type="application/rss+xml"/><item><title>The Allow SCP that worked until it didn't</title><link>https://ferkakta.dev/scp-allow-overrides-notaction-deny/</link><pubDate>Tue, 24 Mar 2026 21:00:00 -0600</pubDate><guid>https://ferkakta.dev/scp-allow-overrides-notaction-deny/</guid><description>&lt;p&gt;I run a multi-tenant SaaS platform on AWS with Control Tower managing the organization. Control Tower deploys a region deny guardrail — an SCP that blocks API calls outside your home region. The mechanism is a &lt;code&gt;NotAction&lt;/code&gt; deny: it lists services that are allowed to operate globally (IAM, CloudFront, Route 53, a few dozen others), and denies everything else when &lt;code&gt;aws:RequestedRegion&lt;/code&gt; doesn&amp;rsquo;t match your approved list.&lt;/p&gt;
&lt;p&gt;This guardrail is one of the first things you hit when you try to do anything interesting. And the documentation says you can&amp;rsquo;t override a deny with an allow.&lt;/p&gt;</description></item></channel></rss>