fix(docs): Add route override note for aws peering

[moredure]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
documentation	Ready	Preview	Aug 27, 2026 10:47am

[qodo-free-for-open-source-projects]

PR Summary by Qodo

Document AWS peering route precedence risks

🐞 Bug fix 📝 Documentation 🕐 Less than 5 minutes

AI Description

• Warns that more-specific AWS routes override broader Dragonfly Cloud peering routes.
• Adds an overlap example and route-table checks to prevent silent connectivity failures.

Diagram

graph TD
  Traffic["VPC Traffic"] --> Routes["AWS Route Table"] --> Match{"More-specific match?"}
  Match -->|No| Peering["Peering Route"] --> Cloud["Dragonfly Cloud"]
  Match -->|Yes| Alternate["Alternate Target"]

Loading

High-Level Assessment

An inline warning beside the AWS route setup steps is the appropriate approach because reviewers and users encounter the risk at the exact configuration point. A separate troubleshooting page would make this critical prerequisite easier to miss.

Files changed (1) +18 / -0

Documentation (1) +18 / -0

connections.mdWarn about AWS route overlap during peering setup +18/-0

Warn about AWS route overlap during peering setup

• Adds an AWS peering warning explaining longest-prefix-match behavior and how overlapping, more-specific routes can silently redirect traffic. Provides a concrete CIDR example and instructs users to inspect associated subnet route tables before adding the peering route.

docs/cloud/connections.md

[qodo-free-for-open-source-projects]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

1. Valid alternate routes misclassified 🐞 Bug ≡ Correctness

Description

The warning claims any more-specific route to a different target breaks connectivity, but
longest-prefix matching only proves that traffic bypasses the peering route; a transit gateway or
another connection may intentionally provide a valid path to the destination. This blanket
prohibition can make users remove a working alternate route even when the data store remains
reachable through it.

Code

docs/cloud/connections.md[R64-65]

+would be sent to that route instead of the AWS peering connection, causing the data store to become unreachable
+from those subnets.

Evidence

The added example itself establishes only that traffic is sent to the alternate target instead of
the peering connection, then makes the unsupported leap that the data store is therefore
unreachable. It explicitly lists transit and other peering gateways as alternate targets, while the
surrounding setup scopes the direct peering route to subnets that require that route.

docs/cloud/connections.md[61-65]
docs/cloud/connections.md[45-49]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The warning equates bypassing the AWS peering route with loss of connectivity, although a more-specific route can intentionally reach the destination through another target.

## Issue Context
Longest-prefix matching establishes which route wins, not whether the winning target provides connectivity. Describe the route as conflicting only when its target does not provide the intended valid path, and avoid stating that every alternate target makes the data store unreachable.

## Fix Focus Areas
- docs/cloud/connections.md[57-68]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

Tip of the day

💡 Did you know, you can ask Qodo to dismiss a finding you disagree with, with your reason on record

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[qodo-free-for-open-source-projects]

1. Valid alternate routes misclassified 🐞 Bug ≡ Correctness

The warning claims any more-specific route to a different target breaks connectivity, but
longest-prefix matching only proves that traffic bypasses the peering route; a transit gateway or
another connection may intentionally provide a valid path to the destination. This blanket
prohibition can make users remove a working alternate route even when the data store remains
reachable through it.

Agent Prompt

## Issue description
The warning equates bypassing the AWS peering route with loss of connectivity, although a more-specific route can intentionally reach the destination through another target.

## Issue Context
Longest-prefix matching establishes which route wins, not whether the winning target provides connectivity. Describe the route as conflicting only when its target does not provide the intended valid path, and avoid stating that every alternate target makes the data store unreachable.

## Fix Focus Areas
- docs/cloud/connections.md[57-68]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools