Skip to main content

Verifying client access to S3 object storage

After configuring the S3 server and buckets, S3 administrators can make object stores available to client systems, either ONTAP systems with remote FabricPool capacity (cloud) tiers or S3 client apps, or to a local FabricPool capacity tier.

  • Enabling ONTAP S3 access for remote FabricPool tiering
    For ONTAP S3 to be used as a remote FabricPool capacity (cloud) tier, the ONTAP S3 administrator must provide information about the S3 server configuration to the remote ONTAP cluster administrator.
  • Attaching ONTAP S3 Object Store as Cloud Tier
    Once you have all of the information above you are ready to attach the remote DM Series device as the cloud tier for your primary DM Series system. The following steps will walk you throug that process.
  • Defining a tiering policy for volumes
    Once you have attached the secondary system as your cloud tier, you will need to assign your tiering policy on a per volume basis to determine data locality.
  • Verifying the cloud tier
    Once everything is configured and the cooling period is met, you will see that data is being moved to the cloud tier.
  • Enabling 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.
  • Enabling client access from an S3 app
    For S3 client apps to access the ONTAP S3 server, the ONTAP S3 administrator must provide configuration information to the S3 user.