Cloud services catalog
PinPole ships a large service library per cloud provider. Each service becomes a node you drag from the left palette onto the canvas. Connections between nodes represent data or control flow for simulation and AI recommendations.
How to use these pages
- AWS catalog — all AWS nodes, quick actions, and configuration section names.
- Azure catalog — all Azure nodes in PinPole.
- Google Cloud (GCP) catalog — all GCP nodes (specs live under
gpcin the product codebase).
Each catalog includes:
- A quick lookup table for scanning services and internal node IDs.
- Per-service detail with the same section titles you see in the app’s Node configuration panel (collapsible groups of fields).
Engineering notes in the app
Many sections include textarea fields for engineering notes and hints on individual fields. Those full defaults live in the product; this documentation lists structure (sections and actions) so you can navigate the UI confidently.
Infrastructure placement (all providers)
When you configure a service node, PinPole appends an Infrastructure placement section (naming varies slightly by cloud):
| Provider | Typical fields |
|---|---|
| AWS | VPC name or id, Availability Zone, subnet type (private / public / isolated) |
| Azure | VNet name or id, region / AZ, subnet type (private / public / gateway) |
| GCP | VPC network name, region / zone, subnet type (private / public) |
Use consistent names across nodes that belong to the same network boundary so diagrams and simulations stay coherent.
Related documentation
- Design canvas workflow
- Configure services
- Canvas tools & toolbar
- AWS service reference notes (deep dives on common AWS patterns)
- Canvas capabilities