- Newest
- Most votes
- Most comments
Downtime & Cost During OpenSearch Configuration Changes
Thanks for raising this — it’s an important operational question.
🔹 Downtime: AWS OpenSearch uses blue/green deployments to avoid downtime. It spins up a new (“green”) environment with the desired config changes, syncs data from the current cluster (“blue”), and only cuts traffic over when the green environment is healthy. So under normal conditions: zero downtime.
🔹 Cost Impact: Yes, there is temporary double resource usage during this process. You’ll be billed for both environments while green is being provisioned and data is being replicated. If you're scaling frequently, this can become costly — especially when changing instance types or node counts.
Suggestions to reduce impact:
Combine multiple changes into one operation
Schedule scale-ups during low-traffic periods
Use Index State Management or Auto-Tune for intelligent scaling
Would be happy to expand on any of these options if helpful.
Relevant content
- asked 6 days ago
- asked 6 days ago
- AWS OFFICIALUpdated 2 months ago