PinPole User Guide — AWS supplement
Version 2.0 · Replaces Sections 11, 14–16, 19 of legacy v1.0 (AWS-only monolith)
Read Shared features first for provider-agnostic workflows. This page adds AWS-specific behaviour.
1. AWS on the canvas
- The palette lists AWS services (icons and labels aligned to familiar AWS names).
- Compatibility rules enforce plausible wiring (e.g. blocking impossible edges); messages reference AWS-shaped patterns.
- Node configuration sections mirror AWS parameters — capacity, runtime, endpoints, service quotas, etc.
Catalogue: every modelled service and panel section title is listed in the AWS catalog.
2. Simulation nuances (AWS)
- Metrics and alerts reflect AWS service semantics (e.g. Lambda concurrency, API Gateway throttle models, DynamoDB capacity).
- When tuning provisioned concurrency, reserved concurrency, or account limits, restart simulations cleanly if behaviour looks stuck — see FAQ.
- For high-RPS API Gateway patterns, CloudFront plus async paths (SQS) often appear in recommendations — Pattern 6.
Deep dive: AWS service reference notes. Patterns: Optimisation patterns.
3. Infrastructure code and export (AWS)
From the canvas you can align with common AWS IaC flows:
| Direction | Notes |
|---|---|
| Terraform | Export or definition hand-off for Terraform pipelines — verify the current Export panel for HCL vs intermediate JSON. |
| AWS CDK | CDK-oriented export where enabled for AWS diagrams. |
| CloudFormation | Stack-oriented payloads when the product surfaces CloudFormation mapping. |
Roadmap for full Terraform HCL generation: Roadmap. Shared export overview: Shared features — §11 Export.
4. Deploy to Cloud — Live (AWS)
Deploy to Cloud for AWS is available on eligible plans.
High level:
- Connect — cross-account IAM role via STS (CloudFormation creates least-privilege role in your account).
- Review — inspect generated plan vs canvas.
- Deploy — provision resources; monitor the deploy panel.
- Verify — confirm live endpoints and health.
Full procedure: Step 7 — Deploy to AWS.
Practice: deploy to non-prod first; tie deployments to a simulation run ID recorded in execution history.
5. Cloud Terminal (AWS context)
Cloud Terminal answers AWS-flavoured questions against the simulated architecture (limits, behaviour, config). It is not a replacement for the real AWS CLI in your account, but accelerates design-time reasoning.
See Cloud Terminal.
6. Billing and costs (design-time)
- Estimated monthly figures on runs and history are models for comparison — not invoices.
- Always validate against AWS Pricing Calculator and your organisation’s discounts before commitments.
7. Where AWS content lives in these docs
| Topic | Doc |
|---|---|
| Design workflow | Design canvas |
| Configure nodes | Configure services |
| Simulate | Run simulation |
| Results | Interpret results |
| Recommendations | AI recommendations |
| PinPole vs native tools | PinPole vs AWS |
Return to User guide overview · Shared features · Azure · GCP