Skip to main content

Key considerations and system adaptation for OpenSearch® Security management

Before enabling OpenSearch Security management for Aiven for OpenSearch service, it is crucial to be aware of its impact on your current system and adapt your infrastructure accordingly. This document highlights essential aspects to consider before enabling it.

Test OpenSearch® Security management

If you are an existing Aiven for OpenSearch user, testing OpenSearch Security management before applying it to your running services is advisable. To do this, you have two options:

  1. Create a new service for testing purposes.
  2. Fork one of your existing running services to create a test environment.

Enabling OpenSearch® Security management

Once OpenSearch Security management is enabled, the following changes will occur:

  1. Your current Aiven for OpenSearch users and roles will be transferred to OpenSearch.
  2. Aiven for OpenSearch Access Control List (ACL) APIs will be deactivated. The affected API endpoints are:
  3. Aiven for OpenSearch ACL in Aiven Terraform provider will be disabled. The affected resources are:
  4. Managing OpenSearch ACL through the Aiven Console will no longer be available. Instead, use the OpenSearch API and OpenSearch Security dashboard for user and role management.

Adapting your system, automation, and infrastructure

Preparing and adapting your systems, automation processes, and infrastructure is important to accommodate the changes introduced by OpenSearch Security Management for Aiven for OpenSearch. This adaptation ensures that your organization can seamlessly transition to the new security measures and benefit from enhanced protection.

  1. Assess the impact of OpenSearch Security management on your existing systems and infrastructure, identifying areas that require modification to support the new security features.
  2. Review and update your automation processes to incorporate the security configurations, policy, and control implementation offered by OpenSearch Security, ensuring consistency across your system and infrastructure.
  3. Test and validate the updated systems, automation, and infrastructure to ensure compatibility and functionality with the new security features.
  4. Provide training and support to your teams to familiarize them with the changes and ensure they can effectively manage the transition.
  5. Monitor and adjust your systems, automation, and infrastructure as needed, maintaining optimal performance and security in alignment with your organization's requirements.