broken links

Author: davemooreuws

docs/get-started/foundations/deployment/index.mdx

@@ -17,7 +17,7 @@ You can read about why this separation is important on the [why nitric](/get-sta
 
 ## Providers
 
-The plugins used to deploy your application to a specific target platform are called [providers](/reference/providers). Typically providers do one of two things:
+The plugins used to deploy your application to a specific target platform are called [providers](/providers). Typically providers do one of two things:
 
 1. **Deploy your application directly**
 2. **Generate Infrastructure-as-Code**
@@ -36,9 +36,9 @@ Nitric ships with five official providers. The first three are direct deployment
 
 All of the direct deployment providers use [Pulumi](https://pulumi.com) under the hood for their deployments, so Pulumi will need to be configured to persist your stack state and to run the deployment to the cloud of your choice.
 
-- [AWS](/reference/providers/aws)
-- [Google Cloud](/reference/providers/gcp)
-- [Azure](/reference/providers/azure)
+- [AWS](/providers/pulumi/aws)
+- [Google Cloud](/providers/pulumi/gcp)
+- [Azure](/providers/pulumi/azure)
 
 <Note>
   If you're new to Nitric we recommend starting with one of the direct
@@ -49,16 +49,16 @@ All of the direct deployment providers use [Pulumi](https://pulumi.com) under th
 
 All of the IaC providers generate Terraform code for deployment. This allows you to use Nitric's deployment automation and still leverage your existing Terraform workflows.
 
-- [AWSTF](/reference/providers/awstf)
-- [GCPTF](/reference/providers/gcptf)
+- [AWSTF](/providers/terraform/aws)
+- [GCPTF](/providers/terraform/gcp)
 
 <Note>An Azure Terraform provider is in development.</Note>
 
 These providers are also a good starting point for customization when you have existing Terraform Modules or workflows you want to integrate with Nitric.
 
 ## Custom Providers
 
-If you have a specific cloud service, deployment workflow or tooling you want to use, you can build a [custom provider](/reference/providers/custom). Custom providers allow you to target the host you prefer with your own tools and configuration.
+If you have a specific cloud service, deployment workflow or tooling you want to use, you can build a [custom provider](/providers/custom). Custom providers allow you to target the host you prefer with your own tools and configuration.
 
 You can also extend the existing providers to change which cloud services are used to fulfill the Nitric resource contracts, to add configuration options or to change the deployment process.
 
@@ -118,7 +118,7 @@ Stack files define the deployment plugin (provider), any additional configuratio
 
 The common configuration option available in all stack files is the `provider` field, which specifies the provider plugin to use for the deployment. The standard format for specifying a provider is `[namespace]/[provider]@[version]`. The `namespace` for all standard providers is `nitric`. The `provider` is the name of the provider plugin, and the `version` is the version of the provider plugin to use.
 
-There is another format for specifying providers as a container image `docker://[image]`, which you can read about in the [reference docs](/reference/providers/custom/docker).
+There is another format for specifying providers as a container image `docker://[image]`, which you can read about in the [reference docs](/providers/custom/docker).
 
 Here is a basic example, using the standard nitric AWS provider `nitric/[email protected]`.
 
@@ -127,11 +127,11 @@ provider: nitric/[email protected]
 region: us-east-1
 ```
 
-Provider specific stack configuration, including advanced configuration options, can be viewed in the reference docs for each [provider](/reference/providers).
+Provider specific stack configuration, including advanced configuration options, can be viewed in the reference docs for each [provider](/providers).
 
-- [AWS stack configuration](/reference/providers/aws/configuration)
-- [Azure stack configuration](/reference/providers/azure/configuration)
-- [GCP stack configuration](/reference/providers/gcp/configuration)
+- [AWS stack configuration](/providers/pulumi/aws/configuration)
+- [Azure stack configuration](/providers/pulumi/azure/configuration)
+- [GCP stack configuration](/providers/pulumi/gcp/configuration)
 
 <Note>
   If you create a custom provider you're able define the options available in

docs/get-started/foundations/infrastructure/index.mdx

@@ -342,9 +342,8 @@ provider: your_namespace/[email protected]
   The runtime code for cloud services like SNS still exists, it's just isolated
   to an independent module. It could be from a [Nitric
   provider](https://github.com/nitrictech/nitric/blob/main/cloud/aws/runtime/topic/sns.go)
-  or [something custom](/reference/providers/custom/building-custom-provider)
-  built by you or an independent team, such as platform engineers or DevOps
-  teams.
+  or [something custom](/providers/custom/create) built by you or an independent
+  team, such as platform engineers or DevOps teams.
 </Note>
 
 ---

docs/get-started/quickstart.mdx

@@ -415,9 +415,9 @@ Now that you've implemented a basic API and tested that it works, you can deploy
 
 The first step is to set up your credentials for the cloud provider.
 
-- [AWS](/reference/providers/aws)
-- [Azure](/reference/providers/azure)
-- [GCP](/reference/providers/gcp)
+- [AWS](/providers/pulumi/aws)
+- [Azure](/providers/pulumi/azure)
+- [GCP](/providers/pulumi/gcp)
 
 You'll then need to create a [stack](/reference/cli#stacks) that represents your project and a deployment target.
 

docs/guides/dart/serverless-rest-api-example.mdx

@@ -258,9 +258,9 @@ curl --location --request DELETE 'http://localhost:4001/profiles/[id]'
 
 At this point, you can deploy the application to any supported cloud provider. Start by setting up your credentials and any configuration for the cloud you prefer:
 
-- [AWS](/reference/providers/aws)
-- [Azure](/reference/providers/azure)
-- [Google Cloud](/reference/providers/gcp)
+- [AWS](/providers/pulumi/aws)
+- [Azure](/providers/pulumi/azure)
+- [Google Cloud](/providers/pulumi/gcp)
 
 Next, we'll need to create a `stack`. Stacks represent deployed instances of an application, including the target provider and other details such as the deployment region. You'll usually define separate stacks for each environment such as development, testing and production. For now, let's start by creating a `dev` stack.
 

docs/guides/go/serverless-rest-api-example.mdx

@@ -245,9 +245,9 @@ curl --location --request DELETE 'http://localhost:4001/profiles/[id]'
 
 At this point, you can deploy what you've built to any of the supported cloud providers. To do this start by setting up your credentials and any configuration for the cloud you prefer:
 
-- [AWS](/reference/providers/aws)
-- [Azure](/reference/providers/azure)
-- [GCP](/reference/providers/gcp)
+- [AWS](/providers/pulumi/aws)
+- [Azure](/providers/pulumi/azure)
+- [GCP](/providers/pulumi/gcp)
 
 Next, we'll need to create a `stack`. A stack represents a deployed instance of an application, which is a key value store of resources defined in your project. You might want separate stacks for each environment, such as stacks for `dev`, `test` and `prod`. For now, let's start by creating a `dev` stack.
 

docs/guides/jvm/serverless-rest-api-example.mdx

@@ -187,10 +187,10 @@ Here we're creating an API named `public` and collection named `profiles`, then
 <Note>
   Resources in Nitric like `api` and `collection` represent high-level cloud
   resources. When your app is deployed Nitric automatically converts these
-  requests into appropriate resources for the specific
-  [provider](/reference/providers). Nitric also takes care of adding the IAM
-  roles, policies, etc. that grant the requested access. For example the
-  `collection` resource uses DynamoDB in AWS or FireStore on Google Cloud.
+  requests into appropriate resources for the specific [provider](/providers).
+  Nitric also takes care of adding the IAM roles, policies, etc. that grant the
+  requested access. For example the `collection` resource uses DynamoDB in AWS
+  or FireStore on Google Cloud.
 </Note>
 
 ### Create profiles with POST
@@ -430,9 +430,9 @@ curl --location --request DELETE 'http://localhost:4001/profiles/[id]'
 
 At this point, you can deploy the application to any supported cloud provider. Start by setting up your credentials and any configuration for the cloud you prefer:
 
-- [AWS](/reference/providers/aws)
-- [Azure](/reference/providers/azure)
-- [Google Cloud](/reference/providers/gcp)
+- [AWS](/providers/pulumi/aws)
+- [Azure](/providers/pulumi/azure)
+- [Google Cloud](/providers/pulumi/gcp)
 
 Next, we'll need to create a `stack`. Stacks represent deployed instances of an application, including the target provider and other details such as the deployment region. You'll usually define separate stacks for each environment such as development, testing and production. For now, let's start by creating a `dev` stack.
 

docs/guides/nodejs/api-with-nextjs.mdx

@@ -391,9 +391,9 @@ Pressing `ctrl + a + k` will end the application.
 
 Setup credentials and cloud specific configuration:
 
-- [AWS](/reference/providers/aws)
-- [Azure](/reference/providers/azure)
-- [GCP](/reference/providers/gcp)
+- [AWS](/providers/pulumi/aws)
+- [Azure](/providers/pulumi/azure)
+- [GCP](/providers/pulumi/gcp)
 
 Create a stack, which is a deployment target for your application.
 

docs/guides/nodejs/graphql.mdx

@@ -367,9 +367,9 @@ curl --location -X POST \
 
 Setup your credentials and any other cloud specific configuration:
 
-- [AWS](/reference/providers/aws)
-- [Azure](/reference/providers/azure)
-- [GCP](/reference/providers/gcp)
+- [AWS](/providers/pulumi/aws)
+- [Azure](/providers/pulumi/azure)
+- [GCP](/providers/pulumi/gcp)
 
 Create a stack - a collection of resources identified in your project which will be deployed.
 

docs/guides/nodejs/nitric-and-drizzle.mdx

@@ -278,7 +278,7 @@ region: us-east-2
 
 ### Deploy
 
-Go ahead and deploy to AWS using the `nitric up` command. Ensure you have setup your [AWS credentials](/reference/providers/aws#usage) correctly.
+Go ahead and deploy to AWS using the `nitric up` command. Ensure you have setup your [AWS credentials](/providers/pulumi/aws#usage) correctly.
 
 ```bash
 nitric up

docs/guides/nodejs/nitric-and-prisma.mdx

@@ -271,7 +271,7 @@ region: us-east-2
 
 ### Deploy
 
-Go ahead and deploy to AWS using the `nitric up` command. Ensure you have set up your [AWS credentials](/reference/providers/aws#usage) correctly.
+Go ahead and deploy to AWS using the `nitric up` command. Ensure you have set up your [AWS credentials](/providers/pulumi/aws#usage) correctly.
 
 ```bash
 nitric up