Skip to main content
NetApp Knowledge Base

Add S3 bucket as a capacity tier fails with signature mismatch

  1. Last updated
    Dec 18, 2024
  2. Save as PDF
Views:
58
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:
12/18/2024, 3:50:09 PM

Applies to

  • ONTAP 9
  • FabricPool

Issue

Add the s3 bucket as a capacity tier.
Cluster::*> storage aggregate object-store config create -object-store-name store_name -provider-type ONTAP_S3 -server s3.local -container-name localbucket -ipspace Cluster -use-http-proxy false <access-key> -secret-password <secret key>
Cluster::*>  ERROR osc.signatureMismatch: Object-store PUT operation server-calculated request signature does not match the signature sent to object-store server s3 for bucket or container s3-bucket02 on node cluster1. Check the keys and signing method.

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.