Skip to main content
NetApp Knowledge Base

S3 client receives "Not Implemented" when accessing Boto3 presigned URL using V2 signatures

Views:
121
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9
  • ONTAP S3
  • Amazon Web Services (AWS) signature

Issue

Attempt to access ONTAP S3 using the pre-signed URL created by boto3 was returned with error - 501 Not Implemented.

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.