​
Overview

Notes on the VPC for whoever works on it next — “Collaborate with your team and document important notes about this VPC”.
Navigation: Networking → VPC → click a VPC → Comments.

​
Composing

Write in the box and submit with ⌘+↵. Mark a comment Admin only or Visible to all team members.

​
Comments are permanent

Comments cannot be edited or deleted. The only action on an existing comment is toggling its visibility between Make Public and Make Admin Only.The character counter suggests a 2000-character limit, but nothing enforces it — so a long comment will post, and then it’s there for good.
Because nothing can be removed, don’t put anything sensitive here — no keys, no passwords, no pre-shared keys, no customer data. A comment posted as Admin only and later toggled public cannot be unposted.

​
What is worth writing

The console records what changed in Events. Nothing records why. That’s the gap this section fills, and it’s the difference between inheriting a VPC you can reason about and one you have to reverse-engineer.
Write the comment at the moment you make the change, not later. The detail that matters — the partner’s name, the ticket number, the reason you rejected the obvious option — is gone within a week.

​
Admin only versus visible to all

Admin only is the right default for anything about access: who can VPN in, which addresses are allowlisted, why a rule is unusually permissive. Visible to all suits operational notes — planned maintenance, why a tier is empty, what a machine is for.Neither is a security boundary for secrets. It controls visibility within your organisation, nothing more.

Events

What changed, and when.

Audit Log

Who changed it, with values.

Network Designer

Review a VPC before writing your notes.

Users

Who counts as an admin.