Get started with Amazon OpenSearch Service: T-shirt size your domain for log analytics
Big Data Blog
This article provides comprehensive guidelines for sizing Amazon OpenSearch Service domains for log analytics workloads, focusing on optimizing performance and resource allocation.
- Recommends time-based indexing strategy for log data with daily or weekly indexes
- Provides a T-shirt sizing approach for domain configuration based on daily data volume
- Offers detailed calculation methods for:
- Storage requirements
- Shard count
- CPU requirements
- Instance type selection
- Presents a sizing table ranging from XSmall (10 GB/day) to XXL (80 TB/day)
- Emphasizes the importance of monitoring, adjusting, and optimizing OpenSearch Service domains
The key takeaway is to use these guidelines as a starting point, continuously monitor performance, and adapt the configuration to specific workload characteristics.
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
Feb 16
2026
2026
Amazon OpenSearch Service 101: T-shirt size your domain for e-commerce search
Aug 20
2025
2025
Build enterprise-scale log ingestion pipelines with Amazon OpenSearch Service
Mar 7
2024
2024
Petabyte-scale log analytics with Amazon S3, Amazon OpenSearch Service, and Amazon OpenSearch Ingestion
Feb 18
2026
2026
Best practices for right-sizing Amazon OpenSearch Service domains
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.