<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vpc-Peering on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/vpc-peering/</link><description>Recent content in Vpc-Peering on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 16 Oct 2026 15:05:37 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/vpc-peering/index.xml" rel="self" type="application/rss+xml"/><item><title>Oracle Database@AWS ODB peering adds aggregate and default route support</title><link>https://curadevops.metacog.co.kr/insights/2026-10-16-oracle-database-aws-supports-aggregate-and-default-routes-fo/</link><pubDate>Fri, 16 Oct 2026 15:05:37 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-10-16-oracle-database-aws-supports-aggregate-and-default-routes-fo/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> If you run Oracle Database@AWS, this new GA capability lets you advertise a single aggregate CIDR or default route (0.0.0.0/0) over ODB peering instead of managing per-network entries — worth updating your ODB network peering config during your next network ops review cycle.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>