Skip to content

Storage tiers & lifecycle policies for Azure Blob Storage snapshot repositories #126987

Open
@DaveCTurner

Description

@DaveCTurner

Today users of snapshot repositories backed by Azure Blob Storage cannot specify which access tier to use, so Elasticsearch will use the account-level default tier for all uploads. We should give users the ability to tell Elasticsearch to specify a particular storage tier at upload time rather than using the account-level default. For similar reasoning to that described in #81352 we should make this separately configurable for data and metadata blobs. In addition, we should allow users to specify tags for Elasticsearch-related uploads so that they can apply a lifecycle policy to their snapshot data. Again, users should be able to specify different tags for data and metadata blobs so that these datasets can have different lifecycle policies.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions