From 4c6e4a9d07ec9013c97d315745a784de5012526b Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 21 Jul 2026 18:37:04 +0000 Subject: [PATCH 1/2] Add cloud-agnostic getting-started overview and connect-cloud page Rebuild /docs/get-started/ as an end-to-end overview: a light "Why Pulumi" value-prop section, a five-step journey (install, connect your cloud account, write a program, deploy, iterate) with a Mermaid flowchart, the existing cloud fan-out cards, and a link to the previously orphaned Pulumi for Terraform Users flow. Add /docs/get-started/connect-cloud/, a generic credentials explainer targeting the funnel's biggest dropoff step: Pulumi has no credential system of its own and uses your cloud CLI's existing credentials. Includes an identity-check command table and a card fan-out into each cloud's existing configure-access page (new data-track values so landing-page analytics stay clean), plus the ESC OIDC best-practice pointer. Per-cloud flows, layouts, and nav data files are intentionally untouched; a follow-up PR will consolidate the near-identical flow steps into shortcodes. Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_01SFeRMk9djuoDMn83d4wZ4v --- content/docs/get-started/_index.md | 33 ++++++++- content/docs/get-started/connect-cloud.md | 83 +++++++++++++++++++++++ 2 files changed, 114 insertions(+), 2 deletions(-) create mode 100644 content/docs/get-started/connect-cloud.md diff --git a/content/docs/get-started/_index.md b/content/docs/get-started/_index.md index fae85265d3e8..99f311492198 100644 --- a/content/docs/get-started/_index.md +++ b/content/docs/get-started/_index.md @@ -1,6 +1,6 @@ --- title_tag: Get Started with Pulumi -meta_desc: Step-by-step guides for creating, deploying, and managing infrastructure with Pulumi on the cloud using your favorite language. +meta_desc: Learn the five steps to get started with Pulumi — install the CLI, connect your cloud account, write a program, deploy, and iterate — then pick your cloud. title: Get Started #Breadcrumb h1: Get Started with Pulumi # Page title no_on_this_page: true @@ -22,7 +22,32 @@ Pulumi is a modern [infrastructure as code](/what-is/what-is-infrastructure-as-c Pulumi IaC is free, [open source](https://github.com/pulumi/pulumi), and optionally pairs with [Pulumi Cloud](/docs/iac/guides/basics/pulumi-cloud-vs-oss/) to make managing infrastructure secure, reliable, and hassle-free. -Choose a cloud provider to get started: +## Why Pulumi + +- **Use a real programming language.** Define infrastructure in TypeScript, Python, Go, C#, Java, or YAML — with loops, functions, testing, and full IDE support instead of a domain-specific language. +- **See every change before it happens.** Pulumi previews exactly what will be created, updated, or deleted before anything touches your cloud account. +- **Keep your existing credentials.** Pulumi has no credential system of its own — it uses the cloud access you already have, so there's nothing new to set up or secure. + +For the full story, see [What is Pulumi?](/what-is/what-is-pulumi/). + +## How getting started works + +Getting started follows the same five steps on every cloud; only the provider details differ. + +```mermaid +flowchart LR + A["1. Install the CLI"] --> B["2. Connect your cloud account"] --> C["3. Write a program"] --> D["4. Deploy"] --> E["5. Iterate and evolve"] +``` + +1. **Install the Pulumi CLI.** [Install Pulumi](/docs/install/) with your operating system's package manager or a one-line installer script. One CLI covers every cloud and every language. +1. **Connect your cloud account.** Pulumi authenticates to your cloud the same way your cloud provider's own CLI does — if that already works on your machine, you're done. See [Connect your cloud account](/docs/get-started/connect-cloud/) for how this works and how to set it up. +1. **Write a program.** Run `pulumi new` to scaffold a project from a template in your language of choice, then declare cloud resources as code. +1. **Deploy.** Run `pulumi up` to preview the planned changes and then apply them. Pulumi records what it created in a [stack](/docs/iac/concepts/stacks/), an isolated, configurable instance of your program — see [How Pulumi Works](/docs/iac/guides/basics/how-pulumi-works/) for the details. +1. **Iterate and evolve.** Change your code and run `pulumi up` again — Pulumi computes the difference and applies only what changed. When you're done experimenting, `pulumi destroy` tears everything down cleanly. + +## Choose your cloud + +Ready to begin? Choose a cloud provider and complete the full tutorial:
@@ -63,6 +88,8 @@ Choose a cloud provider to get started:
+Coming from Terraform? See [Pulumi for Terraform Users](/docs/iac/get-started/terraform/) to use Pulumi alongside your existing Terraform infrastructure. + ## Learn more The following sections are also useful when first learning how to use Pulumi: @@ -77,3 +104,5 @@ The following sections are also useful when first learning how to use Pulumi:

Learn how to support, migrate, or convert existing cloud infrastructure with Pulumi.

