fix (more) broken links (#15531)

* fix broken links

* minor fixes

* a few more external link fixes

Author: thoward

content/blog/announcing-public-preview-update-plans/index.md

@@ -12,7 +12,7 @@ canonical_url: "https://www.pulumi.com/docs/iac/concepts/update-plans/"
 ---
 
 > [!INFO]
-> Update Plans are now generally available and no longer require the `PULUMI_EXPERIMENTAL` environment variable. For the most up-to-date information about using Update Plans, please see the [Update Plans documentation](/docs/cli/commands/pulumi-preview#save-a-plan-file).
+> Update Plans are now generally available and no longer require the `PULUMI_EXPERIMENTAL` environment variable. For the most up-to-date information about using Update Plans, please see the [Update Plans documentation](/docs/cli/commands/pulumi_preview#save-a-plan-file).
 
 Pulumi’s previews are an important part of any workflow where you want to see the changes that will be made to your infrastructure before actually making the changes (with `pulumi up`). However, today there is no guarantee that the `pulumi up` operation will do only what was previewed; if the program, or your infrastructure, changes between the preview and the update, the update might make additional changes to bring your infrastructure back in line with what’s defined in your program. We’ve [heard from many of you](https://github.com/pulumi/pulumi/issues/2318) that you need a strong guarantee about exactly which changes an update will make to your infrastructure, especially in critical and production environments.
 

content/blog/announcing-pulumi-esc-github-action/index.md

@@ -72,7 +72,7 @@ jobs:
 
 The GitHub Action workflow above does the following:
 
-1.	Authenticate with Pulumi Cloud using pulumi/auth-actions. Instead of storing a permanent token, we use a [short-lived token to authenticate with Pulumi Cloud](https://www.pulumi.com/docs/pulumi-cloud/access-management/oidc/client/github/).
+1.	Authenticate with Pulumi Cloud using pulumi/auth-actions. Instead of storing a permanent token, we use a [short-lived token to authenticate with Pulumi Cloud](https://www.pulumi.com/docs/pulumi-cloud/access-management/oidc-client/github/).
 2.	Inject the environment variables from `tinyco/someProject/myEnv` into the current GitHub Actions environment, making them accessible to subsequent steps in the workflow.
 
 ## What’s Next?

content/blog/building-and-publishing-docker-images-to-a-private-amazon-ecr-repository/index.md

@@ -23,7 +23,7 @@ need to operate your own container repositories or worry about scaling
 the underlying infrastructure. ECR hosts your images in a highly
 available and scalable architecture, allowing you to reliably deploy
 containers for your applications. In this article, we'll see how
-[Pulumi Crosswalk for AWS](/crosswalk/aws/) lets you use
+[Pulumi Crosswalk for AWS](/docs/iac/clouds/aws/guides/) lets you use
 infrastructure as code to easily build, publish, and pull from private
 ECR repositories.
 <!--more-->
@@ -208,7 +208,7 @@ manually going and cleaning up the stale garbage in the future.
 
 ## Next Steps
 
-We've shown how [Pulumi Crosswalk for AWS](/crosswalk/aws/)
+We've shown how [Pulumi Crosswalk for AWS](/docs/iac/clouds/aws/guides/)
 can create a tight developer inner
 loop for building, publishing, and consuming Docker images, using
 private ECR repositories, while keeping all your ECS or EKS services and

content/blog/cloud-engineering-fuels-startup-innovation/index.md

@@ -87,7 +87,7 @@ Fauna provides a flexible, developer-friendly, transactional database delivered
 - Increased the reliability and quality of infrastructure using existing code review processes and running unit tests.
 - Controlled access to its infrastructure using Pulumi’s SSO integration with its identity provider service.
 
-[Read Fauna's blog post→](https://fauna.com/blog/building-faunas-gdpr-compliant-distributed-and-scalable-database)
+[Read Fauna's blog post→](https://web.archive.org/web/20250516064352/https://fauna.com/blog/building-faunas-gdpr-compliant-distributed-and-scalable-database)
 
 ## Summary
 

content/blog/codegen-learnings/index.md

@@ -112,7 +112,7 @@ Semantic search is based on the conceptual similarity of the term you're looking
 
 A common way to determine the similarity between the two strings is to first turn these strings into _vector embeddings_ - arrays of floating point values representing the semantic meaning of each string - and then calculate the _cosine similarity_ between the two vectors, which is the cosine of the angle between the vectors. [Various methods](https://huggingface.co/blog/matryoshka) of producing vector embeddings are fascinating but we will not cover them here in depth.
 
-For Pulumi code generation we are using the OpenAI's [Ada-002 embedding model](https://medium.com/@siladityaghosh/a-deep-dive-into-openais-text-embedding-ada-002-the-power-of-semantic-understanding-7072c0386f83) which at this moment represents a good balance between performance and cost.
+For Pulumi code generation we are using the OpenAI's [Ada-002 embedding model](https://www.downelink.com/a-deep-dive-into-openais-text-embedding-ada-002-unlocking-the-power-of-semantic-understanding/) which at this moment represents a good balance between performance and cost.
 
 Producing vector embeddings from the user query is the standard approach in this situation. However, for Pulumi code generator we added a little twist - to increase the odds of getting more relevant information from the Registry (i.e. to increase the recall) we first make an LLM call to generate a small set of relevant search terms that will produce an array of vector embeddings.
 

content/blog/delivering-cloud-native-infrastructure-as-code-a-pulumi-white-paper/index.md

@@ -26,7 +26,7 @@ technology generation, and even by cloud vendor, and so deny the full
 potential of cloud native application delivery.
 
 In our latest white paper,
-[Delivering Cloud Native Infrastructure as Code](/whitepapers/delivering-cloud-native-infrastructure-as-code/),
+[Delivering Cloud Native Infrastructure as Code](./Pulumi-Delivering-CNI-as-Code.pdf),
 we make the case for a consistent programming model for the cloud and examine:
 
 - How the cloud has already evolved three times as it increasingly
@@ -40,7 +40,6 @@ we make the case for a consistent programming model for the cloud and examine:
   development and operations functions, and does not satisfy the need
   for increasing delivery speed in the cloud.
 
-You can read the paper in full [here](/whitepapers/delivering-cloud-native-infrastructure-as-code/),
-or download a copy [here](./Pulumi-Delivering-CNI-as-Code.pdf).
+You can read the paper in full [here](./Pulumi-Delivering-CNI-as-Code.pdf).
 
 Let us know what you think!

content/blog/deploying-netlify-cms-on-aws/index.md

@@ -51,7 +51,7 @@ Simplifying the file and deleting unneeded parameters produces this:
 
 ![File Structure](./file-structure.jpg)
 
-The `./src/index.js` file is the entry point for React to create the App class inside `./public/index.html`'s  `<div id=root>`. `App` (defined in `./src/App.js`) is a React Component that returns the `NetlifyCMS` React component defined inside `./src/components/NetlifyCMS/index.js`. We can also specify the [custom preview](https://docs.netlify.com/create/cloud-project/previewing/) and [custom widget](https://docs.netlify.com/) for the CMS app in this file.
+The `./src/index.js` file is the entry point for React to create the App class inside `./public/index.html`'s  `<div id=root>`. `App` (defined in `./src/App.js`) is a React Component that returns the `NetlifyCMS` React component defined inside `./src/components/NetlifyCMS/index.js`. We can also specify the [custom preview](https://docs.netlify.com/manage/visual-editor/cloud-setup/previewing/) and [custom widget](https://docs.netlify.com/) for the CMS app in this file.
 
 To preview the CMS app content, run `yarn start`.
 

content/blog/esc-projects-environment-tags-launch/index.md

@@ -20,7 +20,7 @@ We're thrilled to unveil two new features that will empower you to organize your
 
 ## Overview of Pulumi ESC 
 
-Pulumi ESC is a developer-first platform designed to simplify the management of secrets and configurations into collections called <i>[environments](/docs/esc/environments/)</i>. As a fully managed solution, it offers [dynamic cloud provider credential](/docs/esc/get-started/esc-run-command/) resolution, a rich set of [providers](/docs/esc/providers/) to retrieve secrets from external platforms, and the ability to use the secrets and configurations you have defined across any surface, including your applications and infrastructure via [Multi-language SDKs](/docs/esc/sdk/), [REST APIs](/docs/pulumi-cloud/cloud-rest-api/#environments), [CLI](/docs/esc-cli/), [Pulumi-Service Provider](/registry/packages/pulumiservice/api-docs/environment/), and [Automation API](/blog/esc-automation-api-pulumi-service-provider-launch/#streamline-automated-workflows-with-automation-api-enhancements). Like all Pulumi functionality, Pulumi ESC focuses on enhancing both agility and security in modern cloud development.
+Pulumi ESC is a developer-first platform designed to simplify the management of secrets and configurations into collections called <i>[environments](/docs/esc/environments/)</i>. As a fully managed solution, it offers [dynamic cloud provider credential](/docs/esc/integrations/dynamic-login-credentials/) resolution, a rich set of [providers](/docs/esc/providers/) to retrieve secrets from external platforms, and the ability to use the secrets and configurations you have defined across any surface, including your applications and infrastructure via [Multi-language SDKs](/docs/esc/sdk/), [REST APIs](/docs/pulumi-cloud/cloud-rest-api/#environments), [CLI](/docs/esc-cli/), [Pulumi-Service Provider](/registry/packages/pulumiservice/api-docs/environment/), and [Automation API](/blog/esc-automation-api-pulumi-service-provider-launch/#streamline-automated-workflows-with-automation-api-enhancements). Like all Pulumi functionality, Pulumi ESC focuses on enhancing both agility and security in modern cloud development.
 
 As developers have embraced Pulumi ESC to manage their collections of secrets and configurations across many teams and projects, the demand for more sophisticated organizational tools has increased. To address this growing need for more organized and efficient management of cloud environments, we are introducing Projects and Environment Tags in Pulumi ESC.
 

content/blog/future-of-cloud-engineering/index.md

@@ -9,7 +9,7 @@ tags:
     - cloud engineering
 ---
 
-All software is cloud software. All modern applications interact with the cloud in some way, whether it's using cloud for storage, compute capabilities, or with rich cloud services for data, AI/ML, and so much more, to deliver amazing new experiences. As a result, all developers today are cloud developers, and infrastructure teams are key to enabling innovation across the entire organization. I had a great time telling this story at the [Cloud Engineering Summit](https://cloudengineeringsummit.com) today and wanted to take a moment to put pen to paper.
+All software is cloud software. All modern applications interact with the cloud in some way, whether it's using cloud for storage, compute capabilities, or with rich cloud services for data, AI/ML, and so much more, to deliver amazing new experiences. As a result, all developers today are cloud developers, and infrastructure teams are key to enabling innovation across the entire organization. I had a great time telling this story at the [Cloud Engineering Summit](https://www.youtube.com/playlist?list=PLyy8Vx2ZoWlodkVaCTO3Y-3vya68J2c6y) today and wanted to take a moment to put pen to paper.
 
 <!--more-->
 
@@ -95,7 +95,7 @@ Despite the clear gaps, it is clear we've taken some major steps in the directio
 
 As we've seen, the future of cloud engineering is already here in a very real way. The cloud is being infused into application development, we are increasingly treating cloud infrastructure as software, and teams are embracing new ways of working together.
 
-We hope you enjoyed learning more about cloud engineering architectures, workflows, and teams. [Watch the Cloud Engineering Summit Keynote here](https://cloudengineeringsummit.com/talks/welcome-keynote/) or check out [one of the many amazing Cloud Engineering talks now](https://cloudengineeringsummit.com/schedule/)!
+We hope you enjoyed learning more about cloud engineering architectures, workflows, and teams. [Watch the Cloud Engineering Summit Keynote here](https://www.youtube.com/watch?v=w6Dj2zf-39M&list=PLyy8Vx2ZoWlodkVaCTO3Y-3vya68J2c6y&index=2) or check out [one of the many amazing Cloud Engineering talks now](hhttps://www.youtube.com/playlist?list=PLyy8Vx2ZoWlodkVaCTO3Y-3vya68J2c6y)!
 
 This event would not have been possible without the participation and support of our top sponsors:
 

content/blog/getting-started-with-pac/index.md

@@ -162,7 +162,7 @@ Policy Packs run:
 Permalink: https://app.pulumi.com/spara/elasticsearch/dev/previews/bb6df58f-69aa-485a-99a4-d076bc067b84
 ```
 
-AWSGuard flagged two recommended Elasticsearch best practices, encryption and deploying only within a VPC and not publically. By enabling encryption at rest, unauthorized users cannot read data in Elasticseach clusters, storage, indices, and log files. By enabling Elasticsearch’s built-in encryption, your deployment follows recommended practices that comply with [HIPAA](https://aspe.hhs.gov/report/health-insurance-portability-and-accountability-act-1996) and [GDPR](https://gdprinfo.eu/). AWS VPCs can keep the network traffic between your applications and Elasticsearch cluster within your infrastructure’s network and not over the public internet. Isolating Elasticsearch within your infrastructure can help mitigate the likelihood of data exposure.
+AWSGuard flagged two recommended Elasticsearch best practices, encryption and deploying only within a VPC and not publically. By enabling encryption at rest, unauthorized users cannot read data in Elasticseach clusters, storage, indices, and log files. By enabling Elasticsearch’s built-in encryption, your deployment follows recommended practices that comply with [HIPAA](https://aspe.hhs.gov/reports/health-insurance-portability-accountability-act-1996) and [GDPR](https://gdprinfo.eu/). AWS VPCs can keep the network traffic between your applications and Elasticsearch cluster within your infrastructure’s network and not over the public internet. Isolating Elasticsearch within your infrastructure can help mitigate the likelihood of data exposure.
 
 ## CrossGuard available in Pulumi 2.0