<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Policy on StorageNews</title>
    <link>https://storagenews.top/tags/policy/</link>
    <description>Recent content in Policy on StorageNews</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 25 Jul 2026 12:34:57 +0000</lastBuildDate>
    <atom:link href="https://storagenews.top/tags/policy/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Access Denied S3 403: Diagnose KMS and IAM Layers</title>
      <link>https://storagenews.top/posts/kiro-cli-s3-403-diagnosis-let-it-read-keep-the-fix-yours/</link>
      <pubDate>Tue, 14 Jul 2026 00:00:00 +0000</pubDate>
      <author>StorageNews</author>
      <guid>https://storagenews.top/posts/kiro-cli-s3-403-diagnosis-let-it-read-keep-the-fix-yours/</guid>
      <description>An S3 access denied error returns HTTP 403, but the root cause rarely sits in a single log line.</description>
    </item>
    <item>
      <title>IAM policy S3: Fix ListBucket errors fast</title>
      <link>https://storagenews.top/posts/iam-policy-s3-fix-listbucket-errors-fast/</link>
      <pubDate>Thu, 09 Jul 2026 00:00:00 +0000</pubDate>
      <author>StorageNews</author>
      <guid>https://storagenews.top/posts/iam-policy-s3-fix-listbucket-errors-fast/</guid>
      <description>Most S3 failures stem from missing bucket ARNs for ListBucket. Learn why you need two distinct resource formats to fix AccessDenied errors.</description>
    </item>
    <item>
      <title>Lifecycle policy rules that cut S3 costs by 20%</title>
      <link>https://storagenews.top/posts/lifecycle-policy-rules-that-cut-s3-costs-by-20/</link>
      <pubDate>Mon, 06 Jul 2026 00:00:00 +0000</pubDate>
      <author>StorageNews</author>
      <guid>https://storagenews.top/posts/lifecycle-policy-rules-that-cut-s3-costs-by-20/</guid>
      <description>Automate transitions to One Zone-IA to save 20% on storage. Learn how to delete logs after 366 days using precise S3 lifecycle rules.</description>
    </item>
  </channel>
</rss>
