<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Fips on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/fips/</link><description>Recent content in Fips on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 20 Aug 2026 11:19:17 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/fips/index.xml" rel="self" type="application/rss+xml"/><item><title>AWS Storage Gateway FIPS endpoints now available over PrivateLink</title><link>https://curadevops.metacog.co.kr/insights/2026-08-20-aws-storage-gateway-now-supports-fips-compliant-private-conn/</link><pubDate>Thu, 20 Aug 2026 11:19:17 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-20-aws-storage-gateway-now-supports-fips-compliant-private-conn/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> If you run Tape or Volume Gateway for regulated workloads, you can now route FIPS-compliant traffic privately via PrivateLink instead of over the public internet; plan to create a FIPS interface VPC endpoint and re-activate gateways on software version 3.2.7 or later.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> For organizations with compliance mandates (FedRAMP, HIPAA) using Storage Gateway, this removes a previous architectural constraint — FIPS traffic can now stay private — which may simplify audit scope for regulated workloads.&lt;/li>
&lt;/ul></description></item></channel></rss>