Cloud Infrastructure Provisioning

A provider chosen on evidence, accounts and networks laid out properly, compute, storage and databases sized for the real workload, and the routines that keep a cloud estate reliable for engineers and founders.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Cloud Infrastructure Provisioning, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

⚙️ Software Engineering

Cloud Infrastructure Provisioning

Choosing and setting up cloud services for compute, storage, networking and databases so applications run reliably at the right cost.

  1. Workload requirements sheet before provisioning
  2. Choosing a cloud provider for the first workload
  3. Separate accounts for production, staging and sandboxes
  4. Root account lockdown and break-glass access
  5. Budget alerts and spend guardrails from day one
  6. Region and availability zone selection
  7. Resource naming and tagging convention
  8. Network address plan for every environment
  9. Compute model choice among VMs, containers and serverless
  10. Managed database engine and size selection
  11. Monthly cloud resource inventory
  12. Quarterly access review of cloud users and roles
  13. Database backup restore tests
  14. Machine image patching and refresh cycle
  15. Service quota and limit watch
  16. Certificate and domain renewal register
  17. Provider notices and deprecation triage
  18. Sandbox lifecycle with expiry dates
  19. Cloud credential and key rotation schedule
  20. Virtual networks, routing and NAT fundamentals
  21. Identity and access policies in practice
  22. Object storage classes, lifecycle and access
  23. Load balancers and DNS routing practice
  24. Managed database replicas and failover drills
  25. Estimating cost with the provider pricing calculator
  26. Shared responsibility map for your services
  27. Serverless functions and event triggers practice
  28. Moving databases off public endpoints
  29. Multi-zone upgrade for the production database
  30. Content delivery network for static assets
  31. Managed secrets store instead of env files
  32. Instance type selection from measured load
  33. Managed or self-hosted cache and message queue
  34. Well-architected self-review of the production stack
  35. Outbound traffic and egress controls
  36. Storage design for user uploads
  37. Production launch infrastructure readiness check
  38. Database major version upgrade window
  39. Startup cloud credits application
  40. Cloud support plan and contract renewal
  41. Founder's first production stack on a small budget
  42. Handing infrastructure to a first hire or contractor
  43. Taking over an undocumented cloud account
  44. Hosting answers for customer security questionnaires
  45. Moving from a hosting platform to your own cloud account
  46. Multi-region active-passive design
  47. Hybrid connectivity to an on-premises network
  48. Data residency and region requirements mapping
  49. Landing zone with organisation guardrail policies
  50. Cloud exit and portability assessment

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Workload requirements sheet before provisioning

Teams that open the cloud console before writing anything down end up sizing for a guess and paying for it twice. One page listing expected users, requests per second at peak, data volume after a year, latency targets, uptime promise, recovery point and recovery time, and any data location rules gives every later choice in this area something to be measured against.

First tasks

  • Write down expected peak requests per second and active users for the first year
  • Estimate stored data after twelve months, including files and backups
  • Agree recovery point and recovery time targets with the product owner
  • List every data location or compliance rule that customers or regulators impose

Choosing a cloud provider for the first workload

Switching providers after launch costs months, so the choice deserves a week of evidence rather than whichever console someone used at a previous job. Scoring two or three providers against the requirements sheet, the team's existing skills, regional coverage, managed database options, support plans and startup credits turns a habit into a decision you can defend to investors and new hires.

First tasks

  • List the managed services the requirements sheet needs from any provider
  • Score two or three providers on services, regions, support, cost and team skills
  • Deploy a hello-world service on the front runner to test the tooling
  • Write a one-page decision note with the scores and the reasons

Separate accounts for production, staging and sandboxes

Running everything in one account means a mistyped command in a test can delete production data, and nobody can see which environment is costing what. Splitting into separate accounts or projects for production, staging, shared services and personal sandboxes, grouped under one organisation with consolidated billing, gives each environment its own blast radius and its own bill.

First tasks

  • Sketch the account layout for production, staging, shared tooling and sandboxes
  • Create the organisation and turn on consolidated billing
  • Create each account and connect them to single sign-on
  • Draw the final structure and add it to the infrastructure README

Make it yours.

Install Cloud Infrastructure Provisioning, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.