Skip to main content

Deployment and security

Find answers to common questions about supported deployment platforms, available methods, and security incident handling for Self-Deployed Runtime.

Did you know?

Some capabilities shown here may require additional enablement or licensing. Contact your Atlan representative for details.

What platforms are supported for running OCI images?​

Self-Deployed Runtime images run on any OCI-compatible runtime, including Podman, Docker, ECS, and Kubernetes. Docker Compose and Helm charts are provided for easier deployment.

Does Self-Deployed Runtime require stateful storage in Kubernetes clusters?​

No. Self-Deployed Runtime doesn't require a stateful store in your infrastructure. State information for SDR-based jobs is managed on the Atlan tenant.

What Kubernetes platforms and versions does Self-Deployed Runtime support?​

Atlan certifies Self-Deployed Runtime on managed Kubernetes: Amazon EKS, Azure AKS, and Google Kubernetes Engine (GKE). Kubernetes 1.24 and later is supported.

Which secret stores and storage backends does Self-Deployed Runtime support?​

The supported options depend on your deployment method. To find the configuration for your environment:

  1. Open the install guide for your deployment method: Docker Compose or Kubernetes.
  2. Select your connector from the dropdown at the top of the page.
  3. Navigate to Configure secret storage for supported secret stores (AWS Secrets Manager, Azure Key Vault, GCP Secret Manager, HashiCorp Vault, and others), or Configure object storage for supported storage backends (AWS S3, Google Cloud Storage, Azure Blob Storage, and others).

How does Self-Deployed Runtime handle security incidents?​

If you suspect security incidents, contact [email protected]. The Atlan security team coordinates the response and investigation process.

How do I raise security incident response?​

If you suspect security incidents, follow this process:

  1. Immediate isolation: Stop Self-Deployed Runtime processing immediately
  2. Preserve evidence: Capture logs and system state
  3. Contact security: Email [email protected] with incident details
  4. Document timeline: Record all incident-related activities and timestamps
  5. Coordinate response: Work with Atlan security team for investigation

See also​

  • Functionality: Frequently asked questions about how Self-Deployed Runtime features compare to Atlan-hosted execution modes.
  • Customer environment security best practices: Security baselines and requirements for deploying Self-Deployed Runtime in your environment.
  • Security: Security architecture, authentication, encryption, and compliance controls for Self-Deployed Runtime.