[FINDINGS] VPN Gateway Connections

[pmhanson]

Environment

Cloud provider(s) scanned:

• AWS
• [ X] Azure

Number of accounts/subscriptions scanned:
10+

Regions scanned:
1

Industry (optional):

What CleanCloud Found

Total findings:

Biggest waste detected:
It found 4 VPN Gateways, but claims that they are all idle. Three of the four are not idle and had traffic within the last 30 days. There were loads of other findings but I'll create other tickets for those.

Any surprises?

Estimated Savings

Estimated monthly waste identified:

Have you acted on the findings?

• Yes — cleaned up resources
• Planning to
• [X ] Using it for visibility only

How You're Using CleanCloud

• Local development
• CI/CD pipeline enforcement
• Scheduled scans
• Security/compliance review

Enforcement mode (if any):

Feedback

What worked well?

What could be better?

---

Thanks for sharing — your feedback directly shapes what we build next.

[sureshcsdp]

Thanks for reporting this and sharing your findings — really appreciate it, especially with 10+ subscriptions scanned!

This is a bug for sure and we have just fixed.

The root cause: Azure's list_connections() API returns summary objects where connection_status is often None even for live, active connections.

The old code only counted a connection as active when status was explicitly Connected — so your three active gateways with unpopulated status were incorrectly treated as idle.

The fix is in v1.6.4 — update with:
pipx upgrade cleancloud
or
pip install --upgrade cleancloud

The fixed rule now treats None/unknown status as active (conservative assumption), only flagging when status is explicitly NotConnected or Disconnected.

If its not fixed with latest v1.6.4 please do let us know here by adding a comment with more info.

And please do raise issues other findings — first-hand reports from real environments with 10+ subscriptions are exactly what helps make the rules more accurate.

If you're comfortable sharing the estimated waste figures too, that's invaluable for validating cost accuracy across different account sizes.

Looking forward to them!

[sureshcsdp]

Hi @pmhanson - just a quick note that we’ve released version v1.7.1. If you happen to do any further testing, it would be great if you could upgrade your local CleanCloud version to this release.

If the scan finds any cost waste in your environment, it would be really helpful if you could create a discussion and share the waste report there. And if you run into any bugs or issues, please feel free to create a new issue in the Issues tab.

Thanks!

[sureshcsdp]

Hi @pmhanson would you be able to pull latest version and run the engine in your environements and see how it works ?
Thanks for your support!

[sureshcsdp]

Hi @bt-paulhanson Thanks for confirming.
In the meantime, if you see any more issues, could you please raise a separate issue?
Many Thanks for checking it out.