From 4d92f84fe2d5766abccedcd71f82aa396699568a Mon Sep 17 00:00:00 2001 From: workprentice <257153108+workprentice@users.noreply.github.com> Date: Tue, 25 Aug 2026 12:26:16 +0000 Subject: [PATCH] docs: point internal links at final URLs, not redirecting ones Several blog posts and the pricing page link internally through URLs that now 301-redirect to a newer path (the get-started/download-install, guides/continuous-delivery, comparisons/cloud-template-transpilers, support/debugging, pulumi_stack_init, and product/pulumi-cloud migrations). Point every internal link at its final destination instead, so crawlers and readers reach the target in one hop. No sitemap or canonical changes were needed; both were already clean. Verified with the repo's markdown lint and prettier checks. --- content/blog/aws-cdk-on-pulumi-1.0/index.md | 2 +- .../better-cli-interactions-for-agents-and-humans/index.md | 4 ++-- .../blog/hidden-costs-of-infrastructure-management/index.md | 2 +- .../index.md | 2 +- content/blog/introducing-pulumi-registry/index.md | 2 +- .../index.md | 2 +- .../blog/mlops-huggingface-llm-aws-sagemaker-python/index.md | 2 +- content/blog/neo-automations/index.md | 2 +- content/blog/pulumi-cloud-dark-mode/index.md | 2 +- content/blog/pulumi-kubernetes-operator-and-kargo/index.md | 2 +- content/blog/pulumi-up-2024/index.md | 2 +- content/blog/registry-component-api-docs/index.md | 2 +- .../index.md | 2 +- content/blog/resource-search/index.md | 2 +- content/blog/stack-init-teams-flag/index.md | 2 +- .../blog/why-choose-pulumi-cloud-over-diy-backends/index.md | 2 +- .../iac/operations/stack-management/using-a-diy-backend.md | 2 +- content/pricing/_index.md | 2 +- 18 files changed, 19 insertions(+), 19 deletions(-) diff --git a/content/blog/aws-cdk-on-pulumi-1.0/index.md b/content/blog/aws-cdk-on-pulumi-1.0/index.md index 5f5d27ec1ac9..b97bb15f638f 100644 --- a/content/blog/aws-cdk-on-pulumi-1.0/index.md +++ b/content/blog/aws-cdk-on-pulumi-1.0/index.md @@ -199,7 +199,7 @@ Pulumi let's you read and create any resource type across thousands of different - Customize [resource options](https://www.pulumi.com/docs/iac/concepts/options/) (eg. to protect a database against accidental deletion or deploy to multiple regions in the same program) - [Detect and manage drift](https://www.pulumi.com/docs/pulumi-cloud/deployments/drift/) with Pulumi deployments - Track and store user actions and change history with [Audit Logs](https://www.pulumi.com/docs/pulumi-cloud/audit-logs/) -- And a host of other benefits from [Pulumi Cloud](https://www.pulumi.com/product/pulumi-cloud/) +- And a host of other benefits from [Pulumi Cloud](https://www.pulumi.com/product/) ## Expanded Features in pulumi-cdk 1.0 diff --git a/content/blog/better-cli-interactions-for-agents-and-humans/index.md b/content/blog/better-cli-interactions-for-agents-and-humans/index.md index c33e363a9c6a..46a3219a4922 100644 --- a/content/blog/better-cli-interactions-for-agents-and-humans/index.md +++ b/content/blog/better-cli-interactions-for-agents-and-humans/index.md @@ -25,7 +25,7 @@ social: AI agents do a lot of their work through CLIs. They're easier to call than HTTP APIs and they produce predictable output. Over the last few months our own CLI traffic has shifted from mostly people typing commands to people and agents running commands together, often in the same session. -Today we're shipping a release built for both. The [Pulumi CLI](/docs/iac/cli/) is reorganized around three ideas: the right command should be the one you can guess, anything you can do in [Pulumi Cloud](/product/pulumi-cloud/) should also be doable from the terminal, and what comes back should be just as readable to an agent as it is to a person. +Today we're shipping a release built for both. The [Pulumi CLI](/docs/iac/cli/) is reorganized around three ideas: the right command should be the one you can guess, anything you can do in [Pulumi Cloud](/product/) should also be doable from the terminal, and what comes back should be just as readable to an agent as it is to a person. @@ -297,4 +297,4 @@ More on how it works, and what you can do with it, in the days ahead. A lot of what makes a developer tool worth using is in the details, and most of what's in [this release](/releases/agentic-infrastructure-era/) is exactly that, across the whole CLI, with humans and agents in mind. -We'd love for you to [grab the latest release](/docs/get-started/download-install/) and give it a try. Tell us what's now easy, what's still hard, and what to fix next on [GitHub](https://github.com/pulumi/pulumi/issues) or in the [community Slack](https://slack.pulumi.com/). The fastest way the CLI gets better is feedback from the humans and agents who live in it. +We'd love for you to [grab the latest release](/docs/install/) and give it a try. Tell us what's now easy, what's still hard, and what to fix next on [GitHub](https://github.com/pulumi/pulumi/issues) or in the [community Slack](https://slack.pulumi.com/). The fastest way the CLI gets better is feedback from the humans and agents who live in it. diff --git a/content/blog/hidden-costs-of-infrastructure-management/index.md b/content/blog/hidden-costs-of-infrastructure-management/index.md index f75f4bb39f9e..7f54a3492e54 100644 --- a/content/blog/hidden-costs-of-infrastructure-management/index.md +++ b/content/blog/hidden-costs-of-infrastructure-management/index.md @@ -19,7 +19,7 @@ Note: This post discusses Pulumi Copilot, which Pulumi Neo has replaced. [Learn ## What is Pulumi Cloud? -Infrastructure as Code tools like Pulumi require systems for coordinating deployments, which include concurrency control, state management, and security. For the purposes of this post, let's refer to these systems as IaC backends. There are several options for managing these backends: you can either handle them yourself, which we'll call DIY, or you can leverage [Pulumi Cloud](/product/pulumi-cloud/), available as a SaaS or self-hosted solution. With Pulumi Cloud, you gain access to a comprehensive infrastructure management platform designed to handle everything running in the cloud. This platform automates your IaC deployments, centralizes [secrets management](/what-is/what-is-secrets-management/) and orchestration to manage secrets sprawl effectively, and employs AI to oversee infrastructure assets and ensure compliance. On the other hand, with a DIY approach, you have the flexibility to build everything Pulumi Cloud offers or opt for a more minimalistic setup tailored to your organization's specific needs. Both options are well-supported by Pulumi, but there are distinct advantages to choosing Pulumi Cloud over the DIY method, which we'll explore further. +Infrastructure as Code tools like Pulumi require systems for coordinating deployments, which include concurrency control, state management, and security. For the purposes of this post, let's refer to these systems as IaC backends. There are several options for managing these backends: you can either handle them yourself, which we'll call DIY, or you can leverage [Pulumi Cloud](/product/), available as a SaaS or self-hosted solution. With Pulumi Cloud, you gain access to a comprehensive infrastructure management platform designed to handle everything running in the cloud. This platform automates your IaC deployments, centralizes [secrets management](/what-is/what-is-secrets-management/) and orchestration to manage secrets sprawl effectively, and employs AI to oversee infrastructure assets and ensure compliance. On the other hand, with a DIY approach, you have the flexibility to build everything Pulumi Cloud offers or opt for a more minimalistic setup tailored to your organization's specific needs. Both options are well-supported by Pulumi, but there are distinct advantages to choosing Pulumi Cloud over the DIY method, which we'll explore further. ## Costs and Complexities of DIY Backends diff --git a/content/blog/iac-best-practices-implementing-rbac-and-security/index.md b/content/blog/iac-best-practices-implementing-rbac-and-security/index.md index c4757cdad430..50b62919cadf 100644 --- a/content/blog/iac-best-practices-implementing-rbac-and-security/index.md +++ b/content/blog/iac-best-practices-implementing-rbac-and-security/index.md @@ -30,7 +30,7 @@ So far, you've read about how Zephyr started out with a single project and a sin You can review the reasons for this structure in the post on [best practices for structuring Pulumi projects](/blog/iac-best-practices-structuring-pulumi-projects/). One of the reasons listed in the third Zephyr blog post was security: -> ...security is a factor that affects how projects and stacks should be structured. In Zephyr's case, the ability for one team to affect another team's resources was present when everything was a single project. With multiple projects, Zephyr can use stack permissions and role-based access control (RBAC) in [Pulumi Cloud](/product/pulumi-cloud/) to appropriately control _who_ can affect _what_. +> ...security is a factor that affects how projects and stacks should be structured. In Zephyr's case, the ability for one team to affect another team's resources was present when everything was a single project. With multiple projects, Zephyr can use stack permissions and role-based access control (RBAC) in [Pulumi Cloud](/product/) to appropriately control _who_ can affect _what_. The last part of that quote---the part about being able to "appropriately control _who_ can affect _what_"---is another way of describing what's known as [the principle of least privilege](https://en.wikipedia.org/wiki/Principle_of_least_privilege). If you're unfamiliar with this term, we recommend following the link and getting more information, because the principle of least privilege stands at the core of all the recommended practices you'll read in this post. diff --git a/content/blog/introducing-pulumi-registry/index.md b/content/blog/introducing-pulumi-registry/index.md index 556ed8c69a5d..aae2412a7fe3 100644 --- a/content/blog/introducing-pulumi-registry/index.md +++ b/content/blog/introducing-pulumi-registry/index.md @@ -27,7 +27,7 @@ We’re excited to enable any developer to take advantage of the power of these The modern cloud has put more power and more capability to delight customers in developers’ hands than ever before. In Azure, Amazon Web Services, and Google Cloud alone, there are more than 6,300 distinct services, each of which might be the service that gives your team, or your company, the competitive advantage you need to win in the marketplace. But, with all of this power comes cloud complexity: you need to pick the right service, configure it correctly and securely, and integrate it with all of your existing cloud infrastructure. -Pulumi Registry, an integral part of the [Pulumi Cloud Engineering Platform](/product/pulumi-cloud/), tames this complexity by bringing together everything you can do with the cloud into a single location. You can see all of our [Pulumi Packages](/product/packages/), including our Native Providers for the largest and most popular clouds; our broad range of Providers for various cloud, database, networking, monitoring, and other offerings; and all the Components that get you to production faster than ever before. You can easily filter packages by these categories or to find packages for your modern cloud use case, including Serverless, Containers, or Kubernetes. +Pulumi Registry, an integral part of the [Pulumi Cloud Engineering Platform](/product/), tames this complexity by bringing together everything you can do with the cloud into a single location. You can see all of our [Pulumi Packages](/product/packages/), including our Native Providers for the largest and most popular clouds; our broad range of Providers for various cloud, database, networking, monitoring, and other offerings; and all the Components that get you to production faster than ever before. You can easily filter packages by these categories or to find packages for your modern cloud use case, including Serverless, Containers, or Kubernetes. Once you find a package of interest, everything you need to know to build, deploy, and manage cloud infrastructure with that package is at your fingertips. If you’re using a package for the first time or using a service you haven’t used before, Pulumi Registry has tutorials and scenario-specific how-to guides to help you get started. If you want to jump right in, you can install the package–whether you need the NuGet package, the npm package, the Python package, or the Go module–right from Pulumi Registry. If you’re already familiar with the package and need the API reference, it’s only a click away. We’ve also taken this opportunity to make some improvements to the API documentation (which was previously hosted on pulumi.com/docs), like adding a left navigation and type-ahead filter so it’s easier to quickly find the resource or method you’re looking for. diff --git a/content/blog/maximize-speed-scale-savings-multi-cloud-platform/index.md b/content/blog/maximize-speed-scale-savings-multi-cloud-platform/index.md index cdaf0f375db2..27eef7ec5855 100644 --- a/content/blog/maximize-speed-scale-savings-multi-cloud-platform/index.md +++ b/content/blog/maximize-speed-scale-savings-multi-cloud-platform/index.md @@ -54,4 +54,4 @@ _"Pulumi lets us manage multi-cluster Kubernetes infrastructure efficiently, all _– Paul Hemberger, Engineering Manager for Materialize’s cloud team_ -Is your team ready to move from a self-managed environment to Pulumi cloud? Explore your options with [these resources](/product/pulumi-cloud/), and [enroll in our workshop](https://info.pulumi.com/pulumi-platform-engineering-immersion-days) series that’s customizable for your cloud and business environment. +Is your team ready to move from a self-managed environment to Pulumi cloud? Explore your options with [these resources](/product/), and [enroll in our workshop](https://info.pulumi.com/pulumi-platform-engineering-immersion-days) series that’s customizable for your cloud and business environment. diff --git a/content/blog/mlops-huggingface-llm-aws-sagemaker-python/index.md b/content/blog/mlops-huggingface-llm-aws-sagemaker-python/index.md index 205275289c72..52dffebcf1e6 100644 --- a/content/blog/mlops-huggingface-llm-aws-sagemaker-python/index.md +++ b/content/blog/mlops-huggingface-llm-aws-sagemaker-python/index.md @@ -35,7 +35,7 @@ category: tutorials [Amazon SageMaker Model Endpoint]:/registry/packages/aws/api-docs/SageMaker/model [CloudWatch alarms]:/registry/packages/aws/api-docs/cloudwatch/metricalarm [Pulumi project and stack]:/docs/using-pulumi/organizing-projects-stacks/ -[Pulumi Cloud]:https://www.pulumi.com/product/pulumi-cloud +[Pulumi Cloud]:https://www.pulumi.com/product/ [Pulumi state]:https://www.pulumi.com/docs/iac/concepts/state-and-backends [Python Virtual Environment]:/docs/languages-sdks/python/#virtual-environments [venv]:/docs/languages-sdks/python/#virtual-environments diff --git a/content/blog/neo-automations/index.md b/content/blog/neo-automations/index.md index 8ccfc42db3f4..e6012a25e857 100644 --- a/content/blog/neo-automations/index.md +++ b/content/blog/neo-automations/index.md @@ -60,7 +60,7 @@ A scheduled task uses the same context as an interactive Neo task. [Custom Instr ## Try it out -Open Neo in [Pulumi Cloud](/product/pulumi-cloud/), switch to the **Automations** tab, and pick a template or write your own prompt. The [automations docs](/docs/ai/neo/automations/) cover the form, scheduling options, and per-automation overrides. +Open Neo in [Pulumi Cloud](/product/), switch to the **Automations** tab, and pick a template or write your own prompt. The [automations docs](/docs/ai/neo/automations/) cover the form, scheduling options, and per-automation overrides. ![Setting up a scheduled task for Pulumi Neo](/blog/neo-automations/neo-freshness.check.png) diff --git a/content/blog/pulumi-cloud-dark-mode/index.md b/content/blog/pulumi-cloud-dark-mode/index.md index 9a863d08fef1..416592a5cad3 100644 --- a/content/blog/pulumi-cloud-dark-mode/index.md +++ b/content/blog/pulumi-cloud-dark-mode/index.md @@ -19,7 +19,7 @@ tags: category: product --- -[Pulumi Cloud](/product/pulumi-cloud/) helps teams manage and operate their cloud infrastructure in one place, from state and secrets to deployments, visibility, and policy enforcement. +[Pulumi Cloud](/product/) helps teams manage and operate their cloud infrastructure in one place, from state and secrets to deployments, visibility, and policy enforcement. For a long time, one request has consistently come up from the Pulumi community: dark mode. Today, we’re announcing that this request is now available in Pulumi Cloud. diff --git a/content/blog/pulumi-kubernetes-operator-and-kargo/index.md b/content/blog/pulumi-kubernetes-operator-and-kargo/index.md index b2b86beb0c84..158b2a2eac3e 100644 --- a/content/blog/pulumi-kubernetes-operator-and-kargo/index.md +++ b/content/blog/pulumi-kubernetes-operator-and-kargo/index.md @@ -13,7 +13,7 @@ summary: | The Pulumi Kubernetes Operator (PKO) manages Pulumi stacks as Kubernetes resources, while Kargo provides controlled promotion of changes across environments. Used together, they let you manage infrastructure as code with Pulumi while systematically testing and promoting changes through dev, staging, and production environments. --- -The [Pulumi Kubernetes Operator (PKO)](https://www.pulumi.com/docs/iac/guides/continuous-delivery/pulumi-kubernetes-operator/) enables you to manage Pulumi stacks as Kubernetes resources, but it doesn't provide much guidance on change management. [Kargo](https://kargo.io/) fills this gap by providing controlled, staged promotions with verification steps. Together, they let you keep your infrastructure defined in Pulumi while managing multi-environment rollouts in a systematic way. +The [Pulumi Kubernetes Operator (PKO)](https://www.pulumi.com/docs/integrations/clouds/kubernetes/pulumi-kubernetes-operator/) enables you to manage Pulumi stacks as Kubernetes resources, but it doesn't provide much guidance on change management. [Kargo](https://kargo.io/) fills this gap by providing controlled, staged promotions with verification steps. Together, they let you keep your infrastructure defined in Pulumi while managing multi-environment rollouts in a systematic way. This pattern is especially useful for platform teams that need to balance delivery speed with governance as environments and expectations scale. diff --git a/content/blog/pulumi-up-2024/index.md b/content/blog/pulumi-up-2024/index.md index 185689f3a7c3..de6dd4f3fb3d 100644 --- a/content/blog/pulumi-up-2024/index.md +++ b/content/blog/pulumi-up-2024/index.md @@ -30,7 +30,7 @@ In addition to our three products, Pulumi’s platform incorporates three core c You can see this visually depicted here: -[![Pulumi Platform](platform.png)](/product/pulumi-cloud) +[![Pulumi Platform](platform.png)](/product/) We’ve now worked with 3,000 customers to help with their cloud journey and have listened to and solved the problems we regularly hear about. That includes Nvidia who is at the forefront of the AI revolution as well as [BMW](/case-studies/bmw/) who is reimagining their entire engineering mindset in a cloud-first world, both leveraging Pulumi. [Unity Games](/case-studies/unity/) now ships **5x faster** from code to cloud, and Tivity Health **saved 71%** of their cloud spend, automating everything and saving $6.5M annually. diff --git a/content/blog/registry-component-api-docs/index.md b/content/blog/registry-component-api-docs/index.md index fba17e5423de..22b873350149 100644 --- a/content/blog/registry-component-api-docs/index.md +++ b/content/blog/registry-component-api-docs/index.md @@ -79,7 +79,7 @@ This dramatically reduces the time from component discovery to successful deploy ## Getting Started -Automatic API docs are available today for all [Pulumi Cloud](/product/pulumi-cloud/) customers with access to private registry. To start generating docs, simply [publish your component](/docs/idp/concepts/private-registry/#publishing-components). Documentation generation happens automatically with no configuration required, and docs will automatically appear for existing components. +Automatic API docs are available today for all [Pulumi Cloud](/product/) customers with access to private registry. To start generating docs, simply [publish your component](/docs/idp/concepts/private-registry/#publishing-components). Documentation generation happens automatically with no configuration required, and docs will automatically appear for existing components. ## Looking Ahead diff --git a/content/blog/replicating-data-to-support-multi-region-applications/index.md b/content/blog/replicating-data-to-support-multi-region-applications/index.md index af5a633d6189..4995cf5a23cc 100644 --- a/content/blog/replicating-data-to-support-multi-region-applications/index.md +++ b/content/blog/replicating-data-to-support-multi-region-applications/index.md @@ -214,4 +214,4 @@ Understanding these trade-offs is crucial for designing resilient systems. It al Data replication is important for ensuring the resilience and performance of stateful distributed services. This article not only emphasized the significance of data replication in distributed systems, but it also demonstrated how Pulumi, in collaboration with Azure, enables developers to architect and manage resilient, performant, and globally distributed infrastructures for their stateful applications. As cloud-native architectures expand, the importance of infrastructure as code (IaC) in ensuring optimal data replication outcomes becomes increasingly important, and Pulumi can be used to provision the infrastructure required. -Did you learn something new? We’d like to know. If you’d like to try this out for yourself, you can get started with Pulumi Cloud [here](/product/pulumi-cloud/). You can also join our community to be a part of the continuous conversation, and we can’t wait to see what you build! +Did you learn something new? We’d like to know. If you’d like to try this out for yourself, you can get started with Pulumi Cloud [here](/product/). You can also join our community to be a part of the continuous conversation, and we can’t wait to see what you build! diff --git a/content/blog/resource-search/index.md b/content/blog/resource-search/index.md index 6f1b2ec75a69..1701797c58f3 100644 --- a/content/blog/resource-search/index.md +++ b/content/blog/resource-search/index.md @@ -38,7 +38,7 @@ category: product # and please remove these comments before submitting for review. --- -Last month we announced a new [Pulumi Cloud](/product/pulumi-cloud/) feature available for everyone: Resource Search. In the past month, Resource Search has been the fastest adopted feature since launching Pulumi Cloud, with thousands of users leveraging the feature to find resources across cloud environments, projects, stacks, teams, and users. Today we are announcing two new improvements to Resource Search: advanced filtering and Pulumi Teams support. +Last month we announced a new [Pulumi Cloud](/product/) feature available for everyone: Resource Search. In the past month, Resource Search has been the fastest adopted feature since launching Pulumi Cloud, with thousands of users leveraging the feature to find resources across cloud environments, projects, stacks, teams, and users. Today we are announcing two new improvements to Resource Search: advanced filtering and Pulumi Teams support. ## Introduction to Resource Search diff --git a/content/blog/stack-init-teams-flag/index.md b/content/blog/stack-init-teams-flag/index.md index 8054b885f28f..24e5ef79fe62 100644 --- a/content/blog/stack-init-teams-flag/index.md +++ b/content/blog/stack-init-teams-flag/index.md @@ -22,7 +22,7 @@ consist of stacks, which are separate deployments of the same infrastructure. St also be configured with separate inputs. Organization admins can leverage RBAC to grant access permissions at the organization or Pulumi Teams levels. Pulumi Teams and RBAC are available for Enterprise and Business Critical customers. -Stacks are often created via the CLI with the [`pulumi stack init` command](https://www.pulumi.com/docs/iac/cli/commands/pulumi_stack_init/#options). +Stacks are often created via the CLI with the [`pulumi stack init` command](https://www.pulumi.com/docs/iac/cli/commands/pulumi_stack_new/#options). This command initializes a new stack. If you're using the [Pulumi Service](https://www.pulumi.com/docs/iac/concepts/state-and-backends/#pulumi-service-backend) as your backend, you can view your newly created stack in the Pulumi Service console. If your organization uses teams, you will want to give your teammates access to the stack. diff --git a/content/blog/why-choose-pulumi-cloud-over-diy-backends/index.md b/content/blog/why-choose-pulumi-cloud-over-diy-backends/index.md index 2faa6ccc452b..9ce6822632d6 100644 --- a/content/blog/why-choose-pulumi-cloud-over-diy-backends/index.md +++ b/content/blog/why-choose-pulumi-cloud-over-diy-backends/index.md @@ -21,7 +21,7 @@ Many companies are building internal developer platforms or modern infrastructur At Pulumi, we’re committed to open source—always have been; always will be. Pulumi IaC is [entirely open source](https://github.com/pulumi/pulumi) (Apache 2.0 license), meaning you can adopt and extend it however you like. If you’re new to Pulumi, the open source edition is an excellent way to start modernizing your infrastructure. But as your organization grows and the complexity of your environment increases, you may find yourself devoting significant time to rolling your own enterprise IaC backend features. -That’s why we built [Pulumi Cloud](/product/pulumi-cloud/)—to help you avoid building and maintaining these capabilities from scratch while ensuring you can automate, secure, and manage your infrastructure at scale. Pulumi Cloud provides enterprise capabilities that make it easier to build modern infrastructure platforms. Companies receive increasing value from Pulumi Cloud as their organization and their infrastructure platforms grow in size and complexity. +That’s why we built [Pulumi Cloud](/product/)—to help you avoid building and maintaining these capabilities from scratch while ensuring you can automate, secure, and manage your infrastructure at scale. Pulumi Cloud provides enterprise capabilities that make it easier to build modern infrastructure platforms. Companies receive increasing value from Pulumi Cloud as their organization and their infrastructure platforms grow in size and complexity. As companies expand or [platform engineering](/what-is/what-is-platform-engineering/) mandates become more expansive, challenges arise around collaboration, security, governance, and scaling. Some questions that need answering include: diff --git a/content/docs/iac/operations/stack-management/using-a-diy-backend.md b/content/docs/iac/operations/stack-management/using-a-diy-backend.md index 76c1f4114406..9c503c7cf67f 100644 --- a/content/docs/iac/operations/stack-management/using-a-diy-backend.md +++ b/content/docs/iac/operations/stack-management/using-a-diy-backend.md @@ -200,4 +200,4 @@ error: read ".pulumi\\meta.yaml": blob (key ".pulumi/meta.yaml") (code=Unknown): - **Missing region configuration (AWS S3).** The AWS SDK can't determine which region the bucket is in. Specify the region in the backend URL—for example, `pulumi login 's3://?region=us-east-1'`—or set the `AWS_REGION` environment variable before logging in. - **Missing authentication environment variables.** DIY backends authenticate using the cloud provider's own SDK. Verify that the variables that SDK expects are set—see the section for your backend ([AWS S3](#aws-s3), [Azure Blob Storage](#azure-blob-storage), or [Google Cloud Storage](#google-cloud-storage)) above for the specifics. -To get more detail while diagnosing the problem, re-run the command with [CLI verbose logging](/docs/support/debugging/logging/#cli-verbose-logging) enabled. +To get more detail while diagnosing the problem, re-run the command with [CLI verbose logging](/docs/iac/operations/debugging/logging/#cli-verbose-logging) enabled. diff --git a/content/pricing/_index.md b/content/pricing/_index.md index 22386ae7728f..2a76655cfbcd 100644 --- a/content/pricing/_index.md +++ b/content/pricing/_index.md @@ -114,7 +114,7 @@ faq: items: - question: What are Pulumi open source and Pulumi Cloud? answer: | - Pulumi's Infrastructure as Code CLI and SDK are an open-source project that is supported by an active community. [Pulumi Cloud](/product/pulumi-cloud/) is a managed service for the open source CLI and SDK. It tracks your infrastructure’s state and coordinates updates with the CLI, which creates or updates resources to reach your infrastructure’s desired state. It also manages secrets, supports SAML SSO, integrates with CI/CD pipelines, enforces compliance rules, and much more. + Pulumi's Infrastructure as Code CLI and SDK are an open-source project that is supported by an active community. [Pulumi Cloud](/product/) is a managed service for the open source CLI and SDK. It tracks your infrastructure’s state and coordinates updates with the CLI, which creates or updates resources to reach your infrastructure’s desired state. It also manages secrets, supports SAML SSO, integrates with CI/CD pipelines, enforces compliance rules, and much more. You're not required to use Pulumi Cloud. You can use any cloud or on-premises storage to build and run your own backend. - question: Can I use Pulumi for free?