Skip to main content

​
Production-Ready Requirements for OpenMetadata Deployment

This section outlines the minimum hardware and resource specifications required for deploying OpenMetadata and its dependencies. These recommendations ensure optimal performance and scalability for your deployment.

​
OpenMetadata Server

  • vCPUs: Minimum of 4 vCPUs
  • Memory: 16 GiB
  • Storage Volume: 100 GiB

​
External Services

OpenMetadata depends on the following external services, each with specific resource requirements:

​
Version Compatibility Matrix

Before deploying OpenMetadata in a production environment, ensure that all required external services meet the minimum supported versions listed below. Running unsupported versions may lead to ingestion failures, search issues, or upgrade incompatibilities.

​
Note:

OpenMetadata relies on these external services for metadata storage and search indexing. Using versions lower than the minimum supported versions may result in unexpected behavior or deployment failures.

​
Database (e.g., PostgreSQL)

  • vCPUs: Minimum of 4 vCPUs per instance
  • Memory: 16 GiB RAM per instance
  • Storage Volume:
    • 30 GiB (minimum)
    • Dynamic expansion up to 100 GiB

​
Elasticsearch

  • vCPUs: Minimum of 2 vCPUs per instance
  • Memory: 8 GiB RAM per instance
  • Storage Volume: 100 GiB
These specifications are also applicable for managed services like AWS RDS, GCP CloudSQL, or AWS OpenSearch.

​
Summary Recommendations

For a typical OpenMetadata deployment (one replica):
  • OpenMetadata Server: 4 vCPUs, 16 GiB RAM, 100 GiB persistent storage
  • Database: 4 vCPUs, 16 GiB RAM, 30 GiB storage (expandable to 100 GiB)
  • Elasticsearch: 2 vCPUs, 8 GiB RAM, 100 GiB storage
Ensure these resources are allocated adequately to prevent performance bottlenecks or scalability issues. Managed services with equivalent specifications are supported.