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.

What features work differently with Self-Deployed Runtime?​

Self-Deployed Runtime focuses on secure metadata extraction from your infrastructure. Some interactive features available in Atlan-hosted mode require different approaches:

FeatureAtlan-hostedSelf-Deployed Runtime
Metadata extraction✅ Supported✅ Supported
Authentication testing✅ Test during setup⚠️ Configure credentials, test after deployment
Preflight checks✅ Pre-validate permissions⚠️ Validate permissions manually before deployment
Filter selection✅ Interactive dropdowns⚠️ Use regular expressions to specify filters
Sample data preview✅ Supported❌ Not available
Insights queries✅ Supported❌ Not available
Tag reverse sync✅ Supported❌ Not available

For workflows requiring interactive features, use Atlan-hosted execution mode. For secure metadata extraction from private infrastructure, use Self-Deployed Runtime.

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.

How does Self-Deployed Runtime handle security incidents?​

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

How do I raise a security incident response?​

If you suspect a security incident, 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​