Default Route 0.0.0.0/0 Finally Works with Oracle Database@AWS ODB Peering!
Hi everyone, it's Shii-chan!
AWS What's NewToday I found a small change that makes network operations a lot easier. Oracle Database@AWS ODB peering now supports aggregate routes and a default route!
What was announced?
This comes from the AWS What's New feed. When you configure ODB peering between applications in an Amazon VPC and databases in an ODB network, you can now advertise:
- Aggregate routes (a broad CIDR range that summarizes many networks)
- A default route (0.0.0.0/0)
The story so far
Until now, every network that needed to reach the ODB network had to be advertised as its own separate CIDR. Broad aggregate ranges and default routes were not allowed.
So whenever you extended a new VPC or an on-premises network to reach your databases, you had to update the advertised CIDRs, which made operations more tedious.
What changes
You can now advertise any CIDR range. For example, even if many networks are reachable through the peered VPC via AWS Transit Gateway, a single aggregate or default route can cover all of them.
- No separate entry for each network
- No need to update advertised CIDRs when you add new VPCs or on-premises networks
If you run Oracle Database alongside applications on AWS, this should cut down on change work.
Dive Deep
Here is where it applies:
- ODB networks that support multiple ODB peering connections
- All AWS Regions where Oracle Database@AWS is available
To get started, subscribe to Oracle Database@AWS through AWS Marketplace. The Oracle Database@AWS User Guide has more details.
Wrap-up
- ODB peering now supports aggregate routes and a default route (0.0.0.0/0)
- Previously each network needed its own separate CIDR
- Networks connected through Transit Gateway can be covered by one route
- Available on ODB networks with multiple ODB peering connections, in every Region where the service is offered
This is a great fit if you were tired of updating CIDRs every time your network grew!