more links fixed and rules updated

.github/workflows/linkcheck.json

@@ -19,6 +19,7 @@
       { "pattern": "https://helm.datadoghq.com" },
       { "pattern": "https://sqs" },
       { "pattern": "www.rsa-2048.example.com" },
-      { "pattern": "rsa-2048.example.com"}
+      { "pattern": "rsa-2048.example.com" },
+      { "pattern": "https://ingress-red-saas.instana.io/" }
     ]
 }

docs/addons/argo-cd.md

@@ -4,7 +4,7 @@
 
 The Argo CD add-on allows platform administrators to combine cluster provisioning and workload bootstrapping in a single step and enables use cases such as replicating an existing running production cluster in a different region in a matter of minutes. This is important for business continuity and disaster recovery cases as well as for cross-regional availability and geographical expansion.
 
-Please see the documentation below for details on automatic boostrapping with ArgoCD add-on. If you prefer manual bootstrapping (once your cluster is deployed with this add-on included), you can find instructions on getting started with Argo CD in our [Getting Started](../getting-started.md/#deploy-workloads-with-argocd) guide.
+Please see the documentation below for details on automatic boostrapping with ArgoCD add-on. If you prefer manual bootstrapping (once your cluster is deployed with this add-on included), you can find instructions on getting started with Argo CD in our [Getting Started](../getting-started.md#deploy-workloads-with-argocd) guide.
 
 Full Argo CD project documentation [can be found here](https://argo-cd.readthedocs.io/en/stable/).
 

docs/getting-started.md

@@ -136,15 +136,15 @@ You should see output that lists all namespaces in your cluster.
 
 ## Deploy workloads with ArgoCD
 
-Next, let's walk you through how to deploy workloads to your cluster with ArgoCD. This approach leverages the [App of Apps](https://argoproj.github.io/argo-cd/operator-manual/cluster-bootstrapping/#app-of-apps-pattern) pattern to deploy multiple workloads across multiple namespaces. The sample app of apps repository that we use in this getting started guide can be found [here](https://github.com/aws-samples/eks-blueprints-workloads).
+Next, let's walk you through how to deploy workloads to your cluster with ArgoCD. This approach leverages the [App of Apps](https://argo-cd.readthedocs.io/en/stable/operator-manual/cluster-bootstrapping/#app-of-apps-pattern) pattern to deploy multiple workloads across multiple namespaces. The sample app of apps repository that we use in this getting started guide can be found [here](https://github.com/aws-samples/eks-blueprints-workloads).
 
 You can leverage [Automatic Bootstrapping](addons/argo-cd.md#bootstrapping) for automatic onboarding of workloads. This feature may be leveraged even when workload repositories are not ready yet, as it creates a placeholder for future workloads and decouples workload onboarding for the infrastructure provisioning pipeline. The next steps, described in this guide apply for cases when customer prefer to bootstrap their workloads manually through ArgoCD UI console.
 
 ### Install ArgoCD CLI
 
 These steps are needed for manual workload onboarding. For automatic bootstrapping please refer to the [Automatic Bootstrapping](addons/argo-cd.md#bootstrapping).
 
-Follow the instructions found [here](https://argoproj.github.io/argo-cd/cli_installation/) as it will include instructions for your specific OS. You can test that the ArgoCD CLI was installed correctly using the following:
+Follow the instructions found [here](https://argo-cd.readthedocs.io/en/stable/cli_installation/) as it will include instructions for your specific OS. You can test that the ArgoCD CLI was installed correctly using the following:
 
 ```
 argocd version --short --client
@@ -172,7 +172,7 @@ kubectl port-forward $ARGO_SERVER -n argocd 8080:443
 
 Open your browser to http://localhost:8080 and you should see the ArgoCD login screen.
 
-![ArgoCD](../assets/images/argo-cd.png)
+![ArgoCD](./assets/images/argo-cd.png)
 
 ### Logging Into ArgoCD
 
@@ -232,10 +232,10 @@ Open up `localhost:4040` in your browser and you should see the application.
 
 ## Next Steps
 
-For information on onboarding teams to your clusters, see [`Team` documentation](../teams). 
+For information on onboarding teams to your clusters, see [`Team` documentation](./teams/teams.md). 
 
-For information on deploying Continuous Delivery pipelines for your infrastructure, see [`Pipelines` documentation](../pipelines).
+For information on deploying Continuous Delivery pipelines for your infrastructure, see [`Pipelines` documentation](./pipelines.md).
 
-For information on supported add-ons, see [`Add-on` documentation](../addons)
+For information on supported add-ons, see [`Add-on` documentation](./addons/index.md)
 
 For information on Onboarding and managing workloads in your clusters, see [`Workload` documentation](https://github.com/aws-samples/eks-blueprints-workloads). 

docs/internal/input-validations-framework-readme.md

@@ -95,7 +95,7 @@ This is the entry point to use the framework. This function can validate either
 
 ## How to use the constraints-utils.ts
 
-You need two things when utilizing constraints-utils.ts and the following examples are from ['here'](/lib/stacks/eks-blueprint-stack.ts)
+You need two things when utilizing constraints-utils.ts and the following examples are from ['here'](../../lib/stacks/eks-blueprint-stack.ts)
 
 First you need a class with specified keys assigned to given constraints.