Securing OpenSearch: Hints for avoiding common hassles
summary
Configures TLS, authN and authZ for OpenSearch with concrete warnings: a three‑node cluster requires about seven certificates and private keys for transport, REST and admin client auth; the OpenSearch Kubernetes operator can auto‑generate certs but they expire in one year and lack easy renewal; the security admin tool and Helm/Secrets workflows overwrite each other unless coordinated; audit logs are noisy so check the OpenSearch internal locks to see effective roles and role‑mapping when debugging.
AI-written summary · about
chapters (8)
- 0:00Introduction to OpenSearch
- 3:09Implementing TLS security
- 5:53Advanced TLS configurations
- 11:51Configuration management
- 19:11Authentication strategies
- 25:03Authorization and roles
- 33:07Debugging security issues
- 36:47Closing and Q&A
related talks
29mThreat Modeling for OpenSearch: Identifying and Mitigating Security Risks
13mSecuring the Data Frontier: Real-World Strategies With OpenSearch
35mManaging the Managed: Advanced Automation and Security for Amazon...
38mEnabling Secure, Fine-Grained Resource Sharing for Team Collaboration in OpenSearch
11mLightning Talk: A Supply Chain Security View of OpenSearch
14mOpenSearch Data Separation With JWT Authentication for Multi-tenant Applications
13mOpenSearch at Atlassian Scale
21mA Brief Guide to Secure Agentic Knowledge Retrieval