Autenticación y roles de usuarios

Imagine your search engine holds sensitive customer data or internal documents. Without proper security, anyone could potentially access, modify, or delete it.

This lesson will show you how to protect your Elasticsearch cluster by controlling who can do what.

Elasticsearch's security features, part of what was formerly X-Pack, provide robust controls for your cluster. They include:

• Authentication: Verifying user identities.
• Authorization: Defining what authenticated users can do.
• Encryption: Securing communication.

We'll focus on authentication and authorization in this lesson.

To enable security, you need to configure your elasticsearch.yml file. This is typically done during the initial setup of your cluster.

Add the following line to enable security features in your configuration:

When security is enabled, Elasticsearch creates several built-in users with predefined roles. The most important is the elastic user.

• elastic: The superuser, with full administrative privileges. Use this for initial setup and critical operations.
• kibana_system: Used by Kibana to connect to Elasticsearch.
• logstash_system: Used by Logstash for monitoring.

You'll set passwords for these during the initial setup process.

Let's create a new user named dev_user. We'll use the Elasticsearch Users API, which allows you to manage users via REST calls.

This API call creates a user and sets their password. Remember to use strong, unique passwords!

In Elasticsearch, roles are central to authorization. A role is a collection of privileges that define what actions a user can perform.

• Simplifies Management: Assign a role, not individual permissions, to users.
• Granular Control: Roles can grant cluster-level and index-level privileges.
• Cumulative: Users can have multiple roles, and their privileges are combined.

Elasticsearch comes with several useful built-in roles, providing common sets of permissions:

• superuser: Grants all privileges across the cluster.
• viewer: Can read data from all indices.
• editor: Can read and write data to all indices.
• kibana_user: Allows access to Kibana features.

These roles are great starting points, but often you'll need more specific control.

Let's create a custom role called my_app_reader that can only read data from an index named my_application_data.

This role grants read and view_index_metadata privileges on a specific index. It also includes basic cluster monitoring privileges.

Now that we have our dev_user and my_app_reader role, let's assign the role to the user. We'll update the dev_user to have this role.

Remember, users can be assigned multiple roles, inheriting all privileges from each one they possess.

Consider a user named analyst. This user has two roles assigned:

• sales_reader: Grants read privilege on the sales_data index.
• finance_writer: Grants read and write privileges on the finance_reports index.

Which of the following actions are permitted for the analyst user?

You've learned the fundamentals of Elasticsearch security!

• We discussed why security is crucial for your data.
• Explored how to enable security and identify built-in users.
• Understood roles as collections of privileges.
• Created custom users and roles using the Security API.
• Assigned roles to users to control access.

Proper authentication and authorization are key to a secure and robust Elasticsearch deployment.