Skip to main content

Enable ONTAP S3 access for local FabricPool tiering

Contributors netapp-dbagwell netapp-lenida netapp-ahibbard netapp-aherbin
PDFs

For ONTAP S3 to be used as a local FabricPool capacity tier, you must define an object store based on the bucket you created, and then attach the object store to a performance tier aggregate to create a FabricPool.

Before you begin

You must have the ONTAP S3 server name and a bucket name, and the S3 server must have been created using cluster LIFs (with the -vserver Cluster parameter).

About this task

The object-store configuration contains information about the local capacity tier, including the S3 server and bucket names and authentication requirements.

An object-store configuration once created must not be reassociated with a different object-store or bucket. You can create multiple buckets for local tiers, but you cannot create multiple object stores in a single bucket.

A FabricPool license is not required for a local capacity tier.

Steps

  1. Create the object store for the local capacity tier:

    storage aggregate object-store config create -object-store-name store_name -ipspace Cluster -provider-type ONTAP_S3 -server S3_server_name -container-name bucket_name -access-key access_key -secret-password password

    • The -container-name is the S3 bucket you created.

    • The -access-key parameter authorizes requests to the ONTAP S3 server.

    • The -secret-password parameter (secret access key) authenticates requests to the ONTAP S3 server.

    • You can set the -is-certificate-validation-enabled parameter to false to disable certificate checking for ONTAP S3.

    cluster1::> storage aggregate object-store config create
-object-store-name MyLocalObjStore -ipspace Cluster -provider-type ONTAP_S3 -server s3.example.com
-container-name bucket1 -access-key myS3key -secret-password myS3pass

  2. Display and verify the object store configuration information:

    storage aggregate object-store config show

  3. Optional: Determine how much data in a volume is inactive by using inactive data reporting.

    Seeing how much data in a volume is inactive can help you decide which aggregate to use for FabricPool local tiering.

  4. Attach the object store to an aggregate:

    storage aggregate object-store attach -aggregate aggr_name -object-store-name store_name

    You can use the allow-flexgroup true option to attach aggregates that contain FlexGroup volume constituents.

    cluster1::> storage aggregate object-store attach
-aggregate aggr1 -object-store-name MyLocalObjStore

  5. Display the object store information and verify that the attached object store is available:

    storage aggregate object-store show

    cluster1::> storage aggregate object-store show

Aggregate    Object Store Name    Availability State
---------    -----------------    ------------------
aggr1        MyLocalObjStore      available