Skip to main content
NetApp Knowledge Base

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

  1. Last updated
  2. Save as PDF
Views:
62
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
NAS
Last Updated:

Applies to

  • ONTAP S3
    • ONTAP 9.8 and later
  • Amazon Web Services (AWS) signature

Issue

Creation of presigned URL using boto3 results in unable to access S3 presigned URL returns the following error "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.