You're viewing version 2.1 of the OpenSearch documentation. This version is no longer maintained. For the latest version, see the current documentation. For information about OpenSearch version maintenance, see Release Schedule and Maintenance Policy.

Index aliases

An alias is a virtual index name that can point to one or more indexes.

If your data is spread across multiple indexes, rather than keeping track of which indexes to query, you can create an alias and query it instead.

For example, if you’re storing logs into indexes based on the month and you frequently query the logs for the previous two months, you can create a last_2_months alias and update the indexes it points to each month.

Because you can change the indexes an alias points to at any time, referring to indexes using aliases in your applications allows you to reindex your data without any downtime.

Table of contents

1. Create aliases
2. Add or remove indexes
3. Manage aliases
4. Add aliases at index creation
5. Create filtered aliases
6. Index alias options

Create aliases

To create an alias, use a POST request:

POST _aliases

Use the actions method to specify the list of actions that you want to perform. This command creates an alias named alias1 and adds index-1 to this alias:

POST _aliases
{
  "actions": [
    {
      "add": {
        "index": "index-1",
        "alias": "alias1"
      }
    }
  ]
}

You should see the following response:

{
   "acknowledged": true
}

If this request fails, make sure the index that you’re adding to the alias already exists.

To check if alias1 refers to index-1, run the following command:

GET alias1

Add or remove indexes

You can perform multiple actions in the same _aliases operation. For example, the following command removes index-1 and adds index-2 to alias1:

POST _aliases
{
  "actions": [
    {
      "remove": {
        "index": "index-1",
        "alias": "alias1"
      }
    },
    {
      "add": {
        "index": "index-2",
        "alias": "alias1"
      }
    }
  ]
}

The add and remove actions occur atomically, which means that at no point will alias1 point to both index-1 and index-2.

You can also add indexes based on an index pattern:

POST _aliases
{
  "actions": [
    {
      "add": {
        "index": "index*",
        "alias": "alias1"
      }
    }
  ]
}

Manage aliases

To list the mapping of aliases to indexes, run the following command:

GET _cat/aliases?v

Example response

alias     index   filter    routing.index   routing.search
alias1    index-1   *             -                 -

To check which indexes an alias points to, run the following command:

GET _alias/alias1

Example response

{
  "index-2": {
    "aliases": {
      "alias1": {}
    }
  }
}

Conversely, to find which alias points to a specific index, run the following command:

GET /index-2/_alias/*

To check if an alias exists, run the following command:

HEAD /alias1/_alias/

Add aliases at index creation

You can add an index to an alias as you create the index:

PUT index-1
{
  "aliases": {
    "alias1": {}
  }
}

Create filtered aliases

You can create a filtered alias to access a subset of documents or fields from the underlying indexes.

This command adds only a specific timestamp field to alias1:

POST _aliases
{
  "actions": [
    {
      "add": {
        "index": "index-1",
        "alias": "alias1",
        "filter": {
          "term": {
            "timestamp": "1574641891142"
          }
        }
      }
    }
  ]
}

Index alias options

You can specify the options shown in the following table.