sst
diff --git a/‎_archives/deploying-a-react-app-to-netlify.md
+1-1 b/‎_archives/deploying-a-react-app-to-netlify.md
+1-1
diff --git a/‎_archives/dynamically-generate-social-share-images-with-serverless.md
+4-4 b/‎_archives/dynamically-generate-social-share-images-with-serverless.md
+4-4
diff --git a/‎_archives/setting-serverless-environments-variables-in-a-react-app.md
+2-2 b/‎_archives/setting-serverless-environments-variables-in-a-react-app.md
+2-2
diff --git a/‎_archives/using-aws-cdk-with-serverless-framework.md
+1-1 b/‎_archives/using-aws-cdk-with-serverless-framework.md
+1-1
diff --git a/‎_archives/using-cognito-to-add-authentication-to-a-serverless-app.md
+5-5 b/‎_archives/using-cognito-to-add-authentication-to-a-serverless-app.md
+5-5
diff --git a/‎_archives/what-is-aws-appsync.md
+2-2 b/‎_archives/what-is-aws-appsync.md
+2-2
diff --git a/‎_chapters/add-an-api-to-create-a-note.md
+3-3 b/‎_chapters/add-an-api-to-create-a-note.md
+3-3
diff --git a/‎_chapters/adding-auth-to-our-serverless-app.md
+1-1 b/‎_chapters/adding-auth-to-our-serverless-app.md
+1-1
diff --git a/‎_chapters/create-a-dynamodb-table-in-sst.md
+1-1 b/‎_chapters/create-a-dynamodb-table-in-sst.md
+1-1
diff --git a/‎_chapters/create-a-hello-world-api.md
+1-1 b/‎_chapters/create-a-hello-world-api.md
+1-1
diff --git a/‎_chapters/create-a-new-reactjs-app.md
+1-1 b/‎_chapters/create-a-new-reactjs-app.md
+1-1
diff --git a/‎_chapters/create-an-s3-bucket-in-sst.md
+1-1 b/‎_chapters/create-an-s3-bucket-in-sst.md
+1-1
diff --git a/‎_chapters/create-an-sst-app.md
+1-1 b/‎_chapters/create-an-sst-app.md
+1-1
diff --git a/‎_chapters/creating-a-ci-cd-pipeline-for-serverless.md
+1-1 b/‎_chapters/creating-a-ci-cd-pipeline-for-serverless.md
+1-1
diff --git a/‎_chapters/custom-domains-in-serverless-apis.md
+1-1 b/‎_chapters/custom-domains-in-serverless-apis.md
+1-1
diff --git a/‎_chapters/further-reading.md
+2-2 b/‎_chapters/further-reading.md
+2-2
diff --git a/‎_chapters/handle-cors-in-s3-for-file-uploads.md
+2-2 b/‎_chapters/handle-cors-in-s3-for-file-uploads.md
+2-2
diff --git a/‎_chapters/handle-cors-in-serverless-apis.md
+2-2 b/‎_chapters/handle-cors-in-serverless-apis.md
+2-2
@@ -11,7 +11,7 @@ redirect_from:
   - /chapters/hosting-your-react-app.html
 ---
 
