Step 1 of 2
Choose cloud
Choose an option to continue.
Frequently asked questions
What do I need before I start?
You need a Pulumi account, the Pulumi CLI, a cloud account in AWS, Azure, or GCP, and the framework tools for the setup you picked. The language section on the page calls out the extra runtime you need for your language choice (TypeScript, Python, or Go).
How do I deploy changes after the first release?
Edit the files in
website/, rebuild the app, and run pulumi up again from the same stack. Pulumi updates the hosting resources as needed and republishes the built site output.Does this blueprint create DNS for me?
The code-based downloads create a managed DNS zone when you set
domainName, and every setup exports the nameservers you need to delegate at your registrar. The DNS section walks through copying those values from pulumi stack output, switching to custom nameservers at the registrar, and verifying delegation with dig. The blueprint stops short of full custom-domain attachment and certificate validation so the first deployment stays small and predictable.How do I automate this in CI/CD?
Use Pulumi Deployments to run the same stack update from your Git repository. The guide includes a blueprint section that explains the repo, stack, build command, and secrets you need to wire in.
How do I tear everything down?
Run
pulumi destroy from the same project and stack, then remove the stack with pulumi stack rm if you no longer need it. If you delegated DNS to a hosted zone created by this stack, remove that delegation at your registrar or parent DNS provider too.Will this cost money?
Yes. Blueprint costs are typically small, but storage, CDN requests, bandwidth, load balancing, DNS zones, and any later custom-domain or certificate resources can all create charges in your cloud account.