<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Niyantrac Blog</title>
    <link>https://niyantrac.com/blog</link>
    <description>Product updates and guides on AWS backup, versioning, and rollback.</description>
    <language>en</language>
    <atom:link href="https://niyantrac.com/blog/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What's new in Niyantrac 1.8</title>
      <link>https://niyantrac.com/blog/introducing-niyantrac-1-8</link>
      <guid isPermaLink="true">https://niyantrac.com/blog/introducing-niyantrac-1-8</guid>
      <pubDate>Fri, 30 Oct 2026 00:00:00 GMT</pubDate>
      <description>VPC and S3 coverage, multi-account support, built-in support tickets, in-app updates, and two-step sign-in — everything that landed in Niyantrac 1.8.</description>
      <category>Product updates</category>
      <category>VPC</category>
      <category>S3</category>
    </item>
    <item>
      <title>When a WAF rule starts blocking real customers</title>
      <link>https://niyantrac.com/blog/aws-waf-rule-blocking-real-customers</link>
      <guid isPermaLink="true">https://niyantrac.com/blog/aws-waf-rule-blocking-real-customers</guid>
      <pubDate>Fri, 30 Oct 2026 00:00:00 GMT</pubDate>
      <description>A new WAF rule can block checkout, logins, or your own API calls the moment it's saved. Here's how to stop the damage fast, find the rule responsible, and restore the Web ACL that worked.</description>
      <category>AWS has no undo</category>
      <category>WAF</category>
    </item>
    <item>
      <title>Recovering from a bad Route 53 change</title>
      <link>https://niyantrac.com/blog/recover-from-bad-route-53-change</link>
      <guid isPermaLink="true">https://niyantrac.com/blog/recover-from-bad-route-53-change</guid>
      <pubDate>Fri, 30 Oct 2026 00:00:00 GMT</pubDate>
      <description>Route 53 keeps no record history, DNS caching stretches every mistake out, and a deleted hosted zone comes back with new name servers. Here's the recovery playbook.</description>
      <category>AWS has no undo</category>
      <category>Route 53</category>
    </item>
    <item>
      <title>How to roll back a CloudFront distribution change</title>
      <link>https://niyantrac.com/blog/roll-back-cloudfront-distribution-change</link>
      <guid isPermaLink="true">https://niyantrac.com/blog/roll-back-cloudfront-distribution-change</guid>
      <pubDate>Fri, 30 Oct 2026 00:00:00 GMT</pubDate>
      <description>CloudFront has no version history. To undo a bad change you need the old configuration — and AWS doesn't keep it for you. Here's how to recover it, and how to avoid needing to.</description>
      <category>AWS has no undo</category>
      <category>CloudFront</category>
    </item>
    <item>
      <title>How to recover a deleted IAM role</title>
      <link>https://niyantrac.com/blog/recover-deleted-iam-role</link>
      <guid isPermaLink="true">https://niyantrac.com/blog/recover-deleted-iam-role</guid>
      <pubDate>Thu, 29 Oct 2026 00:00:00 GMT</pubDate>
      <description>AWS has no undelete for IAM roles. Here's how to rebuild one from CloudTrail by hand — and the resource-policy gotcha that catches almost everyone.</description>
      <category>AWS has no undo</category>
      <category>IAM</category>
    </item>
    <item>
      <title>Your S3 bucket policy has no history</title>
      <link>https://niyantrac.com/blog/s3-bucket-policy-has-no-history</link>
      <guid isPermaLink="true">https://niyantrac.com/blog/s3-bucket-policy-has-no-history</guid>
      <pubDate>Thu, 29 Oct 2026 00:00:00 GMT</pubDate>
      <description>S3 Versioning protects your objects, not your bucket's configuration. Edit a bucket policy and the old one is simply gone. Here's how to recover it — and catch risky changes before they bite.</description>
      <category>AWS has no undo</category>
      <category>S3</category>
    </item>
    <item>
      <title>A Security Group change broke production: how to find it and fix it</title>
      <link>https://niyantrac.com/blog/security-group-change-broke-production</link>
      <guid isPermaLink="true">https://niyantrac.com/blog/security-group-change-broke-production</guid>
      <pubDate>Thu, 29 Oct 2026 00:00:00 GMT</pubDate>
      <description>Security Group edits take effect instantly and AWS keeps almost no history of them. Here's how to track down the change that broke things — and roll it back safely.</description>
      <category>AWS has no undo</category>
      <category>VPC</category>
    </item>
    <item>
      <title>AWS has no undo button</title>
      <link>https://niyantrac.com/blog/aws-has-no-undo-button</link>
      <guid isPermaLink="true">https://niyantrac.com/blog/aws-has-no-undo-button</guid>
      <pubDate>Wed, 28 Oct 2026 00:00:00 GMT</pubDate>
      <description>CloudTrail tells you what changed. AWS Config can show you what it looked like. Neither one puts it back. Here's what that gap costs, and how to close it.</description>
      <category>AWS has no undo</category>
      <category>Governance</category>
    </item>
  </channel>
</rss>