+ +Beyond IaC, the Pulumi platform also includes [Pulumi ESC](/docs/esc/get-started/) for centralized secrets and configuration and [Pulumi Deployments](/docs/deployments/get-started/) for git-driven deployment workflows. diff --git a/content/docs/get-started/connect-cloud.md b/content/docs/get-started/connect-cloud.md new file mode 100644 index 000000000000..240dd7692074 --- /dev/null +++ b/content/docs/get-started/connect-cloud.md @@ -0,0 +1,83 @@ +--- +title_tag: Connect Pulumi to Your Cloud Account +meta_desc: Pulumi uses your existing AWS, Azure, Google Cloud, or Kubernetes credentials — no separate credential system. Learn how to check and configure cloud access. +title: Connect Your Cloud Account +h1: Connect Your Cloud Account +menu: + get-started: + name: Connect Your Cloud Account + parent: get-started-home + weight: 2 + identifier: get-started-connect-cloud +--- + +Pulumi has no credential system of its own. It authenticates to your cloud the same way your cloud provider's own CLI and SDKs do — using the same environment variables, configuration files, and identity mechanisms. If your cloud provider's CLI already works on your machine, Pulumi already has everything it needs. + +## How Pulumi authenticates + +Each Pulumi provider uses the cloud vendor's official SDK and its standard credential chain, so any authentication method your cloud supports — CLI login, environment variables, instance profiles, workload identity — works with Pulumi unchanged. You can also set credentials explicitly for an individual [stack](/docs/iac/concepts/stacks/) using [provider configuration](/docs/iac/concepts/config/). + +For the full range of options per provider, see the setup pages for [AWS](/registry/packages/aws/installation-configuration/), [Azure](/registry/packages/azure-native/installation-configuration/), [Google Cloud](/registry/packages/gcp/installation-configuration/), and [Kubernetes](/registry/packages/kubernetes/installation-configuration/). + +## Check whether you're already connected + +Run your cloud's identity check. If it prints your account, identity, or cluster details, Pulumi can already manage resources there and you can continue straight to writing your program. + +| Cloud | Command | Success looks like | +| --- | --- | --- | +| AWS | `aws sts get-caller-identity` | Your user ID, account, and ARN are printed | +| Azure | `az account show` | Your subscription and tenant details are printed | +| Google Cloud | `gcloud config list` | Your active account and project are printed | +| Kubernetes | `kubectl cluster-info` | Your cluster's control plane address is printed | + +## Set up access for your cloud + +If the check above didn't succeed — or you'd like to review the details — each getting started guide has a configuration page for its cloud. These pages are part of the full tutorial flow, so the Previous and Next buttons on each page take you back to installing Pulumi or onward to creating and deploying your first project. + +
+ +
+ +## Best practice: short-lived credentials with Pulumi ESC + +Long-lived static keys are the most common source of credential leaks. [Pulumi ESC](/docs/esc/) can mint short-lived cloud credentials on demand via OpenID Connect (OIDC), so nothing sensitive lives on your workstation or in CI. See the ESC login providers for [AWS](/docs/esc/providers/login/aws-login/), [Azure](/docs/esc/providers/login/azure-login/), and [Google Cloud](/docs/esc/providers/login/gcp-login/). + +## Next steps + +1. Pick your cloud above and continue its getting started flow — configuration is step 3 of the tutorial. +1. New to Pulumi entirely? Start from the [getting started overview](/docs/get-started/). From ff3f937d555b36226813e92ad9852632fc6c446f Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 21 Jul 2026 19:51:53 +0000 Subject: [PATCH 2/2] Address review polish notes on connect-cloud page Reword the stepper description so it clearly refers to the per-cloud configure pages rather than this page, and drop the per-cloud "step 3" numbering from Next steps to avoid clashing with the overview's five-step model. Co-Authored-By: Claude --- content/docs/get-started/connect-cloud.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/docs/get-started/connect-cloud.md b/content/docs/get-started/connect-cloud.md index 240dd7692074..d52a31218c79 100644 --- a/content/docs/get-started/connect-cloud.md +++ b/content/docs/get-started/connect-cloud.md @@ -32,7 +32,7 @@ Run your cloud's identity check. If it prints your account, identity, or cluster ## Set up access for your cloud -If the check above didn't succeed — or you'd like to review the details — each getting started guide has a configuration page for its cloud. These pages are part of the full tutorial flow, so the Previous and Next buttons on each page take you back to installing Pulumi or onward to creating and deploying your first project. +If the check above didn't succeed — or you'd like to review the details — each getting started guide has a configuration page for its cloud. Each of those pages is part of its cloud's full tutorial flow, and its Previous and Next buttons take you back to installing Pulumi or onward to creating and deploying your first project.
@@ -79,5 +79,5 @@ Long-lived static keys are the most common source of credential leaks. [Pulumi E ## Next steps -1. Pick your cloud above and continue its getting started flow — configuration is step 3 of the tutorial. +1. Pick your cloud above to configure access, then continue that cloud's tutorial to create and deploy your first project. 1. New to Pulumi entirely? Start from the [getting started overview](/docs/get-started/).