OpenSearch
Create an integration to manage access to an OpenSearch Integration instance.
OpenSearch is an open-source search and analytics suite, maintained by Amazon Web Services (AWS).
Through this integration, Apono helps you discover your OpenSearch Integration resources and securely manage access to the index and roles through your OpenSearch Integration instance.
Prerequisites
Apono Connector
On-prem connection serving as a bridge between an OpenSearch Integration instance and Apono:
Minimum Required Version: 1.4.0 Learn how to update an existing AWS, Azure, GCP, or Kubernetes connector.
OpenSearch Integration Account Access
OpenSearch Integration account with admin privileges
OpenSearch Integration
User for Appono’s connector (User/Password) with assigned roles - https://docs.opensearch.org/docs/latest/security/access-control/users-roles/
Create an OpenSearch Integration user
You must create a user in your OpenSearch Integration instance for the Apono connector and grant that user role to your resources.
Follow these steps to create a service account for OpenSearch Integration in your Cloud Environment:
Create a user for Apono’s connector
Assign roles: AWS opensearch > security_manager, opensource > all_access To enable the roles: plugins.security.restapi.roles_enabled
Create a new role and provide the following permissions:
"cluster:monitor/state"
"cluster:monitor/health"Integrate OpenSearch Integration
Follow these steps to complete the integration:
On the Catalog tab, click OpenSearch Integration. The Connect Integration page appears.
Under Discovery, choose Index or/and Role, and click Next. The Apono connector section expands.
From the dropdown menu, select a connector.
Click Next. The Integration Config page appears.
Define the Integration Config settings.
Integration Name
Unique, alphanumeric, user-friendly name used to identify the integration when constructing an access flow
Select Auth Type
Leave user-password
Url
Enter the OpenSearch Url
SSO Portal Url
Leave empty
Click Next. The Secret Store section expands.
Click Next. The 'Get more with Apono' section expands.
Define the Get more with Apono settings.
Credential Rotation
(Optional) Number of days after which the database credentials must be rotated
Learn more about the Credentials Rotation Policy.
User cleanup after access is revoked (in days)
(Optional) Defines the number of days after access has been revoked that the user should be deleted
Learn more about Periodic User Cleanup & Deletion.
Custom Access Details
(Optional) Instructions explaining how to access this integration's resources
Upon accessing an integration, a message with these instructions will be displayed to end users in the User Portal. The message may include up to 400 characters.
To view the message as it appears to end users, click Preview.
Integration Owner
(Optional) Fallback approver if no resource owner is found
Follow these steps to define one or several integration owners:
From the Attribute dropdown menu, select User or Group under the relevant identity provider (IdP) platform.
From the Value dropdown menu, select one or multiple users or groups.
NOTE: When Resource Owner is defined, an Integration Owner must be defined.
Resource Owner
(Optional) Group or role responsible for managing access approvals or rejections for the resource
Follow these steps to define one or several resource owners:
Enter a Key name. This value is the name of the tag created in your cloud environment.
From the Attribute dropdown menu, select an attribute under the IdP platform to which the key name is associated. Apono will use the value associated with the key (tag) to identify the resource owner. When you update the membership of the group or role in your IdP, this change is also reflected in Apono.
NOTE: When this setting is defined, an Integration Owner must also be defined.
Click Confirm.
Now that you have completed this integration, you can create access flows that grant permission to your OpenSearch Integration instance.
Last updated
Was this helpful?