<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/">
  <channel>
    <title>Warren Parad</title>
    <link>https://warrenparad.net</link>
    <description>Articles by Warren Parad, Authress CTO | Tech Entertainer | International Speaker | Cloud Security Architect | AWS Community Builder | Host of Adventures In DevOps</description>
    <language>en-us</language>
    <lastBuildDate>Tue, 07 Apr 2026 21:23:03 GMT</lastBuildDate>
    <ttl>10080</ttl>
    <sy:updatePeriod>weekly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <atom:link href="https://warrenparad.net/rss.xml" rel="self" type="application/rss+xml" />

  <item>
    <title>Making rate limiting in AWS less terrible</title>
    <link>https://warrenparad.net/articles/exceeding-the-aws-rate-limiting-cloudfront-usage-plans</link>
    <guid>https://warrenparad.net/articles/exceeding-the-aws-rate-limiting-cloudfront-usage-plans</guid>
    <pubDate>Tue, 07 Apr 2026 00:00:00 GMT</pubDate>
    <atom:updated>2026-04-07T21:22:36.814Z</atom:updated>
    <description>APIGW Usage Plans won't get you the per-user rate limiting you need. And using a WAF is an incomplete solution. But rolling your own is of course fraught with the usual challenges.</description>
    <category>aws</category>
    <category>cloudfront</category>
    <category>api gateway</category>
    <category>rate limiting</category>
    <category>security</category>
    <category>waf</category>
  </item>
  </channel>
</rss>