Object Storage Class Optimization

Moving your storage objects to warmer or colder classes according to consumption is an effective savings strategy, but manually assessing the appropriate class for each resource can be complicated and time consuming. Our Object Storage Class Optimization capability assesses observed access patterns after objects have persisted for a given period of time, then offers adjustments to reduce waste.

This section walks you through how to:

• Configure the Object Storage Class Optimization Policy
• Define the Scope of the Object Storage Resources to Include
• Define the Threshold for Moving to Cooler Storage
• Define the Object Storage Class Optimization Actions to Take
• Configure the General Object Storage Class Optimization Policy Options
• Customize the Object Storage Class Optimization Policy
• Review Actions Taken by the Object Storage Class Optimization Policy
• Notify Users on How to Use the Object Storage Class Optimization Policy

Configure the Object Storage Class Optimization Policy

To configure the Instance Rightsizing Policy:

1. Go to the Catalog page (Automation > Catalog).
2. Select the appropriate policy and click Apply.
3. Select the options to configure the policy.

Define the Scope of the Object Storage Resources to Include

To define the scope of the Object Storage Class resources to include:

Determine which resources to evaluate for underutilization.

• To define scope using Select Accounts: Specify the list of accounts to evaluate. For example, you may wish to limit the action to non-production accounts or to any subset of accounts.
• To define scope using Tag filtering: Limit the scope within the selected accounts by specifying tags to exclude. For example, if your production and non-production resources are mixed in your cloud accounts, you can leverage this tag-based filtering functionality to limit the action based on an environment tag.

Define the Threshold for Moving to Cooler Storage

Specify the number of days after which the item will be moved to a cooler storage option. You can set different lengths of time for each level of storage.

Define the Object Storage Class Optimization Actions to Take

To define the Object Storage Class Opimization actions to take:

Perform the following action.

Configure users to be notified: Specify the list of recipients who should receive notifications about rightsizing. Add as many recipients as you like to the Email addresses of the recipients you wish to notify field. They do not need to be registered as Cloud Cost Optimization users.

Configure the General Object Storage Class Optimization Policy Options

To configure the general Object Storage Class Optimization Policy options:

Set the following standard policy configuration options when the Object Storage Class Optimization Policy is applied.

• Frequency for policy to run: Specify the frequency the policy will perform the checks, such as weekly, daily, hourly, or every 15 minutes.
• Fully automated vs approval required: Specify at the time when applied whether the policy will take action after user approval versus automatically without user intervention. See the Skip Action Approvals documentation.

Customize the Object Storage Class Optimization Policy

To customize the Object Storage Class Optimization Policy:

Policy designers can customize the policy definition as they choose, such as:

• Customize the policy to move to warmer storage classes.
• Leverage log data from cloud provider to determine last access dates.

Review Actions Taken by the Object Storage Class Optimization Policy

These actions may occur with approval or fully automated depending on whether the policy manager has selected the Skip Action Approvals option.

• Any Amazon Web Services (AWS) storage that meets the conditions specified will be copied to the new type, and the old version will be removed.
• Microsoft Azure and Google storage that meet the conditions specified will be switched directly over to the new type.