update integrations API docs frontmatter and links to API integrations docs

Signed-off-by: nikki everett <nikki@dagsterlabs.com>

Author: neverett

docs/docs/deployment/dagster-plus/management/customizing-agent-settings.md

@@ -96,7 +96,7 @@ compute_logs:
 
 ## Writing compute logs to AWS S3
 
-{/* /api/libraries/dagster-aws#dagster_aws.s3.S3ComputeLogManager */}
+{/* /integrations/libraries/aws/dagster-aws#dagster_aws.s3.S3ComputeLogManager */}
 You can write compute logs to an AWS S3 bucket by configuring the <PyObject section="libraries" module="dagster_aws" object="s3.S3ComputeLogManager" /> module.
 
 You are also able to stream partial compute log files by configuring the log upload interval (in seconds) using the `upload_interval` parameter.

docs/docs/deployment/dagster-plus/management/managing-compute-logs-and-error-messages.md

@@ -19,7 +19,7 @@ Dagster's compute logs are handled by the configured [`ComputeLogManager`](/api/
 
 ### Writing to your own S3 bucket
 
-If using the Kubernetes agent, you can instead forward logs to your own S3 bucket by using the [`S3ComputeLogManager`](/api/libraries/dagster-aws#dagster_aws.s3.S3ComputeLogManager).
+If using the Kubernetes agent, you can instead forward logs to your own S3 bucket by using the [`S3ComputeLogManager`](/integrations/libraries/dagster-aws#dagster_aws.s3.S3ComputeLogManager).
 
 You can configure the `S3ComputeLogManager` in your [`dagster.yaml` file](/deployment/dagster-plus/management/customizing-agent-settings):
 

docs/docs/deployment/execution/run-monitoring.md

@@ -76,8 +76,8 @@ If a run worker crashes, the run it's managing can hang. The monitoring daemon c
 
 This feature is currently only supported when using:
 
-- [`K8sRunLauncher`](/api/libraries/dagster-k8s#dagster_k8s.K8sRunLauncher) with the [`k8s_job_executor`](/api/libraries/dagster-k8s#dagster_k8s.k8s_job_executor)
-- [`DockerRunLauncher`](/api/libraries/dagster-docker#dagster_docker.DockerRunLauncher) with the [`docker_executor`](/api/libraries/dagster-docker#dagster_docker.docker_executor)
+- [`K8sRunLauncher`](/integrations/libraries/dagster-k8s#dagster_k8s.K8sRunLauncher) with the [`k8s_job_executor`](/integrations/libraries/dagster-k8s#dagster_k8s.k8s_job_executor)
+- [`DockerRunLauncher`](/integrations/libraries/dagster-docker#dagster_docker.DockerRunLauncher) with the [`docker_executor`](/integrations/libraries/dagster-docker#dagster_docker.docker_executor)
 
 The monitoring daemon handles these by performing health checks on the run workers. If a failure is detected, the daemon can launch a new run worker which resumes execution of the existing run. The run worker crash will be show in the event log, and the run will continue to completion. If the run worker continues to crash, the daemon will mark the run as failed after the configured number of attempts.
 

docs/docs/deployment/oss/oss-instance-configuration.md

@@ -100,11 +100,11 @@ To use a SQLite database for storage, configure `storage.sqlite` in `dagster.yam
 
 :::note
 
-To use Postgres storage, you'll need to install the [dagster-postgres](/api/libraries/dagster-postgres) library.
+To use Postgres storage, you'll need to install the [dagster-postgres](/integrations/libraries/dagster-postgres) library.
 
 :::
 
-To use a [PostgreSQL database](/api/libraries/dagster-postgres) for storage, configure `storage.postgres` in `dagster.yaml`:
+To use a [PostgreSQL database](/integrations/libraries/dagster-postgres) for storage, configure `storage.postgres` in `dagster.yaml`:
 
 <CodeExample
   path="docs_snippets/docs_snippets/deploying/dagster_instance/dagster.yaml"
@@ -119,11 +119,11 @@ To use a [PostgreSQL database](/api/libraries/dagster-postgres) for storage, con
 
 :::note
 
-To use MySQL storage, you'll need to install the [dagster-mysql](/api/libraries/dagster-mysql) library.
+To use MySQL storage, you'll need to install the [dagster-mysql](/integrations/libraries/dagster-mysql) library.
 
 :::
 
-To use a [MySQL database](/api/libraries/dagster-mysql) for storage, configure `storage.mysql` in `dagster.yaml`:
+To use a [MySQL database](/integrations/libraries/dagster-mysql) for storage, configure `storage.mysql` in `dagster.yaml`:
 
 <CodeExample
   path="docs_snippets/docs_snippets/deploying/dagster_instance/dagster.yaml"

docs/docs/examples/full-pipelines/rag/sources.md

@@ -12,7 +12,7 @@ To begin we need our specific context. Our RAG system will combine two different
 
 ## GitHub
 
-To retrieve data from GitHub, we are going to borrow code from the [dagster-open-platform](https://github.com/dagster-io/dagster-open-platform). The open platform repository shows how we use Dagster internally, and GitHub is one of the data sources we use, and we wrote a resource to manage pulling that data. The [`GithubResource`](/api/libraries/dagster-github#resources) allows us to query GitHub using GraphQL. We are most interested in issues and discussions, so our resource will have two methods to retrieve that information over a given date range:
+To retrieve data from GitHub, we are going to borrow code from the [dagster-open-platform](https://github.com/dagster-io/dagster-open-platform). The open platform repository shows how we use Dagster internally, and GitHub is one of the data sources we use, and we wrote a resource to manage pulling that data. The [`GithubResource`](/integrations/libraries/dagster-github#resources) allows us to query GitHub using GraphQL. We are most interested in issues and discussions, so our resource will have two methods to retrieve that information over a given date range:
 
 <CodeExample
   path="docs_projects/project_ask_ai_dagster/src/project_ask_ai_dagster/defs/github.py"

docs/docs/guides/build/external-pipelines/aws/aws-ecs-pipeline.md

@@ -8,7 +8,7 @@ import ScaffoldProject from '@site/docs/partials/\_ScaffoldProject.md';
 
 This article covers how to use [Dagster Pipes](/guides/build/external-pipelines) with [AWS ECS](https://aws.amazon.com/ecs).
 
-The [dagster-aws](/api/libraries/dagster-aws) integration library provides the <PyObject section="libraries" object="pipes.PipesECSClient" module="dagster_aws" /> resource which can be used to launch AWS ECS tasks from Dagster assets and ops. Dagster can receive regular events like logs, asset checks, or asset materializations from jobs launched with this client. Using it requires minimal code changes on the task side.
+The [dagster-aws](/integrations/libraries/dagster-aws) integration library provides the <PyObject section="libraries" object="pipes.PipesECSClient" module="dagster_aws" /> resource which can be used to launch AWS ECS tasks from Dagster assets and ops. Dagster can receive regular events like logs, asset checks, or asset materializations from jobs launched with this client. Using it requires minimal code changes on the task side.
 
 ## Prerequisites
 

docs/docs/guides/build/external-pipelines/aws/aws-emr-containers-pipeline.md

@@ -11,7 +11,7 @@ import ScaffoldProject from '@site/docs/partials/\_ScaffoldProject.md';
 
 This tutorial gives a short overview on how to use [Dagster Pipes](/guides/build/external-pipelines) with [AWS EMR on EKS](https://aws.amazon.com/emr/features/eks) (the corresponding AWS API is called `emr-containers`).
 
-The [dagster-aws](/api/libraries/dagster-aws) integration library provides the <PyObject section="libraries" object="pipes.PipesEMRContainersClient" module="dagster_aws" /> resource, which can be used to launch EMR jobs from Dagster assets and ops. Dagster can receive regular events such as logs, asset checks, or asset materializations from jobs launched with this client. Using it requires minimal code changes to your EMR jobs.
+The [dagster-aws](/integrations/libraries/dagster-aws) integration library provides the <PyObject section="libraries" object="pipes.PipesEMRContainersClient" module="dagster_aws" /> resource, which can be used to launch EMR jobs from Dagster assets and ops. Dagster can receive regular events such as logs, asset checks, or asset materializations from jobs launched with this client. Using it requires minimal code changes to your EMR jobs.
 
 ## Prerequisites
 

docs/docs/guides/build/external-pipelines/aws/aws-emr-pipeline.md

@@ -8,7 +8,7 @@ import ScaffoldProject from '@site/docs/partials/\_ScaffoldProject.md';
 
 This article covers how to use [Dagster Pipes](/guides/build/external-pipelines) with [AWS EMR](https://aws.amazon.com/emr).
 
-The [dagster-aws](/api/libraries/dagster-aws) integration library provides the <PyObject section="libraries" object="pipes.PipesEMRClient" module="dagster_aws" /> resource, which can be used to launch AWS EMR jobs from Dagster assets and ops. Dagster can receive regular events such as logs, asset checks, or asset materializations from jobs launched with this client. Using it requires minimal code changes to your EMR jobs.
+The [dagster-aws](/integrations/libraries/dagster-aws) integration library provides the <PyObject section="libraries" object="pipes.PipesEMRClient" module="dagster_aws" /> resource, which can be used to launch AWS EMR jobs from Dagster assets and ops. Dagster can receive regular events such as logs, asset checks, or asset materializations from jobs launched with this client. Using it requires minimal code changes to your EMR jobs.
 
 
 ## Prerequisites

docs/docs/guides/build/external-pipelines/aws/aws-emr-serverless-pipeline.md

@@ -8,7 +8,7 @@ import ScaffoldProject from '@site/docs/partials/\_ScaffoldProject.md';
 
 This article covers how to use [Dagster Pipes](/guides/build/external-pipelines) with [AWS EMR Serverless](https://docs.aws.amazon.com/emr/latest/EMR-Serverless-UserGuide/getting-started.html).
 
-The [dagster-aws](/api/libraries/dagster-aws) integration library provides the <PyObject section="libraries" object="pipes.PipesEMRServerlessClient" module="dagster_aws" /> resource, which can be used to launch AWS EMR Serverless jobs from Dagster assets and ops. Dagster can receive regular events such as logs, asset checks, or asset materializations from jobs launched with this client. Using it requires minimal code changes to your EMR jobs.
+The [dagster-aws](/integrations/libraries/dagster-aws) integration library provides the <PyObject section="libraries" object="pipes.PipesEMRServerlessClient" module="dagster_aws" /> resource, which can be used to launch AWS EMR Serverless jobs from Dagster assets and ops. Dagster can receive regular events such as logs, asset checks, or asset materializations from jobs launched with this client. Using it requires minimal code changes to your EMR jobs.
 
 ## Prerequisites
 

docs/docs/guides/build/external-pipelines/aws/aws-glue-pipeline.md

@@ -10,7 +10,7 @@ import ScaffoldProject from '@site/docs/partials/\_ScaffoldProject.md';
 
 This article covers how to use [Dagster Pipes](/guides/build/external-pipelines) with [AWS Glue](https://aws.amazon.com/glue).
 
-The [dagster-aws](/api/libraries/dagster-aws) integration library provides the <PyObject section="libraries" object="pipes.PipesGlueClient" module="dagster_aws" /> resource which can be used to launch AWS Glue jobs from Dagster assets and ops. Dagster can receive regular events like logs, asset checks, or asset materializations from jobs launched with this client. Using it requires minimal code changes on the job side.
+The [dagster-aws](/integrations/libraries/dagster-aws) integration library provides the <PyObject section="libraries" object="pipes.PipesGlueClient" module="dagster_aws" /> resource which can be used to launch AWS Glue jobs from Dagster assets and ops. Dagster can receive regular events like logs, asset checks, or asset materializations from jobs launched with this client. Using it requires minimal code changes on the job side.
 
 ## Prerequisites