Skip to main content
NetApp Knowledge Base

Metadata cannot be updated for S3 object with SSE Customer Key

  1. Last updated
  2. Save as PDF
Views:
194
Visibility:
Public
Votes:
0
Category:
storagegrid
Specialty:
sgrid
Last Updated:

Applies to

NetApp StorageGRID 11.9 and lower

Issue

  • When attempting to PUT an object using SSE-C, such as
    $ aws s3api put-object --profile MYPROFILE --bucket MYBUCKET --endpoint-url https://my.url  --key awscliv2.zip --body ./awscliv2.zip --sse-customer-algorithm AES256 --sse-customer-key fileb://my.key --metadata TESTMETA=mytest

    No confirmation or error was returned.
     
  • When attempting to replace the metadata with a Copy Object, such as:
    $ aws s3api copy-object --profile MYPROFILE --bucket MYBUCKET --endpoint-url https://my.url  --key awscliv2.zip --copy-source MYBUCKET/awscliv2.zip --sse-customer-algorithm AES256 --sse-customer-key fileb://my.key --copy-source-sse-customer-algorithm AES256 --copy-source-sse-customer-key fileb://my.key --metadata-directive REPLACE --metadata TESTMETA=metareplace

    The following error is returned:
    This results in n error occurred (InternalError) when calling the CopyObject operation (reached max retries: 2): We encountered an internal error. Please try again.

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.