CopyObject and setting the source and destination to the same key with a new ContentType specified. This workaround incurs a cost but at least allows the content type to be updated. Unfortunately, this approach does not appear to work with the Tigris API.however, one of the workarounds I’ve used with S3 was callingand setting the source and destination to the same key, with a new ContentType specified. This workarCopyObject
x-amz-metadata-directive with the value REPLACE (i.e., x-amz-metadata-directive:REPLACE) and include all the headers you need? Then it will perform the copy operation while honoring the metadata in the copy request. Basically, if this header isn’t specified, the default directive is COPY, which means copying all the metadata from the source key, and since source and destination are the same that’s why you were seeing the error.