From f6555f973069bb4c47aba9d0c87fba5e352b3735 Mon Sep 17 00:00:00 2001 From: agustinoli Date: Wed, 1 Jul 2026 14:29:07 -0300 Subject: [PATCH 1/7] docs(tutorials): stop implying Grafana alert setup (SLEAK-5896) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Per Mati's review, the cost-vs-risk intro no longer says "configure alerts in Grafana" — that reads as a how-to we don't cover. It now points to reviewing latency/error-rate metrics that aren't included by default. Also fixed the Section 6 anchor link, which was already broken (missing "y alertas"/"and Alerts" suffix). --- content/tutorials/en/environment-exhaustive-testing-guide.mdx | 2 +- content/tutorials/es/environment-exhaustive-testing-guide.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/tutorials/en/environment-exhaustive-testing-guide.mdx b/content/tutorials/en/environment-exhaustive-testing-guide.mdx index 2f3657cf3..a35d615d2 100644 --- a/content/tutorials/en/environment-exhaustive-testing-guide.mdx +++ b/content/tutorials/en/environment-exhaustive-testing-guide.mdx @@ -22,7 +22,7 @@ A comprehensive checklist of tests to validate that your application is fully fu Each section in this guide has a cost: preparation time, infrastructure overhead, and development effort. Before running a section, evaluate whether the risk it addresses is real for your application and whether the investment is proportional. -Sometimes the same risk can be managed at a lower cost. Instead of building a full load-testing suite, for example, you could configure latency and error-rate alerts in Grafana that notify you before degraded performance reaches your users. Observability and alerting are covered in [Section 6 — Observability](#section-6-observability). +Sometimes the same risk can be managed at a lower cost. Instead of building a full load-testing suite, for example, you could check latency and error-rate metrics in Grafana that we don't include by default, to catch degraded performance before it reaches your users. Observability is covered in [Section 6 — Observability and Alerts](#section-6-observability-and-alerts). Think of this guide as a menu. Pick the sections that match your risk tolerance and application criticality — you don't have to run everything. diff --git a/content/tutorials/es/environment-exhaustive-testing-guide.mdx b/content/tutorials/es/environment-exhaustive-testing-guide.mdx index 435fbfce5..aab7dd098 100644 --- a/content/tutorials/es/environment-exhaustive-testing-guide.mdx +++ b/content/tutorials/es/environment-exhaustive-testing-guide.mdx @@ -22,7 +22,7 @@ Un checklist completo de pruebas para validar que tu aplicación funciona correc Cada sección de esta guía tiene un costo: tiempo de preparación, overhead de infraestructura y esfuerzo de desarrollo. Antes de ejecutar una sección, evaluá si el riesgo que cubre es real para tu aplicación y si la inversión es proporcional. -A veces el mismo riesgo se puede mitigar de forma más económica. En lugar de montar un stack completo de load testing, por ejemplo, podés configurar alertas de latencia y tasa de errores en Grafana que te avisen antes de que el rendimiento degradado llegue a tus usuarios. La observabilidad y las alertas se cubren en la [Sección 6 — Observabilidad](#sección-6-observabilidad). +A veces el mismo riesgo se puede mitigar de forma más económica. En lugar de montar un stack completo de load testing, por ejemplo, podés revisar en Grafana métricas de latencia y tasa de errores que no incluimos por defecto, para detectar el rendimiento degradado antes de que llegue a tus usuarios. La observabilidad se cubre en la [Sección 6 — Observabilidad y alertas](#sección-6-observabilidad-y-alertas). Pensá en esta guía como un menú. Elegí las secciones que correspondan a tu tolerancia al riesgo y la criticidad de tu aplicación — no tenés que correrlo todo. From 254d3a4adf054a1a99b3f8dca56beb680a8fe597 Mon Sep 17 00:00:00 2001 From: agustinoli Date: Wed, 1 Jul 2026 14:33:03 -0300 Subject: [PATCH 2/7] docs(dependency): clarify RDS at-rest encryption is opt-in (SLEAK-5875) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The bot was answering that databases are encrypted with KMS at rest. storage_encrypted defaults to False in the RDS Pulumi module (core/apps/crm/modules/dependency/aws/rds.py) — it's only on if a KMS key is configured at creation time. Added that as a bullet next to the existing SSL/TLS note in ES, and ported the whole "Dependency Access" section to EN, which didn't have it at all. --- content/docs/en/project/dependency/index.mdx | 64 ++++++++++++++++++++ content/docs/es/project/dependency/index.mdx | 1 + 2 files changed, 65 insertions(+) diff --git a/content/docs/en/project/dependency/index.mdx b/content/docs/en/project/dependency/index.mdx index 8b8e20cc3..8232df7fa 100644 --- a/content/docs/en/project/dependency/index.mdx +++ b/content/docs/en/project/dependency/index.mdx @@ -106,3 +106,67 @@ To move forward choose between the following guides. [Memcached](/docs/project/dependency/memcached-aws). [OpenSearch](/docs/project/dependency/opensearch-aws). [SQS](/docs/project/dependency/sqs-aws). + +## Dependency Access + +Dependency access refers to the security and connectivity mechanisms that let your application's workloads interact securely with external dependencies. SleakOps automatically manages these access patterns to ensure secure communication between your services and their dependencies. + +### Access Management + +#### Automatic Service Account Configuration +When you create a dependency, SleakOps automatically: +- **Creates IAM roles** with appropriate permissions for the specific dependency type +- **Configures service accounts** in your Kubernetes namespace +- **Establishes secure connections** between your workloads and the dependency +- **Manages credentials** through Kubernetes secrets and IAM roles + +#### Network Security +- **VPC Integration**: Dependencies are created inside your project's VPC for secure network access +- **Security Groups**: Automatically configured to allow the traffic needed between services +- **Private Endpoints**: Dependencies use private endpoints when available to minimize exposure + +### Access Patterns + +#### Database Access +For database dependencies (MySQL, PostgreSQL, etc.): +- **Connection Strings**: Automatically generated and stored as Kubernetes secrets +- **Authentication**: Managed through IAM roles and database-specific credentials +- **SSL/TLS**: Encrypted connections are configured by default +- **At-Rest Encryption**: Not enabled by default. You can turn it on by configuring a KMS key when you create the dependency +- **Connection Pooling**: Optimized connection management for better performance + +#### Cache Access +For caching services (Redis, Memcached): +- **Endpoint Configuration**: Automatically configured in your application's environment +- **Authentication**: Secure access through IAM roles and service-specific credentials +- **Network Policies**: Access restricted to authorized workloads only + +#### Storage Access +For storage services (S3, etc.): +- **Bucket Policies**: Automatically configured with least-privilege access +- **IAM Permissions**: Service accounts receive only the permissions they need +- **Access Keys**: Managed through AWS IAM roles for greater security + +### Security Best Practices + +#### Principle of Least Privilege +- **Minimal Permissions**: Dependencies receive only the minimum required permissions +- **Resource-Specific Access**: Access is scoped to specific resources whenever possible +- **Regular Audits**: SleakOps provides tools to review and audit dependency access + +#### Credential Management +- **Automatic Rotation**: Credentials are rotated automatically when possible +- **Secure Storage**: All credentials are stored as Kubernetes secrets +- **No Hardcoded Secrets**: Applications access dependencies through environment variables + +:::info Access Monitoring +SleakOps provides monitoring and logging capabilities to track dependency access patterns, helping you identify potential security issues and optimize performance. +::: + +:::tip Troubleshooting Access Issues +If you run into access issues with dependencies: +1. Check the dependency's status in the SleakOps console +2. Confirm your workload has the correct service account +3. Review the IAM role permissions for the dependency +4. Verify network connectivity and security group configurations +::: diff --git a/content/docs/es/project/dependency/index.mdx b/content/docs/es/project/dependency/index.mdx index 3783b5588..cd0b2e36f 100644 --- a/content/docs/es/project/dependency/index.mdx +++ b/content/docs/es/project/dependency/index.mdx @@ -134,6 +134,7 @@ Para dependencias de base de datos (MySQL, PostgreSQL, etc.): - **Cadenas de Conexión**: Generadas automáticamente y almacenadas como secrets de Kubernetes - **Autenticación**: Gestionada a través de roles IAM y credenciales específicas de la base de datos - **SSL/TLS**: Las conexiones encriptadas se configuran por defecto +- **Encriptación at-rest**: No está habilitada por defecto. Podés activarla configurando una KMS key al crear la dependencia - **Connection Pooling**: Gestión optimizada de conexiones para mejor rendimiento #### Acceso a Cache From 918f2837b6697007d5c06d1151a3d6e806f4ba86 Mon Sep 17 00:00:00 2001 From: agustinoli Date: Wed, 1 Jul 2026 14:35:10 -0300 Subject: [PATCH 3/7] docs(tutorials): disambiguate metrics-vs-alerting wording (SLEAK-5896) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Section 6 already says Grafana dashboards include latency and error rate by default, so the previous phrasing ("metrics we don't include by default") contradicted it. What's not on by default is alerting on those metrics — reworded to say that instead. --- content/tutorials/en/environment-exhaustive-testing-guide.mdx | 2 +- content/tutorials/es/environment-exhaustive-testing-guide.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/tutorials/en/environment-exhaustive-testing-guide.mdx b/content/tutorials/en/environment-exhaustive-testing-guide.mdx index a35d615d2..888c68371 100644 --- a/content/tutorials/en/environment-exhaustive-testing-guide.mdx +++ b/content/tutorials/en/environment-exhaustive-testing-guide.mdx @@ -22,7 +22,7 @@ A comprehensive checklist of tests to validate that your application is fully fu Each section in this guide has a cost: preparation time, infrastructure overhead, and development effort. Before running a section, evaluate whether the risk it addresses is real for your application and whether the investment is proportional. -Sometimes the same risk can be managed at a lower cost. Instead of building a full load-testing suite, for example, you could check latency and error-rate metrics in Grafana that we don't include by default, to catch degraded performance before it reaches your users. Observability is covered in [Section 6 — Observability and Alerts](#section-6-observability-and-alerts). +Sometimes the same risk can be managed at a lower cost. Instead of building a full load-testing suite, for example, you could keep an eye on the latency and error-rate metrics in Grafana — we don't set up alerting on those by default, so it's on you to check them proactively and catch degraded performance before it reaches your users. Observability is covered in [Section 6 — Observability and Alerts](#section-6-observability-and-alerts). Think of this guide as a menu. Pick the sections that match your risk tolerance and application criticality — you don't have to run everything. diff --git a/content/tutorials/es/environment-exhaustive-testing-guide.mdx b/content/tutorials/es/environment-exhaustive-testing-guide.mdx index aab7dd098..e7fe2e85e 100644 --- a/content/tutorials/es/environment-exhaustive-testing-guide.mdx +++ b/content/tutorials/es/environment-exhaustive-testing-guide.mdx @@ -22,7 +22,7 @@ Un checklist completo de pruebas para validar que tu aplicación funciona correc Cada sección de esta guía tiene un costo: tiempo de preparación, overhead de infraestructura y esfuerzo de desarrollo. Antes de ejecutar una sección, evaluá si el riesgo que cubre es real para tu aplicación y si la inversión es proporcional. -A veces el mismo riesgo se puede mitigar de forma más económica. En lugar de montar un stack completo de load testing, por ejemplo, podés revisar en Grafana métricas de latencia y tasa de errores que no incluimos por defecto, para detectar el rendimiento degradado antes de que llegue a tus usuarios. La observabilidad se cubre en la [Sección 6 — Observabilidad y alertas](#sección-6-observabilidad-y-alertas). +A veces el mismo riesgo se puede mitigar de forma más económica. En lugar de montar un stack completo de load testing, por ejemplo, podés seguirle el pulso a las métricas de latencia y tasa de errores en Grafana — no configuramos alertas sobre ellas por defecto, así que queda en vos revisarlas de forma proactiva y detectar el rendimiento degradado antes de que llegue a tus usuarios. La observabilidad se cubre en la [Sección 6 — Observabilidad y alertas](#sección-6-observabilidad-y-alertas). Pensá en esta guía como un menú. Elegí las secciones que correspondan a tu tolerancia al riesgo y la criticidad de tu aplicación — no tenés que correrlo todo. From abf63ab7e518f9c34d1f6c702e01310319930662 Mon Sep 17 00:00:00 2001 From: agustinoli Date: Wed, 1 Jul 2026 14:53:56 -0300 Subject: [PATCH 4/7] docs(dependency): update at-rest encryption default per ae8c16d1 (SLEAK-5875) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The previous wording described the pre-06/2026 behavior. Since ae8c16d1 (RDS improvements), storageEncrypted defaults to true in the creation schema for MySQL/PostgreSQL/MariaDB/Oracle, and Aurora has always hardcoded storage_encrypted=True with no opt-out. Only dependencies created before that change may lack the flag — called that out instead of stating a blanket "not encrypted by default". --- content/docs/en/project/dependency/index.mdx | 2 +- content/docs/es/project/dependency/index.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/docs/en/project/dependency/index.mdx b/content/docs/en/project/dependency/index.mdx index 8232df7fa..152437726 100644 --- a/content/docs/en/project/dependency/index.mdx +++ b/content/docs/en/project/dependency/index.mdx @@ -132,7 +132,7 @@ For database dependencies (MySQL, PostgreSQL, etc.): - **Connection Strings**: Automatically generated and stored as Kubernetes secrets - **Authentication**: Managed through IAM roles and database-specific credentials - **SSL/TLS**: Encrypted connections are configured by default -- **At-Rest Encryption**: Not enabled by default. You can turn it on by configuring a KMS key when you create the dependency +- **At-Rest Encryption**: Enabled by default on new dependencies — you can turn it off or configure your own KMS key when you create it. Aurora (PostgreSQL/MySQL) is always encrypted, with no way to opt out. If the dependency was created before this improvement shipped, check the specific case: it may not be encrypted - **Connection Pooling**: Optimized connection management for better performance #### Cache Access diff --git a/content/docs/es/project/dependency/index.mdx b/content/docs/es/project/dependency/index.mdx index cd0b2e36f..4b9d8181b 100644 --- a/content/docs/es/project/dependency/index.mdx +++ b/content/docs/es/project/dependency/index.mdx @@ -134,7 +134,7 @@ Para dependencias de base de datos (MySQL, PostgreSQL, etc.): - **Cadenas de Conexión**: Generadas automáticamente y almacenadas como secrets de Kubernetes - **Autenticación**: Gestionada a través de roles IAM y credenciales específicas de la base de datos - **SSL/TLS**: Las conexiones encriptadas se configuran por defecto -- **Encriptación at-rest**: No está habilitada por defecto. Podés activarla configurando una KMS key al crear la dependencia +- **Encriptación at-rest**: Habilitada por defecto en dependencias nuevas — podés desactivarla o configurar tu propia KMS key al crearla. Aurora (PostgreSQL/MySQL) siempre está encriptada, sin opción de desactivarlo. Si la dependencia ya existía antes de esta mejora, verificá el caso puntual: puede no estar encriptada - **Connection Pooling**: Gestión optimizada de conexiones para mejor rendimiento #### Acceso a Cache From db8fe9d85d380adbe7a2a78a46a908971e389dcd Mon Sep 17 00:00:00 2001 From: agustinoli Date: Wed, 1 Jul 2026 14:57:22 -0300 Subject: [PATCH 5/7] docs(dependency): split dense encryption bullet, fix missing EOF newline (SLEAK-5875) --- content/docs/en/project/dependency/index.mdx | 5 ++++- content/docs/es/project/dependency/index.mdx | 7 +++++-- 2 files changed, 9 insertions(+), 3 deletions(-) diff --git a/content/docs/en/project/dependency/index.mdx b/content/docs/en/project/dependency/index.mdx index 152437726..672407a72 100644 --- a/content/docs/en/project/dependency/index.mdx +++ b/content/docs/en/project/dependency/index.mdx @@ -132,7 +132,10 @@ For database dependencies (MySQL, PostgreSQL, etc.): - **Connection Strings**: Automatically generated and stored as Kubernetes secrets - **Authentication**: Managed through IAM roles and database-specific credentials - **SSL/TLS**: Encrypted connections are configured by default -- **At-Rest Encryption**: Enabled by default on new dependencies — you can turn it off or configure your own KMS key when you create it. Aurora (PostgreSQL/MySQL) is always encrypted, with no way to opt out. If the dependency was created before this improvement shipped, check the specific case: it may not be encrypted +- **At-Rest Encryption**: Enabled by default on new dependencies + - You can turn it off or configure your own KMS key when you create it + - Aurora (PostgreSQL/MySQL) is always encrypted, with no way to opt out + - If the dependency was created before this improvement shipped, check the specific case: it may not be encrypted - **Connection Pooling**: Optimized connection management for better performance #### Cache Access diff --git a/content/docs/es/project/dependency/index.mdx b/content/docs/es/project/dependency/index.mdx index 4b9d8181b..9b93d4f23 100644 --- a/content/docs/es/project/dependency/index.mdx +++ b/content/docs/es/project/dependency/index.mdx @@ -134,7 +134,10 @@ Para dependencias de base de datos (MySQL, PostgreSQL, etc.): - **Cadenas de Conexión**: Generadas automáticamente y almacenadas como secrets de Kubernetes - **Autenticación**: Gestionada a través de roles IAM y credenciales específicas de la base de datos - **SSL/TLS**: Las conexiones encriptadas se configuran por defecto -- **Encriptación at-rest**: Habilitada por defecto en dependencias nuevas — podés desactivarla o configurar tu propia KMS key al crearla. Aurora (PostgreSQL/MySQL) siempre está encriptada, sin opción de desactivarlo. Si la dependencia ya existía antes de esta mejora, verificá el caso puntual: puede no estar encriptada +- **Encriptación at-rest**: Habilitada por defecto en dependencias nuevas + - Podés desactivarla o configurar tu propia KMS key al crearla + - Aurora (PostgreSQL/MySQL) siempre está encriptada, sin opción de desactivarlo + - Si la dependencia ya existía antes de esta mejora, verificá el caso puntual: puede no estar encriptada - **Connection Pooling**: Gestión optimizada de conexiones para mejor rendimiento #### Acceso a Cache @@ -171,4 +174,4 @@ Si encuentras problemas de acceso con dependencias: 2. Confirma que tu carga de trabajo tiene la service account correcta 3. Revisa los permisos del rol IAM para la dependencia 4. Verifica la conectividad de red y configuraciones de security groups -::: \ No newline at end of file +::: From a07db836ed456dd88308c82d878f5353ac55f153 Mon Sep 17 00:00:00 2001 From: agustinoli Date: Wed, 1 Jul 2026 15:58:56 -0300 Subject: [PATCH 6/7] docs(tutorials): keep monitoring guidance tool-agnostic (SLEAK-5896) Cost-vs-risk intro now says "any monitoring stack" instead of naming Grafana specifically. Trimmed the default metrics list in the Observability section to what dashboards reliably show out of the box. --- content/tutorials/en/environment-exhaustive-testing-guide.mdx | 4 ++-- content/tutorials/es/environment-exhaustive-testing-guide.mdx | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/content/tutorials/en/environment-exhaustive-testing-guide.mdx b/content/tutorials/en/environment-exhaustive-testing-guide.mdx index 888c68371..97da639ca 100644 --- a/content/tutorials/en/environment-exhaustive-testing-guide.mdx +++ b/content/tutorials/en/environment-exhaustive-testing-guide.mdx @@ -22,7 +22,7 @@ A comprehensive checklist of tests to validate that your application is fully fu Each section in this guide has a cost: preparation time, infrastructure overhead, and development effort. Before running a section, evaluate whether the risk it addresses is real for your application and whether the investment is proportional. -Sometimes the same risk can be managed at a lower cost. Instead of building a full load-testing suite, for example, you could keep an eye on the latency and error-rate metrics in Grafana — we don't set up alerting on those by default, so it's on you to check them proactively and catch degraded performance before it reaches your users. Observability is covered in [Section 6 — Observability and Alerts](#section-6-observability-and-alerts). +Sometimes the same risk can be managed at a lower cost. Instead of building a full load-testing suite, for example, any monitoring stack you already have in place can let you act proactively before performance degrades and reaches your users. Observability is covered in [Section 6 — Observability and Alerts](#section-6-observability-and-alerts). Think of this guide as a menu. Pick the sections that match your risk tolerance and application criticality — you don't have to run everything. @@ -377,7 +377,7 @@ Observability is not optional — if something goes wrong after the migration, y ### Metrics in Grafana 1. Open **Grafana** (available as an addon in your Cluster) -2. Verify that dashboards exist for your application showing at minimum: CPU usage, memory usage, requests/sec, error rate, and response latency +2. Verify that dashboards exist for your application showing at minimum: CPU usage and memory usage 3. **Pass:** All metrics are populated with recent data 4. **Fail:** Metrics are missing or show "No data" — check that Prometheus is scraping your application's metrics endpoint diff --git a/content/tutorials/es/environment-exhaustive-testing-guide.mdx b/content/tutorials/es/environment-exhaustive-testing-guide.mdx index e7fe2e85e..186a619bc 100644 --- a/content/tutorials/es/environment-exhaustive-testing-guide.mdx +++ b/content/tutorials/es/environment-exhaustive-testing-guide.mdx @@ -22,7 +22,7 @@ Un checklist completo de pruebas para validar que tu aplicación funciona correc Cada sección de esta guía tiene un costo: tiempo de preparación, overhead de infraestructura y esfuerzo de desarrollo. Antes de ejecutar una sección, evaluá si el riesgo que cubre es real para tu aplicación y si la inversión es proporcional. -A veces el mismo riesgo se puede mitigar de forma más económica. En lugar de montar un stack completo de load testing, por ejemplo, podés seguirle el pulso a las métricas de latencia y tasa de errores en Grafana — no configuramos alertas sobre ellas por defecto, así que queda en vos revisarlas de forma proactiva y detectar el rendimiento degradado antes de que llegue a tus usuarios. La observabilidad se cubre en la [Sección 6 — Observabilidad y alertas](#sección-6-observabilidad-y-alertas). +A veces el mismo riesgo se puede mitigar de forma más económica. En lugar de montar un stack completo de load testing, por ejemplo, cualquier stack de monitoreo que ya tengas te permite accionar de forma proactiva antes de que el rendimiento se degrade y llegue a tus usuarios. La observabilidad se cubre en la [Sección 6 — Observabilidad y alertas](#sección-6-observabilidad-y-alertas). Pensá en esta guía como un menú. Elegí las secciones que correspondan a tu tolerancia al riesgo y la criticidad de tu aplicación — no tenés que correrlo todo. @@ -377,7 +377,7 @@ La observabilidad no es opcional — si algo falla después de la migración, ne ### Métricas en Grafana 1. Abrí **Grafana** (disponible como addon en tu Cluster) -2. Verificá que existan dashboards para tu aplicación mostrando como mínimo: uso de CPU, uso de memoria, requests/seg, tasa de errores, y latencia de respuesta +2. Verificá que existan dashboards para tu aplicación mostrando como mínimo: uso de CPU y uso de memoria 3. **Pasa:** Todas las métricas están pobladas con datos recientes 4. **Falla:** Faltan métricas o muestran "No data" — verificá que Prometheus esté scrapeando el endpoint de métricas de tu aplicación From 3972cfa9b3b54093869a4189eebdb48815732962 Mon Sep 17 00:00:00 2001 From: agustinoli Date: Wed, 1 Jul 2026 16:15:59 -0300 Subject: [PATCH 7/7] fix(tutorials): fix broken anchor link in ES postgresql-dump-restore The link pointed to the English anchor slug (#how-do-i-create-a-postgresql-database-dump) on a page whose heading is in Spanish. Updated it to the actual generated slug. --- content/tutorials/es/postgresql-dump-restore.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/tutorials/es/postgresql-dump-restore.mdx b/content/tutorials/es/postgresql-dump-restore.mdx index d71fdcc44..f270f2ab2 100644 --- a/content/tutorials/es/postgresql-dump-restore.mdx +++ b/content/tutorials/es/postgresql-dump-restore.mdx @@ -40,7 +40,7 @@ Ejecutá este comando desde cualquier máquina con acceso de red a la base de da pg_dump -h POSTGRESQL_ADDRESS -U POSTGRESQL_USERNAME -W -Fc -f dump.dump ``` -Para opciones detalladas, consultá la [documentación de la Dependency PostgreSQL de SleakOps](/docs/project/dependency/postgresql-aws#how-do-i-create-a-postgresql-database-dump). +Para opciones detalladas, consultá la [documentación de la Dependency PostgreSQL de SleakOps](/docs/project/dependency/postgresql-aws#cómo-puedo-crear-un-backup-dump-de-mi-base-de-datos-postgresql). ### Paso 2 — Escalar la instancia RDS destino