diff --git a/src/fragments/cli/plugins/custom-transformer.mdx b/src/fragments/cli/plugins/custom-transformer.mdx
index c850c7817fe..5c624184995 100644
--- a/src/fragments/cli/plugins/custom-transformer.mdx
+++ b/src/fragments/cli/plugins/custom-transformer.mdx
@@ -350,4 +350,4 @@ For the full source code of the `@model` transformer, go [here](https://github.c
 
 ## VS Code Extension
 
-Add the [VSCode extension](https://marketplace.visualstudio.com/items?itemName=aws-amplify.aws-amplify-vscode) to get code snippets and automatic code completion for Amplify APIs.
+Add the [VSCode extension](https://aws.amazon.com/visualstudiocode/) to get code snippets and automatic code completion for Amplify APIs.
diff --git a/src/pages/cli-legacy/graphql-transformer/auth.mdx b/src/pages/cli-legacy/graphql-transformer/auth.mdx
index 3414b981ae8..048533b540e 100644
--- a/src/pages/cli-legacy/graphql-transformer/auth.mdx
+++ b/src/pages/cli-legacy/graphql-transformer/auth.mdx
@@ -597,7 +597,7 @@ subscription OnCreatePost {
 }
 ```
 
-Note that if your type doesn’t already have an `owner` field the Transformer will automatically add this for you. Passing in the current user can be done dynamically in your code by using [Auth.currentAuthenticatedUser()](https://docs.amplify.aws/lib/auth/manageusers/q/platform/js#retrieve-current-authenticated-user) in JavaScript, [AWSMobileClient.default().username](/sdk/auth/working-with-api.md/q/platform/ios#utility-properties) in iOS, or [AWSMobileClient.getInstance().getUsername()](/sdk/auth/working-with-api.md/q/platform/android#utility-properties) in Android.
+Note that if your type doesn’t already have an `owner` field the Transformer will automatically add this for you. Passing in the current user can be done dynamically in your code by using [Auth.currentAuthenticatedUser()](https://docs.amplify.aws/lib/auth/manageusers/q/platform/js#retrieve-current-authenticated-user) in JavaScript, [AWSMobileClient.default().username](/sdk/auth/working-with-api/q/platform/ios#utility-properties) in iOS, or [AWSMobileClient.getInstance().getUsername()](/sdk/auth/working-with-api/q/platform/android#utility-properties) in Android.
 
 In the case of groups if you define the following:
 
diff --git a/src/pages/cli-legacy/graphql-transformer/overview.mdx b/src/pages/cli-legacy/graphql-transformer/overview.mdx
index 4f7176d1dcb..a571c83832d 100644
--- a/src/pages/cli-legacy/graphql-transformer/overview.mdx
+++ b/src/pages/cli-legacy/graphql-transformer/overview.mdx
@@ -30,7 +30,7 @@ type Comment @model {
 
 The GraphQL Transform simplifies the process of
 developing, deploying, and maintaining GraphQL APIs. With it, you define your API using the
-[GraphQL Schema Definition Language (SDL)](https://facebook.github.io/graphql/June2018/) and can then use automation to transform it into a fully
+[GraphQL Schema Definition Language (SDL)](https://graphql.org/learn/schema/) and can then use automation to transform it into a fully
 descriptive cloudformation template that implements the spec. The transform also provides a framework
 through which you can define your own transformers as `@directives` for custom workflows.
 
diff --git a/src/pages/cli-legacy/graphql-transformer/resolvers.mdx b/src/pages/cli-legacy/graphql-transformer/resolvers.mdx
index 80398e9dace..e8bbbbd2064 100644
--- a/src/pages/cli-legacy/graphql-transformer/resolvers.mdx
+++ b/src/pages/cli-legacy/graphql-transformer/resolvers.mdx
@@ -555,7 +555,7 @@ Amazon OpenSearch domains can take a while to deploy. Take this time to read up
 
 An index mapping tells OpenSearch how it should treat the data that you are trying to store. By default, if you create an object with field `"location": { "lat": 40, "lon": -40 }`, OpenSearch will treat that data as an *object* type when in reality you want it to be treated as a *geo_point*. You use the mapping APIs to tell OpenSearch how to do this.
 
-Make sure you tell OpenSearch that your location field is a *geo_point* before creating objects in the index because otherwise you will need delete the index and try again. Go to the [Amazon OpenSearch Console](https://console.aws.amazon.com/es/home) and find the OpenSearch domain that contains this environment's GraphQL API ID. Click on it and open the OpenSearch Dashboard link. To get the OpenSearch Dashboard to show up you need to install a browser extension such as [AWS Agent](https://addons.mozilla.org/en-US/firefox/addon/aws-agent/) and configure it with your AWS profile's public key and secret so the browser can sign your requests to the OpenSearch Dashboard for security reasons. Once you have the OpenSearch Dashboard open, click the "Dev Tools" tab on the left and run the commands below using the in browser console.
+Make sure you tell OpenSearch that your location field is a *geo_point* before creating objects in the index because otherwise you will need delete the index and try again. Go to the [Amazon OpenSearch Console](https://console.aws.amazon.com/aos/home) and find the OpenSearch domain that contains this environment's GraphQL API ID. Click on it and open the OpenSearch Dashboard link. To get the OpenSearch Dashboard to show up you need to install a browser extension such as [AWS Agent](https://addons.mozilla.org/en-US/firefox/addon/aws-agent/) and configure it with your AWS profile's public key and secret so the browser can sign your requests to the OpenSearch Dashboard for security reasons. Once you have the OpenSearch Dashboard open, click the "Dev Tools" tab on the left and run the commands below using the in browser console.
 
 ```text
 # Create the /todo index if it does not exist
diff --git a/src/pages/cli/auth/override.mdx b/src/pages/cli/auth/override.mdx
index 674e49efd43..10c93c72615 100644
--- a/src/pages/cli/auth/override.mdx
+++ b/src/pages/cli/auth/override.mdx
@@ -120,7 +120,7 @@ You can override the following user pool group resources that Amplify generates:
 |[userPoolGroup](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cognito-userpoolgroup.html)|The map of user pool groups|
 |[userPoolGroupRole](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-iam-role.html)|The map of user pool group roles|
 |[roleMapCustomResource](https://docs.aws.amazon.com/cdk/api/latest/docs/@aws-cdk_aws-cloudformation.CustomResource.html)|A custom CloudFormation resource to map user pool groups to their roles|
-|[lambdaExecutionRole](iam.CfnRole)|Lambda execution role for the "user pool group"-to-role mapping function|
+|[lambdaExecutionRole](https://docs.aws.amazon.com/lambda/latest/dg/lambda-intro-execution-role.html)|Lambda execution role for the "user pool group"-to-role mapping function|
 |[roleMapLambdaFunction](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-lambda-function.html)|The Lambda function that facilitates the user pool group to role mapping|
 
 
diff --git a/src/pages/cli/hosting/hosting.mdx b/src/pages/cli/hosting/hosting.mdx
index ec193debddd..d19c958da4d 100644
--- a/src/pages/cli/hosting/hosting.mdx
+++ b/src/pages/cli/hosting/hosting.mdx
@@ -48,7 +48,7 @@ Amplify Console automatically handles cache invalidation and there is no additio
 
 If you start from the Amplify Console's home page and connect your project's code repository (by clicking `Connect app` button), the frontend environment is created for your project once the workflow successfully completes. After setting up hosting in the Amplify Console, you cannot run the `amplify hosting add` command from your local installation of the Amplify CLI. To disable hosting, please visit the Amplify Console and disconnect the branch from the `App settings > General` page.
 
-If you're hosting a Single Page Web App (SPA) with routing such as [`react-router`](https://reactrouter.com/web/guides/quick-start), you'll need to add a [redirect](https://docs.aws.amazon.com/amplify/latest/userguide/redirects.html#redirects-for-single-page-web-apps-spa) in the Amplify console.
+If you're hosting a Single Page Web App (SPA) with routing such as [`react-router`](https://reactrouter.com/en/main/start/tutorial), you'll need to add a [redirect](https://docs.aws.amazon.com/amplify/latest/userguide/redirects.html#redirects-for-single-page-web-apps-spa) in the Amplify console.
 
 ![SPA redirect](/images/hosting/spa-redirect.png)
 
diff --git a/src/pages/cli/project/troubleshooting.mdx b/src/pages/cli/project/troubleshooting.mdx
index 3f94e79c8fa..d0562ea760f 100644
--- a/src/pages/cli/project/troubleshooting.mdx
+++ b/src/pages/cli/project/troubleshooting.mdx
@@ -70,7 +70,7 @@ Upon deployment, the Amplify-generated CloudFormation templates provision an App
 
 #### Scenario 1: "amplify push" fails after manually updating DynamoDB tables and GSIs from the console.
 Assume you have an application with a GraphQL schema deployed to the cloud.
-Amplify creates DynamoDB tables for all [@model]((/cli/graphql/data-modeling/)) types and GSIs for all [@index]((/cli/graphql/data-modeling/)) fields in the GraphQL schema.
+Amplify creates DynamoDB tables for all [@model](/cli/graphql/data-modeling/) types and GSIs for all [@index](/cli/graphql/data-modeling/) fields in the GraphQL schema.
 "Drift" is introduced if you delete any of the GSIs using the DynamoDB console, instead of using the Amplify CLI.
 With drift, future changes to the GraphQL schema may fail to deploy.
 As an example, if you change the names of some `@model` types and `@index` fields in your GraphQL schema and perform the `amplify push --allow-destructive-graphql-schema-updates` command, Amplify will first remove all DynamoDB tables corresponding to the original model names.
@@ -151,8 +151,8 @@ To debug any issues related to secrets not being correctly copied across environ
 "Cannot exceed quota for PoliciesPerRole"
 </Callout>
 
-AWS maintains [service quotas](/general/latest/gr/aws-service-information.html) for various AWS services. If your application contains many resources, such as large GraphQL schemas with many resolvers or many REST APIs, you may hit a service limit.
-To identify if exceeding an [AWS Service level quotas](/general/latest/gr/aws-service-information.html) caused a deployment failure, check the AWS console for the CloudFormation deployment/failure logs.
+AWS maintains [service quotas](https://docs.aws.amazon.com/general/latest/gr/aws-service-information.html) for various AWS services. If your application contains many resources, such as large GraphQL schemas with many resolvers or many REST APIs, you may hit a service limit.
+To identify if exceeding an [AWS Service level quotas](https://docs.aws.amazon.com/general/latest/gr/aws-service-information.html) caused a deployment failure, check the AWS console for the CloudFormation deployment/failure logs.
 
 **Suggested Resolution:**
 1. If your application's resource requirements are impaired by AWS service quotas, you can use the [AWS Service Quotas console](https://console.aws.amazon.com/servicequotas) to view and request increases for most AWS quotas.