Enable ONTAP S3 access for local FabricPool tiering
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.
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).
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.
Create the object store for the local capacity tier:
storage aggregate object-store config create -object-store-name store_name -ispace Cluster -provider-type ONTAP_S3 -server S3_server_name -container-name bucket_name -access-key access_key -secret-password password
-container-nameis the S3 bucket you created.
-access-keyparameter authorizes requests to the ONTAP S3 server.
-secret-passwordparameter (secret access key) authenticates requests to the ONTAP S3 server.
You can set the
falseto disable certificate checking for ONTAP S3.
cluster1::> storage aggregate object-store config create -object-store-name MyLocalObjStore -ispace Cluster -provider-type ONTAP_S3 -server s3.example.com -container-name bucket1 -access-key myS3key -secret-password myS3pass
Display and verify the object store configuration information:
storage aggregate object-store config show
Optional: To see how much data in a volume is inactive, follow the steps in Determining 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.
Attach the object store to an aggregate:
storage aggregate object-store attach -aggregate aggr_name -object-store-name store_name
You can use the
trueoption to attach aggregates that contain FlexGroup volume constituents.
cluster1::> storage aggregate object-store attach -aggregate aggr1 -object-store-name MyLocalObjStore
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