<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Fedramp on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/fedramp/</link><description>Recent content in Fedramp on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 22 Sep 2026 15:18:39 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/fedramp/index.xml" rel="self" type="application/rss+xml"/><item><title>Amazon EVS achieves FedRAMP Class C authorization in all US regions</title><link>https://curadevops.metacog.co.kr/insights/2026-09-22-amazon-evs-now-in-scope-for-fedramp-class-c/</link><pubDate>Tue, 22 Sep 2026 15:18:39 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-09-22-amazon-evs-now-in-scope-for-fedramp-class-c/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> Relevant if running VMware workloads on AWS in a government or regulated environment; no operational change required, but expands compliance options for teams evaluating EVS for FedRAMP-scoped workloads.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> If the org has federal or regulated customers, EVS gaining FedRAMP Class C authorization may open a path to migrate VMware workloads to AWS while meeting compliance requirements — worth noting in cloud strategy discussions.&lt;/li>
&lt;/ul></description></item></channel></rss>