When should I use UltraWarm nodes?

UltraWarm nodes are ideal for storing data that you query infrequently but need to keep accessible — typically older log data or time-series data beyond the hot retention period. UltraWarm uses S3-backed storage at roughly one-tenth the cost of hot EBS-attached storage. Data on UltraWarm nodes is read-only. A common pattern is to keep 7-14 days of data on hot nodes for active querying and move older data to UltraWarm for up to several months of retention at lower cost.

Do I need dedicated master nodes?

AWS strongly recommends dedicated master nodes for production domains. Master nodes manage cluster state, shard allocation, and index operations — without dedicated masters, data nodes handle these tasks, which can impact query performance during cluster events. Use three master nodes (for quorum) in production. For domains with fewer than 10 data nodes and non-critical workloads, you can skip dedicated masters, but expect reduced stability during blue/green deployments or node failures.

OpenSearch Cost Estimator

StorageAWS

Estimate Amazon OpenSearch domain costs with data, master, and warm nodes.

OpenSearch Configuration

Data Nodes

Instance Type

EBS Storage per Node (GB)

gp3 EBS at $0.08/GB/month per data node.

Dedicated Master Nodes

Raw Output

Output will appear here...

About This Tool

Amazon OpenSearch Service (successor to Amazon Elasticsearch Service) provides managed search and analytics domains with support for OpenSearch and legacy Elasticsearch engines. Domain costs depend on the number and type of data nodes, optional dedicated master nodes for cluster stability, warm nodes using UltraWarm for cost-effective storage of infrequently queried data, and EBS storage volumes. Additional costs include data transfer, optional features like fine-grained access control, and cross-cluster search. This estimator models monthly costs for production-grade OpenSearch deployments across different node configurations.

When to Use This Tool

•Sizing an OpenSearch domain with the right balance of data nodes, master nodes, and warm nodes for log analytics
•Estimating costs for migrating from self-managed Elasticsearch to Amazon OpenSearch Service
•Comparing costs between different instance families (general purpose, compute-optimized, memory-optimized) for search workloads

Frequently Asked Questions

When should I use UltraWarm nodes?: UltraWarm nodes are ideal for storing data that you query infrequently but need to keep accessible — typically older log data or time-series data beyond the hot retention period. UltraWarm uses S3-backed storage at roughly one-tenth the cost of hot EBS-attached storage. Data on UltraWarm nodes is read-only. A common pattern is to keep 7-14 days of data on hot nodes for active querying and move older data to UltraWarm for up to several months of retention at lower cost.
Do I need dedicated master nodes?: AWS strongly recommends dedicated master nodes for production domains. Master nodes manage cluster state, shard allocation, and index operations — without dedicated masters, data nodes handle these tasks, which can impact query performance during cluster events. Use three master nodes (for quorum) in production. For domains with fewer than 10 data nodes and non-critical workloads, you can skip dedicated masters, but expect reduced stability during blue/green deployments or node failures.

Related Learning Guides

Cost Optimization Strategies26 min read

Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.