π‘οΈ AWS OpenSearch Domain fine-grained access control is not enabledπ’
- Contextual name: π‘οΈ Domain fine-grained access control is not enabledπ’
- ID:
/ce/ca/aws/opensearch/domain-fine-grained-access-control - Tags:
- π’ Policy with categories
- π’ Policy with type
- π’ Production policy
- Policy Type:
COMPLIANCE_POLICY - Policy Categories:
SECURITY
Logicβ
- π§ prod.logic.yamlπ’
Similar Policiesβ
Descriptionβ
Descriptionβ
This policy identifies AWS OpenSearch Domains that do not have fine-grained access control enabled.
Fine-grained access control in Amazon OpenSearch Service adds authentication and authorization controls at the index, document, field, and API level. It allows you to define a master user, map users and backend roles to OpenSearch roles, and limit what identities can view or modify within the domain. This provides stronger protection than relying only on network placement or coarse domain access policies.
Rationaleβ
Enabling fine-grained access control helps enforce least-privilege access to search clusters that often contain sensitive operational, application, or business data. Without it, users and applications that can reach the domain may receive broader access than necessary, increasing the risk of unauthorized data exposure, destructive changes, and privilege misuse.
Impactβ
Enabling fine-grained access control is a security architecture change and should be planned carefully. It requires HTTPS, encryption at rest, and node-to-node encryption. Existing access policies, Dashboards access, and application authentication flows might need to be updated to avoid access disruptions. After fine-grained access control is enabled, it cannot be disabled on the existing domain.
... see more
Remediationβ
Remediationβ
Enable Fine-Grained Access Controlβ
Fine-grained access control requires the following security settings on the domain:
- HTTPS enforcement and the latest TLS policy. See
AWS OpenSearch Domain is not encrypted with the latest TLS policy.- Encryption at rest. See
AWS OpenSearch Domain is not encrypted at rest.- Node-to-node encryption. See
AWS OpenSearch Domain Node To Node Encryption is not enabled.Decide whether the domain will use the internal user database or an external identity source such as IAM or SAML. Configure a master user and review the domain access policy so it does not conflict with the fine-grained authorization model.
Option 1: Use the Internal User Databaseβ
Enable fine-grained access control and configure an internal master user:
aws opensearch update-domain-config \
--domain-name {{domain-name}} \
--domain-endpoint-options EnforceHTTPS=true \
--encryption-at-rest-options Enabled=true \
... [see more](remediation.md)