bm ilm tier rm

Required Permissions

Buckit requires the following permissions scoped to to the bucket or buckets for which you are creating lifecycle management rules.

• s3:PutLifecycleConfiguration

• s3:GetLifecycleConfiguration

Buckit also requires the following administrative permissions on the cluster in which you are creating remote tiers for object transition lifecycle management rules:

• admin:SetTier

• admin:ListTier

For example, the following policy provides permission for configuring object transition lifecycle management rules on any bucket in the cluster:.

{
   "Version": "2012-10-17",
   "Statement": [
      {
            "Action": [
               "admin:SetTier",
               "admin:ListTier"
            ],
            "Effect": "Allow",
            "Sid": "EnableRemoteTierManagement"
      },
      {
            "Action": [
               "s3:PutLifecycleConfiguration",
               "s3:GetLifecycleConfiguration"
            ],
            "Resource": [
                        "arn:aws:s3:::*"
            ],
            "Effect": "Allow",
            "Sid": "EnableLifecycleManagementRules"
      }
   ]
}

Parameters

The command accepts the following arguments:

TARGET

Required

The alias of a configured Buckit deployment on which the desired tier exists.

TIER_NAME

Required

The name of an existing remote tier to remove.

You must specify the tier in all-caps, e.g. WARM_TIER.

No object can have transitioned to the tier.

Global Flags

This command supports any of the global flags.

S3 Compatibility

The bm commandline tool is built for compatibility with the AWS S3 API and is tested with Buckit and AWS S3 for expected functionality and behavior.

Buckit provides no guarantees for other S3-compatible services, as their S3 API implementation is unknown and therefore unsupported. While bm commands may work as documented, any such usage is at your own risk.