Fix links

cloudposse · Nov 19, 2024 · 220e3d5 · 220e3d5
1 parent 721c667
commit 220e3d5
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 4 deletions.
diff --git a/docs/layers/accounts/tutorials/deprecated-cold-start-components.mdx b/docs/layers/accounts/tutorials/deprecated-cold-start-components.mdx
@@ -52,7 +52,7 @@ The following guidance provides clarity on the security of the metadata files.
 
 :::
 
-Learn more about the [sso](/components/library/aws/aws-inden/) component.
+Learn more about the [sso](/components/library/aws/identity-center/) component.
 
 #### Provision `iam-primary-roles` component
 

diff --git a/docs/layers/monitoring/datadog/setup.mdx b/docs/layers/monitoring/datadog/setup.mdx
@@ -63,7 +63,7 @@ plat is in place, usually EKS or ECS.
 
 There are two core components to the Datadog implementation
 
-1.  [**datadog-configuration**](https://docs.cloudposse.com/components/library/aws/datadog-configuration)
+1.  [**datadog-configuration**](https://docs.cloudposse.com/components/library/aws/datadog-credentials)
 
 2.  [**datadog-integration**](https://docs.cloudposse.com/components/library/aws/datadog-integration)
 
@@ -107,7 +107,7 @@ This component also handles default configurations such as Datadog URL and provi
 components to utilize via its submodule `datadog_keys`.
 
 Use a configuration similar to the following but check the
-[`README.md`](https://docs.cloudposse.com/components/library/aws/datadog-configuration/) for exact input references.
+[`README.md`](https://docs.cloudposse.com/components/library/aws/datadog-credentials/) for exact input references.
 
 ```yaml
 components:

diff --git a/docs/layers/monitoring/monitoring.mdx b/docs/layers/monitoring/monitoring.mdx
@@ -31,7 +31,7 @@ We have broken down the monitoring solution into several components to make it e
 
 #### Foundation
 
-- [`datadog-configuration`](/components/library/aws/datadog-configuration/): This is a **utility** component. This component expects Datadog API and APP keys to be stored in SSM or ASM, it then copies the keys to SSM/ASM of each account this component is deployed to. This is for several reasons:
+- [`datadog-configuration`](/components/library/aws/datadog-credentials/): This is a **utility** component. This component expects Datadog API and APP keys to be stored in SSM or ASM, it then copies the keys to SSM/ASM of each account this component is deployed to. This is for several reasons:
   1. Keys can be easily rotated from one place
   2. Keys can be set for a group and then copied to all accounts in that group, meaning you could have a pair of api keys and app keys for production accounts and another set for non-production accounts.
   This component is **required** for all other components to work. As it also stores information about your Datadog account, which other components will use, such as your Datadog site url, along with providing an easy interface for other components to configure the Datadog provider.