Final lab: Lifecycle, backup and permissions

What you will learn in this TP

• Write an ISM policy
• Restore a snapshot
• Limit permissions

Introduction #

What you will learn in this section

• Write an ISM policy
• Restore a snapshot
• Limit permissions

Context. Before production, you must prove that indexes manage themselves, that an accidental deletion can be repaired and that a reader cannot break anything.

Prerequisites: the first lab  ·  Estimated time: 50 min

A prototype ready to operate.

Setup #

Guided steps, with their solution.

1. 1. Write the policy

   Why? Without ISM, indexes grow until the disk is full.

   Create a policy: rollover, read-only at 7 days, deletion at 30 days. The 2-document threshold only serves to observe the rollover.

2. 2. Trigger the rollover

   Why? Rollover needs a write alias and the rollover_alias setting.

   Create the template and first index, then write two documents. After two to three minutes, a cycle-000002 index should appear.

3. 3. Back up and restore

   Why? A replica does not protect against deletion.

   Create the repository, take a snapshot, delete logs-app-000001 and restore it: the count must return to 3.

4. 4. Create a read-only role

   Why? Least privilege is proven by a refusal.

   Create the user, the role and their mapping. Check that reading returns 200 and deleting 403.

Difficulty level : ●●●○○ (3/5)