diff --git a/content/en/docs/edp/deployment/otc/_index.md b/content/en/docs/edp/deployment/otc/_index.md
index fc88a72..d19d1b8 100644
--- a/content/en/docs/edp/deployment/otc/_index.md
+++ b/content/en/docs/edp/deployment/otc/_index.md
@@ -62,6 +62,30 @@ Services and workloads are primarily provisioned using Terraform.
-
+## Managed Services
+EDP instances heavily utilize Open Telekom Cloud's (OTC) managed services to
+simplify operations, enhance reliability, and allow the team to focus on
+application development rather than infrastructure management. The core
+components of each deployed instance run within the managed Kubernetes service.
-TODO: EDP <-> managed services
+The following managed services are integral to EDP deployments:
+
+- **Cloud Container Engine (CCE)**: The managed Kubernetes service that forms
+ the foundation of each EDP instance, hosting all containerized core components
+ and workloads.
+- **Relational Database Service (RDS) for PostgreSQL**: Provides scalable and
+ reliable PostgreSQL database instances, primarily used by applications such as
+ Forgejo.
+- **Object Storage Service (OBS)**: Offers S3-compatible object storage for
+ storing backups, application data (e.g., for Forgejo), and other static
+ assets.
+- **Cloud Search Service (CSS)**: An optional service providing robust search
+ capabilities, specifically used for Forgejo's indexing and search
+ functionalities.
+- **Networking**: Essential networking components, including Virtual Private
+ Clouds (VPCs), Load Balancers, and DNS management, which facilitate secure and
+ efficient communication within the EDP ecosystem.
+- **Cloud Backup and Recovery (CBR)**: Vaults are configured to automatically
+ back up persistent volumes created by CCE instances, ensuring data resilience
+ and disaster recovery readiness.
diff --git a/content/en/docs/edp/deployment/otc/instances.md b/content/en/docs/edp/deployment/otc/instances.md
index 756350d..6b6d51d 100644
--- a/content/en/docs/edp/deployment/otc/instances.md
+++ b/content/en/docs/edp/deployment/otc/instances.md
@@ -84,6 +84,10 @@ Terraform lifecycle, offering `plan`, `deploy`, and `destroy` operations.
is intentionally retained within the `stacks-instances` repository for
historical tracking or potential re-creation.
+> NOTE: When deploying a new instance of EDP it is bootstrapped with random
+> secrets including admin logins. Initial admin credentials for individual
+> components are printed in workflow output. They can be retrieved from the
+> secrets withing Kubernetes at a later point in time.