-In this section we'll be looking at how to deploy your React.js app as a static website to [Netlify](https://www.netlify.com). You'll recall that in the [main part of the guide]({% link _chapters/create-a-new-reactjs-app.md %}) we used the SST [`ReactStaticSite`]({{ site.docs_url }}/constructs/ReactStaticSite) construct to deploy our React app to AWS.
+In this section we'll be looking at how to deploy your React.js app as a static website to [Netlify](https://www.netlify.com). You'll recall that in the [main part of the guide]({% link _chapters/create-a-new-reactjs-app.md %}) we used the SST [`ReactStaticSite`]({{ site.v2_url }}/constructs/ReactStaticSite) construct to deploy our React app to AWS.
 
 Netlify allows you to [host your React app for free](https://www.netlify.com/pricing/) and it allows your to `git push` to deploy your apps.
 
 
@@ -764,7 +764,7 @@ And that's it! Our social cards are now dynamically created for all our pages.
 
 ### Wrapping Up
 
-You can check out how these images look on [Serverless-Stack.com](/) and on our [Docs site]({{ site.docs_url }}) by sharing a couple of our pages.
+You can check out how these images look on [Serverless-Stack.com](/) and on our [Docs site]({{ site.v2_url }}) by sharing a couple of our pages.
 
 Also, make sure to check out the repo that powers our social cards service — [{{ page.repo | remove: "https://" }}]({{ page.repo }})
 
@@ -774,8 +774,8 @@ The repo is setup with [Seed](https://seed.run), so a `git push` to the `main` b
 
 We used a couple of SST constructs while building this service. You can read more about them here:
 
-- [Api]({{ site.docs_url }}/constructs/Api)
-- [Bucket]({{ site.docs_url }}/constructs/Bucket)
-- [Function]({{ site.docs_url }}/constructs/Function)
+- [Api]({{ site.v2_url }}/constructs/Api)
+- [Bucket]({{ site.v2_url }}/constructs/Bucket)
+- [Function]({{ site.v2_url }}/constructs/Function)
 
 Hope you enjoyed this chapter. Leave a comment below if you have any questions or feedback!
@@ -68,7 +68,7 @@ export default class MyStack extends sst.Stack {
 }
 ```
 
-Here we are using the [`ReactStaticSite`]({{ site.docs_url }}/constructs/ReactStaticSite) construct. It allows us to set React environment variables from our API.
+Here we are using the [`ReactStaticSite`]({{ site.v2_url }}/constructs/ReactStaticSite) construct. It allows us to set React environment variables from our API.
 
 ```typescript
 environment: {
@@ -149,7 +149,7 @@ We need our React app to be deployed with our environment variables. SST uses [C
 3. Replace the environment variables in our React app.
 4. Deploy our React app to S3 and CloudFront.
 
-[SST](/){:target="_blank"} and the [`ReactStaticSite`]({{ site.docs_url }}/constructs/ReactStaticSite){:target="_blank"} construct do this automatically for you.
+[SST](/){:target="_blank"} and the [`ReactStaticSite`]({{ site.v2_url }}/constructs/ReactStaticSite){:target="_blank"} construct do this automatically for you.
 
 ![Serverless environment variable set in a React app deployed to AWS](/assets/extra-credit/serverless-environment-variable-set-in-a-react-app-deployed-to-aws.png)
 
 
@@ -16,7 +16,7 @@ In this guide we've looked at two different ways of creating serverless applicat
 As in, you can create your infrastructure with SST and manage your Lambda functions and APIs with Serverless Framework. There are a couple of reasons why you might find yourself wanting to do this.
 
 1. Your applications are currently built using Serverless Framework and you want to use [AWS CDK]({% link _archives/what-is-aws-cdk.md %}) instead of [CloudFormation for your resources]({% link _archives/configure-dynamodb-in-serverless.md %}).
-2. Or, you are looking to [migrate from Serverless Framework to SST]({{ site.docs_url }}/migrating-from-serverless-framework).
+2. Or, you are looking to [migrate from Serverless Framework to SST]({{ site.v2_url }}/migrating-from-serverless-framework).
 
 In this chapter we'll look at how we can use SST to define your infrastructure using CDK and connecting that to our Serverless Framework app.
 
 
@@ -58,7 +58,7 @@ const auth = new sst.Cognito(this, "Auth", {
 });
 ```
 
-This is using the SST [`Cognito`]({{ site.docs_url }}/constructs/Cognito) construct to create a Cognito User Pool and an Identity Pool.
+This is using the SST [`Cognito`]({{ site.v2_url }}/constructs/Cognito) construct to create a Cognito User Pool and an Identity Pool.
 
 #### Aliases
 
@@ -99,7 +99,7 @@ new Cognito(this, "Auth", {
 
 #### Cognito Triggers
 
-You also might want to trigger (before and after authentication) some actions. The [Cognito Triggers]({{ site.docs_url }}/constructs/Cognito#authuserpooltriggers) allow you to define Lambda functions that get executed for specific events.
+You also might want to trigger (before and after authentication) some actions. The [Cognito Triggers]({{ site.v2_url }}/constructs/Cognito#authuserpooltriggers) allow you to define Lambda functions that get executed for specific events.
 
 ```js
 new Cognito(this, "Auth", {
@@ -114,7 +114,7 @@ new Cognito(this, "Auth", {
 
 ### Adding an API
 
-Now let's look at how we can use Cognito to secure our API. In [`stacks/MyStack.js`]({{ repo_url }}/stacks/MyStack.js) of our example, you'll notice our SST [`Api`]({{ site.docs_url }}/constructs/Api) definition.
+Now let's look at how we can use Cognito to secure our API. In [`stacks/MyStack.js`]({{ repo_url }}/stacks/MyStack.js) of our example, you'll notice our SST [`Api`]({{ site.v2_url }}/constructs/Api) definition.
 
 ```js
 // Create an HTTP API
@@ -163,7 +163,7 @@ export async function handler() {
 
 ### Adding a React Static Site
 
-We can now turn our attention to the frontend part of our application. In [`stacks/MyStack.js`]({{ repo_url }}/stacks/MyStack.js) take a look at the SST [`ReactStaticSite`]({{ site.docs_url }}/constructs/ReactStaticSite) definition.
+We can now turn our attention to the frontend part of our application. In [`stacks/MyStack.js`]({{ repo_url }}/stacks/MyStack.js) take a look at the SST [`ReactStaticSite`]({{ site.v2_url }}/constructs/ReactStaticSite) definition.
 
 ```js
 // Deploy our React app
@@ -555,7 +555,7 @@ Make sure to check out the rest of the [`frontend/src/App.js`]({{ repo_url }}/fr
 
 ### Testing our App
 
-SST features a [Live Lambda Development]({{ site.docs_url }}/live-lambda-development) environment that allows you to work on your serverless apps live.
+SST features a [Live Lambda Development]({{ site.v2_url }}/live-lambda-development) environment that allows you to work on your serverless apps live.
 
 To test our [example]({{ repo_url }}):
 
 
@@ -110,11 +110,11 @@ Data sources in AWS AppSync are services, databases, or APIs that hold the data
 
 There are just a handful of data sources that AWS AppSync supports, such as [Amazon DynamoDB](https://aws.amazon.com/dynamodb/), [AWS Lambda](https://aws.amazon.com/lambda/) (Lambda can allow you to use other options, such as RDS or ElastiCache), and [Amazon Elasticsearch Service](https://aws.amazon.com/elasticsearch-service/).
 
-SST’s [`AppSyncApi` construct]({{ site.docs_url }}/constructs/AppSyncApi#examples) makes creating data sources a lot easier. We'll be looking at some examples of how to do this below.
+SST’s [`AppSyncApi` construct]({{ site.v2_url }}/constructs/AppSyncApi#examples) makes creating data sources a lot easier. We'll be looking at some examples of how to do this below.
 
 You’ll need data sources whenever you need to fetch and manipulate data. However, in some cases where you might only want to perform data transformation with resolvers and subscriptions to be invoked by a mutation, you might not need a data source.
 
-Using the [SST `AppSyncApi`]({{ site.docs_url }}/constructs/AppSyncApi), you could add a data source to your GraphQL API easily without having to log in to your AWS console.
+Using the [SST `AppSyncApi`]({{ site.v2_url }}/constructs/AppSyncApi), you could add a data source to your GraphQL API easily without having to log in to your AWS console.
 
 ```js
 import { AppSyncApi } from "@serverless-stack/resources";
 
@@ -35,9 +35,9 @@ api.route("POST /notes", "packages/functions/src/create.main");
 
 We are doing a couple of things of note here.
 
-- We are creating an API using SST's [`Api`]({{ site.ion_url }}/docs/component/apigatewayv2/){:target="_blank"} component. It creates an [Amazon API Gateway HTTP API](https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api.html){:target="_blank"}.
+- We are creating an API using SST's [`Api`]({{ site.sst_url }}/docs/component/apigatewayv2/){:target="_blank"} component. It creates an [Amazon API Gateway HTTP API](https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api.html){:target="_blank"}.
 
-- We are [linking]({{ site.ion_url }}/docs/linking/){:target="_blank"} our DynamoDB table to our API using the `link` prop. This will allow our API to access our table.
+- We are [linking]({{ site.sst_url }}/docs/linking/){:target="_blank"} our DynamoDB table to our API using the `link` prop. This will allow our API to access our table.
 
 - The first route we are adding to our API is the `POST /notes` route. It'll be used to create a note.
 
@@ -109,7 +109,7 @@ There are some helpful comments in the code but let's go over them quickly.
 - Parse the input from the `event.body`. This represents the HTTP request body.
 - It contains the contents of the note, as a string — `content`.
 - It also contains an `attachment`, if one exists. It's the filename of a file that will be uploaded to [our S3 bucket]({% link _chapters/create-an-s3-bucket-in-sst.md %}).
-- We can access our linked DynamoDB table through `Resource.Notes.name` using the [SST SDK]({{ site.ion_url }}/docs/reference/sdk/){:target="_blank"}. Here, `Notes` in `Resource.Notes`, is the name of our Table component from the [Create a DynamoDB Table in SST]({% link _chapters/create-a-dynamodb-table-in-sst.md %}) chapter. By doing `link: [table]` earlier in this chapter, we are allowing our API to access our table.
+- We can access our linked DynamoDB table through `Resource.Notes.name` using the [SST SDK]({{ site.sst_url }}/docs/reference/sdk/){:target="_blank"}. Here, `Notes` in `Resource.Notes`, is the name of our Table component from the [Create a DynamoDB Table in SST]({% link _chapters/create-a-dynamodb-table-in-sst.md %}) chapter. By doing `link: [table]` earlier in this chapter, we are allowing our API to access our table.
 - The `userId` is the id for the author of the note. For now we are hardcoding it to `123`. Later we'll be setting this based on the authenticated user.
 - Make a call to DynamoDB to put a new object with a generated `noteId` and the current date as the `createdAt`.
 - And if the DynamoDB call fails then return an error with the HTTP status code `500`.
 
@@ -13,7 +13,7 @@ comments_id: adding-auth-to-our-serverless-app/2457
 
 So far we've created the [DynamoDB table]({% link _chapters/create-a-dynamodb-table-in-sst.md %}), [S3 bucket]({% link _chapters/create-an-s3-bucket-in-sst.md %}), and [API]({% link _chapters/add-an-api-to-create-a-note.md %}) parts of our serverless backend. Now let's add auth into the mix. As we talked about in the [previous chapter]({% link _chapters/auth-in-serverless-apps.md %}), we are going to use [Cognito User Pool](https://aws.amazon.com/cognito/){:target="_blank"} to manage user sign ups and logins. While we are going to use [Cognito Identity Pool](https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-identity.html){:target="_blank"} to manage which resources our users have access to.
 
-Setting this all up can be pretty complicated in Terraform. SST has simple [`CognitoUserPool`]({{ site.ion_url }}/docs/component/aws/cognito-user-pool/){:target="_blank"} and [`CognitoIdentityPool`]({{ site.ion_url }}/docs/component/aws/cognito-identity-pool/){:target="_blank"} components to help with this.
+Setting this all up can be pretty complicated in Terraform. SST has simple [`CognitoUserPool`]({{ site.sst_url }}/docs/component/aws/cognito-user-pool/){:target="_blank"} and [`CognitoIdentityPool`]({{ site.sst_url }}/docs/component/aws/cognito-identity-pool/){:target="_blank"} components to help with this.
 
 ### Create the Components
 
 
@@ -28,7 +28,7 @@ export const table = new sst.aws.Dynamo("Notes", {
 
 Let's go over what we are doing here.
 
-We are using the [`Dynamo`]({{ site.ion_url }}/docs/component/aws/dynamo/){:target="_blank"} component to create our DynamoDB table.
+We are using the [`Dynamo`]({{ site.sst_url }}/docs/component/aws/dynamo/){:target="_blank"} component to create our DynamoDB table.
 
 It has two fields:
 
 
@@ -63,7 +63,7 @@ Let's go ahead and deploy this.
 
 ### Start Your Dev Environment
 
-We'll do this by starting up our local development environment. SST's dev environment runs your functions [Live]({{ site.ion_url }}/docs/live){:target="_blank"}. It allows you to work on your serverless apps live.
+We'll do this by starting up our local development environment. SST's dev environment runs your functions [Live]({{ site.sst_url }}/docs/live){:target="_blank"}. It allows you to work on your serverless apps live.
 
 {%change%} Start your dev environment.
 
 
@@ -57,7 +57,7 @@ build: {
 
 ### Add the React App to SST
 
-We are going to be deploying our React app to AWS. To do that we'll be using the SST [`StaticSite`]({{ site.ion_url }}/docs/component/aws/static-site/){:target="_blank"} component.
+We are going to be deploying our React app to AWS. To do that we'll be using the SST [`StaticSite`]({{ site.sst_url }}/docs/component/aws/static-site/){:target="_blank"} component.
 
 {%change%} Create a new file in `infra/web.ts` and add the following.
 
 
@@ -18,7 +18,7 @@ Recall the following from `infra/storage.ts`.
 export const bucket = new sst.aws.Bucket("Uploads");
 ```
 
-Here we are creating a new S3 bucket using the SST [`Bucket`]({{ site.ion_url }}/docs/component/aws/bucket){:target="_blank"} component.
+Here we are creating a new S3 bucket using the SST [`Bucket`]({{ site.sst_url }}/docs/component/aws/bucket){:target="_blank"} component.
 
 ### Commit the Changes
 
 
@@ -74,7 +74,7 @@ export default $config({
 To rename an app, you’ll need to remove the resources from the old one and deploy to the new one.
 {%endcaution%}
 
-The name of your app as you might recall is `notes`. A word of caution on IaC, if you rename your app after you deploy it, it doesn't rename the previously created resources in your app. You'll need to remove your old app and redeploy it again with the new name. To get a better sense of this, you can read more about the [SST workflow]({{ site.ion_url }}/docs/workflow){:target="_blank"}.
+The name of your app as you might recall is `notes`. A word of caution on IaC, if you rename your app after you deploy it, it doesn't rename the previously created resources in your app. You'll need to remove your old app and redeploy it again with the new name. To get a better sense of this, you can read more about the [SST workflow]({{ site.sst_url }}/docs/workflow){:target="_blank"}.
 
 ## Project layout
 
 
@@ -44,7 +44,7 @@ Our workflow is fairly simple. But as your team grows, you'll need to add additi
 
 There are many common CI/CD services, like [GitHub Actions](https://github.com/features/actions){:target="_blank"}, [Travis CI](https://travis-ci.org){:target="_blank"} or [CircleCI](https://circleci.com){:target="_blank"}. These usually require you to manually configure the above pipeline. It involves a fair bit of scripts and configuration.
 
-SST makes this easier with the [SST Console]({{ site.ion_url }}/docs/console/){:target="_blank"}'s [Autodeploy](/docs/console/#autodeploy){:target="_blank"} feature. It also shows you all the resources in your app and allows you to monitor and debug them.
+SST makes this easier with the [SST Console]({{ site.sst_url }}/docs/console/){:target="_blank"}'s [Autodeploy](/docs/console/#autodeploy){:target="_blank"} feature. It also shows you all the resources in your app and allows you to monitor and debug them.
 
 We should mention that you don't have to use the SST Console. And this section is completely optional.
 
 
@@ -23,7 +23,7 @@ This tells SST that we want to use a custom domain **if** we are deploying to th
 
 We could for example, base it on the stage name, `api-${app.stage}.my-serverless-app.com`. So for `dev` it might be `api-dev.my-serverless-app.com`. But we'll leave that as an exercise for you.
 
-The `$app` is a global variable that's available in our config. You can [learn more about it here]({{ site.ion_url }}/docs/reference/global/#app){:target="_blank"}.
+The `$app` is a global variable that's available in our config. You can [learn more about it here]({{ site.sst_url }}/docs/reference/global/#app){:target="_blank"}.
 
 ### Deploy the App
 
 
@@ -10,7 +10,7 @@ comments_id: further-reading/209
 
 Once you've completed the guide, you are probably going to use SST for your next project. To help you along the way we try to compile a list of docs that you can use as a reference. The following can be used to drill down in detail for some of the technologies and services used in this guide.
 
-- [SST Documentation]({{ site.ion_url }}): Documentation for SST
+- [SST Documentation]({{ site.sst_url }}/docs/): Documentation for SST
 
 - [DynamoDB, explained](https://www.dynamodbguide.com): A Primer on the DynamoDB NoSQL database
 
@@ -26,6 +26,6 @@ Once you've completed the guide, you are probably going to use SST for your next
 
 - [Vitest Docs](https://vitest.dev/guide/): The official Vitest docs
 
-- [SST Console Docs]({{ site.ion_url }}/docs/console/): The SST Console docs
+- [SST Console Docs]({{ site.sst_url }}/docs/console/): The SST Console docs
 
 If you have found any other guides or tutorials helpful in building your serverless app, feel free to edit this page and submit a PR. Or you can let us know via the comments.
@@ -10,7 +10,7 @@ comments_id: handle-cors-in-s3-for-file-uploads/2174
 
 In the notes app we are building, users will be uploading files to the bucket we just created. And since our app will be served through our custom domain, it'll be communicating across domains while it does the uploads. By default, S3 does not allow its resources to be accessed from a different domain. However, [cross-origin resource sharing (CORS)](https://en.wikipedia.org/wiki/Cross-origin_resource_sharing){:target="_blank"} defines a way for client web applications that are loaded in one domain to interact with resources in a different domain.
 
-Similar to the [previous chapter]({% link _chapters/handle-cors-in-serverless-apis.md %}), the [`Bucket`]({{ site.ion_url }}/docs/component/aws/bucket/){:target="_blank"} component enables CORS by default.
+Similar to the [previous chapter]({% link _chapters/handle-cors-in-serverless-apis.md %}), the [`Bucket`]({{ site.sst_url }}/docs/component/aws/bucket/){:target="_blank"} component enables CORS by default.
 
 ```ts
 new sst.aws.Bucket("Uploads", {
@@ -19,7 +19,7 @@ new sst.aws.Bucket("Uploads", {
 });
 ```
 
-You can configure this further. [Read more about this here]({{ site.ion_url }}/docs/component/aws/bucket#cors){:target="_blank"}.
+You can configure this further. [Read more about this here]({{ site.sst_url }}/docs/component/aws/bucket#cors){:target="_blank"}.
 
 ```ts
 new sst.aws.Bucket("Uploads", {
 
@@ -46,7 +46,7 @@ And our browser won't show us the HTTP response. This can make debugging our API
 
 ### CORS in API Gateway
 
-The [`ApiGatewayV2`]({{ site.ion_url }}/docs/component/aws/apigatewayv2/){:target="_blank"} component that we are using enables CORS by default.
+The [`ApiGatewayV2`]({{ site.sst_url }}/docs/component/aws/apigatewayv2/){:target="_blank"} component that we are using enables CORS by default.
 
 ```ts
 new sst.aws.ApiGatewayV2("Api", {
@@ -55,7 +55,7 @@ new sst.aws.ApiGatewayV2("Api", {
 });
 ```
 
-You can further configure the specifics if necessary. You can [read more about this here]({{ site.ion_url }}/docs/component/aws/apigatewayv2#cors){:target="_blank"}.
+You can further configure the specifics if necessary. You can [read more about this here]({{ site.sst_url }}/docs/component/aws/apigatewayv2#cors){:target="_blank"}.
 
 ```typescript
 new sst.aws.ApiGatewayV2("Api", {