Pick a starting point — open it to see what it builds, then continue to chat.
Launches a single EC2 instance inside a dedicated VPC, on a public subnet, protected by a security group.
A classic web/app/data topology: a public load balancer, an application EC2 tier, and a PostgreSQL RDS database, each in its own subnet of a new VPC.
A managed PostgreSQL database on Amazon RDS, placed in a private subnet and locked down with a database security group.
A private S3 bucket with versioning and server-side encryption enabled for safe, durable object storage.
Reuses an existing VPC and subnet via data sources, then deploys a new EC2 instance and security group into that pre-existing network.
A primary and secondary region, each with its own VPC and EC2 tier, fronted by a Route 53 record for regional failover.
A Linux VM with a full networking stack — resource group, virtual network, subnet, network interface, and network security group.
Web, app, and data tiers on Azure: an App Service front end, an application subnet, and an Azure SQL database, all inside one virtual network.
A managed Azure SQL server and database with a firewall rule controlling which IP ranges may connect.
A storage account with a blob container and a lifecycle management policy that tiers and expires old data automatically.
Three isolated resource groups — dev, test, and prod — each with its own storage account, giving you clean environment separation.
A user-assigned managed identity granted a scoped role assignment, plus a Key Vault it can access — the building blocks of least-privilege access.
A Compute Engine VM on a custom VPC network and subnetwork, with a firewall rule allowing controlled ingress.
A VPC network with an application Compute Engine tier and a Cloud SQL PostgreSQL database, fronted by a load balancer forwarding rule.
A managed Cloud SQL PostgreSQL instance with a database and an application user, ready for your workloads to connect.
A Cloud Storage bucket with object versioning and a lifecycle rule that cleans up old, non-current object versions.
Three GCP projects — dev, test, and prod — under a shared folder, giving each environment its own isolated project boundary.
A service account granted a project-level IAM role, plus a managed key — the least-privilege identity building block for GCP workloads.
