External MongoDB
The platform uses MongoDB as its document store. Two options are supported, and the choice must be made and documented before deployment; an undecided option blocks environment configuration.
| Option | You Provide | DynamoAI Provides |
|---|---|---|
| Customer-provided managed endpoint (for example Atlas) | Connection configuration, credentials, and network access (IP allow-list or private connectivity), tested from the cluster | Platform configuration against your endpoint |
| In-cluster MongoDB | Persistent storage (a default StorageClass that can provision PersistentVolumes) | The MongoDB deployment, installed with the platform |
Requirements for a Managed Endpoint
- Connection configuration and credentials delivered through your secret management path (as Kubernetes Secrets, never embedded in Helm values).
- Network access from the cluster: an IP allow-list entry or private connectivity (peering or private endpoint).
- The endpoint reachable from inside the cluster, verified before the deployment window:
Verify connectivity from the cluster
kubectl run -it mongosh --rm --image=mongo -- mongosh "<connection-string>" --eval "db.runCommand({ping: 1})"
Requirements for In-Cluster MongoDB
- A CSI storage driver providing a default StorageClass (see the Kubernetes cluster dependency).
- Persistent storage configured for the MongoDB deployment.