more links

Signed-off-by: nikki everett <[email protected]>
dagster-io · Dec 11, 2024 · dd8d1ff · dd8d1ff
1 parent 60e6aca
commit dd8d1ff
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/index.md b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/index.md
@@ -22,7 +22,7 @@ The Dagster+ agent is a long-lived process that polls Dagster+'s API servers for
 
 See the following guides for setting up an agent:
  - [Kubernetes](/dagster-plus/deployment/deployment-types/hybrid/kubernetes)
- - [AWS ECS](/dagster-plus/deployment/deployment-types/hybrid/new-vpc)
+ - [AWS ECS](/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/new-vpc)
  - [Docker](/dagster-plus/deployment/deployment-types/hybrid/docker)
  - [Locally](/dagster-plus/deployment/deployment-types/hybrid/local)
 

diff --git a/...docs/dagster-plus/features/authentication-and-access-control/rbac/audit-logs.md b/...docs/dagster-plus/features/authentication-and-access-control/rbac/audit-logs.md
@@ -43,7 +43,7 @@ The **Filter** button near the top left of the page can be used to filter the li
 | Log in                         | A user logs in to the Dagster+ organization                                                                   |                                                                           |
 | Update sensor                  | A user toggles a sensor on or off                                                                             | The sensor name, code location, and cursor                                |
 | Update schedule                | A user toggles a schedule on or off                                                                           | The schedule name, code location, and cursor                              |
-| Update alert policy            | A user modifies an [alert policy](/dagster-plus/features/alerts/ui)                                         | The new configuration for the alert policy                                |
+| Update alert policy            | A user modifies an [alert policy](/dagster-plus/features/alerts/creating-alerts)                                         | The new configuration for the alert policy                                |
 | Create deployment              | A user creates a new deployment                                             | Whether the deployment is a branch deployment                             |
 | Delete deployment              | A user removes an existing deployment                                       | Whether the deployment is a branch deployment                             |
 | Create user token              | A user creates a new user token                                                                               |                                                                           |

diff --git a/...dagster-plus/features/ci-cd/branch-deployments/setting-up-branch-deployments.md b/...dagster-plus/features/ci-cd/branch-deployments/setting-up-branch-deployments.md
@@ -82,7 +82,7 @@ While you can use your existing production agent, we recommend creating a dedica
 <Tabs>
   <TabItem value="ecs" label="Amazon ECS">
 
-  1. **Deploy an ECS agent to serve your branch deployments**. Follow the [ECS agent](/dagster-plus/deployment/deployment-types/hybrid/new-vpc) setup guide, making sure to set the **Enable Branch Deployments** parameter if using the CloudFormation template. If you are running an existing agent, follow the [upgrade guide](/dagster-plus/deployment/deployment-types/hybrid/existing-vpc) to ensure your template is up-to-date. Then, turn on the **Enable Branch Deployments** parameter.
+  1. **Deploy an ECS agent to serve your branch deployments**. Follow the [ECS agent](/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/new-vpc) setup guide, making sure to set the **Enable Branch Deployments** parameter if using the CloudFormation template. If you are running an existing agent, follow the [upgrade guide](/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/existing-vpc) to ensure your template is up-to-date. Then, turn on the **Enable Branch Deployments** parameter.
 
   2. **Create a private [Amazon Elastic Registry (ECR) repository](https://console.aws.amazon.com/ecr/repositories).** Refer to the [AWS ECR documentation](https://docs.aws.amazon.com/AmazonECR/latest/userguide/repository-create.html) for instructions.