Encryption method specified is not supported Aws::S3Crt::Model::ServerSideEncryption::NOT_SET

[rvernica]

Confirm by changing [ ] to [x] below to ensure that it's a bug:

• I've gone though Developer Guide and API reference
• I've searched for previous similar issues and didn't find any solution

Describe the bug

Aws::S3Crt::Model::ServerSideEncryption::NOT_SET throws InvalidArgument Message: The encryption method specified is not supported

SDK version number

1.9.97

Platform/OS/Hardware/Device

Linux/CentOS 7

To Reproduce (observed behavior)

1. Get S3 CRT AWS example from https://github.com/awsdocs/aws-doc-sdk-examples/tree/master/cpp/example_code/s3-crt

2. Edit s3-crt-demo.cpp file

3. Before line 107 add

    request.SetServerSideEncryption(Aws::S3Crt::Model::ServerSideEncryption::NOT_SET);
   

4. Compile and run run_s3-crt-demo

Expected behavior

No exception and successful completion of PUT request.

Logs/output

./run_s3-crt-demo 
All buckets under my account:
...
Putting object: "my-object" to bucket: "my-bucket-4023f309-0181-423c-a781-7218632ffba5" ...
PutObject error:
HTTP response code: 400
Resolved remote host IP address: 
Request ID: RPCSPSZ20GTC5RXQ
Exception name: InvalidArgument
Error message: Unable to parse ExceptionName: InvalidArgument Message: The encryption method specified is not supported
7 response headers:
connection : close
content-type : application/xml
date : Sat, 11 Sep 2021 16:08:32 GMT
server : AmazonS3
transfer-encoding : chunked
x-amz-id-2 : b5vqiZiMXEhLL/vkKv+avl+G6dSImH9FHGl5NV+eIdVry0mBWnCu0Zb4/jSy5cJivT1DTyBgNeE=
x-amz-request-id : RPCSPSZ20GTC5RXQ

TRACE logs

...
[INFO] 2021-09-11 16:15:48.900 AuthSigning [140160532788992] (id=0x7f799c000da0) Signing successfully built canonical request for algorithm SigV4, with contents
PUT
/my-object

content-length:5
content-type:binary/octet-stream
host:my-bucket.s3.us-east-1.amazonaws.com
x-amz-content-sha256:UNSIGNED-PAYLOAD
x-amz-date:20210911T161548Z
x-amz-server-side-encryption:

content-length;content-type;host;x-amz-content-sha256;x-amz-date;x-amz-server-side-encryption
UNSIGNED-PAYLOAD

[INFO] 2021-09-11 16:15:48.900 AuthSigning [140160532788992] (id=0x7f799c000da0) Signing successfully built string-to-sign via algorithm SigV4, with contents
AWS4-HMAC-SHA256
20210911T161548Z
20210911/us-east-1/s3/aws4_request
344ad873aa3c080aeaa931028f84a35b2f56532847d5c89487a7036160986eea

[INFO] 2021-09-11 16:15:48.901 AuthSigning [140160532788992] (id=0x7f799c000da0) Http request successfully built final authorization value via algorithm SigV4, with contents
AWS4-HMAC-SHA256 Credential=AKIAX3GSQRN3NLABBR4K/20210911/us-east-1/s3/aws4_request, SignedHeaders=content-length;content-type;host;x-amz-content-sha256;x-amz-date;x-amz-server-side-encryption, Signature=7e2e406001a49b5aaa14959080fc205ec42f187cbb26ff73e11c6f8e4fc862e1

[DEBUG] 2021-09-11 16:15:48.901 task-scheduler [140160541181696] id=0x11ce7a8: Scheduling s3_client_process_work_task task for immediate execution
[DEBUG] 2021-09-11 16:15:48.901 task-scheduler [140160541181696] id=0x11ce7a8: Running s3_client_process_work_task task with <Running> status
[DEBUG] 2021-09-11 16:15:48.901 S3Client [140160541181696] id=0x11ce610 s_s3_client_process_work_default - Moving relevant synced_data into threaded_data.
[DEBUG] 2021-09-11 16:15:48.901 S3Client [140160541181696] id=0x11ce610 s_s3_client_process_work_default - Processing any new meta requests.
[DEBUG] 2021-09-11 16:15:48.901 S3Client [140160541181696] id=0x11ce610 Updating meta requests with 'conservative' flag.
[DEBUG] 2021-09-11 16:15:48.901 S3Client [140160541181696] id=0x11ce610 Updating meta requests without 'conservative' flag.
[DEBUG] 2021-09-11 16:15:48.901 S3Client [140160541181696] id=0x11ce610 Updating vip connections, assigning requests where possible.
[DEBUG] 2021-09-11 16:15:48.901 standard-retry-strategy [140160541181696] id=0x1087990: attempting to acquire retry token for partition_id my-bucket.s3.us-east-1.amazonaws.com
[DEBUG] 2021-09-11 16:15:48.901 standard-retry-strategy [140160541181696] id=0x1087990: bucket for partition_id my-bucket.s3.us-east-1.amazonaws.com does not exist, attempting to create one
[DEBUG] 2021-09-11 16:15:48.901 standard-retry-strategy [140160541181696] id=0x1087990: bucket 0x7f79a4001b00 for partition_id my-bucket.s3.us-east-1.amazonaws.com created
[DEBUG] 2021-09-11 16:15:48.901 exp-backoff-strategy [140160541181696] id=0x1087900: Initializing retry token 0x7f79a40016a0
[DEBUG] 2021-09-11 16:15:48.901 task-scheduler [140160541181696] id=0x7f79a40016f8: Scheduling aws_exponential_backoff_retry_task task for immediate execution
[INFO] 2021-09-11 16:15:48.901 S3ClientStats [140160541181696] id=0x11ce610 Requests-in-flight(approx/exact):1/1  Requests-preparing:0  Requests_queued:0  Requests-network:1  Requests-waiting:0  Requests-streaming:0  Idle-connections:9  Allocated-connections:10  Active-connections:1
[DEBUG] 2021-09-11 16:15:48.901 task-scheduler [140160541181696] id=0x7f79a40016f8: Running aws_exponential_backoff_retry_task task with <Running> status
[DEBUG] 2021-09-11 16:15:48.901 exp-backoff-strategy [140160541181696] id=0x1087900: Vending retry_token 0x7f79a40016a0
[DEBUG] 2021-09-11 16:15:48.901 standard-retry-strategy [140160541181696] id=0x1087990: token acquired callback invoked with error Success. with token 0x7f79a4000b50 and nested token 0x7f79a40016a0
[DEBUG] 2021-09-11 16:15:48.901 connection-manager [140160541181696] id=0x7f79a0002c70: Acquire connection
[DEBUG] 2021-09-11 16:15:48.901 connection-manager [140160541181696] id=0x7f79a0002c70: snapshot - state=1, idle_connection_count=0, pending_acquire_count=1, pending_connect_count=1, vended_connection_count=0, open_connection_count=0, ref_count=1
[INFO] 2021-09-11 16:15:48.901 connection-manager [140160541181696] id=0x7f79a0002c70: Requesting 1 new connections from http
[DEBUG] 2021-09-11 16:15:48.901 dns [140160541181696] id=0xfab700: Host resolution requested for 52.217.87.136
[DEBUG] 2021-09-11 16:15:48.901 dns [140160541181696] id=0xfab700: No cached entries found for 52.217.87.136 starting new resolver thread.
[DEBUG] 2021-09-11 16:15:48.901 dns [140160511702784] static: resolving host 52.217.87.136
[DEBUG] 2021-09-11 16:15:48.901 dns [140160511702784] static: resolved record: 52.217.87.136
[DEBUG] 2021-09-11 16:15:48.901 dns [140160511702784] static, resolving host 52.217.87.136 successful, returned 1 addresses
[DEBUG] 2021-09-11 16:15:48.901 dns [140160511702784] static: new address resolved 52.217.87.136 for host 52.217.87.136 caching
[DEBUG] 2021-09-11 16:15:48.901 dns [140160511702784] static, invoking resolution callback for host 52.217.87.136 with 1 addresses
[DEBUG] 2021-09-11 16:15:48.901 task-scheduler [140160541181696] id=0x7f7998000c20: Scheduling attempt_connection task for immediate execution
[DEBUG] 2021-09-11 16:15:48.901 task-scheduler [140160541181696] id=0x7f7998000c20: Running attempt_connection task with <Running> status
[DEBUG] 2021-09-11 16:15:48.901 socket [140160541181696] id=0x7f79a4005ec0 fd=11: initializing with domain 0 and type 0
[DEBUG] 2021-09-11 16:15:48.901 socket [140160541181696] id=0x7f79a4005ec0 fd=11: setting socket options to: keep-alive 0, keep idle 0, keep-alive interval 0, keep-alive probe count 0.
[WARN] 2021-09-11 16:15:48.901 socket [140160541181696] id=0x7f79a4005ec0 fd=11: setsockopt() for NO_SIGNAL failed with errno 92. If you are having SIGPIPE signals thrown, you may want to install a signal trap in your application layer.
[DEBUG] 2021-09-11 16:15:48.901 socket [140160541181696] id=0x7f79a4005ec0 fd=11: beginning connect.
[DEBUG] 2021-09-11 16:15:48.901 socket [140160541181696] id=0x7f79a4005ec0 fd=11: connecting to endpoint 52.217.87.136:443.
[DEBUG] 2021-09-11 16:15:48.901 task-scheduler [140160541181696] id=0x7f79a4003980: Scheduling (null) task for future execution at time 98602937682399
[DEBUG] 2021-09-11 16:15:48.976 task-scheduler [140160541181696] id=0x7f79a40067e0: Scheduling epoll_event_loop_unsubscribe_cleanup task for immediate execution
[INFO] 2021-09-11 16:15:48.977 socket [140160541181696] id=0x7f79a4005ec0 fd=11: connection success
[DEBUG] 2021-09-11 16:15:48.977 socket [140160541181696] id=0x7f79a4005ec0 fd=11: local endpoint 172.17.0.2:40748
[DEBUG] 2021-09-11 16:15:48.977 socket [140160541181696] id=0x7f79a4005ec0 fd=11: assigning to event loop 0xed38f0
[DEBUG] 2021-09-11 16:15:48.977 channel-bootstrap [140160541181696] id=0xfab7a0: client connection on socket 0x7f79a4005ec0 completed with error 0.
[DEBUG] 2021-09-11 16:15:48.977 channel [140160541181696] id=0x7f79a40075f0: Beginning creation and setup of new channel.
[DEBUG] 2021-09-11 16:15:48.977 task-scheduler [140160541181696] id=0x7f79a4006b30: Scheduling on_channel_setup_complete task for immediate execution
[DEBUG] 2021-09-11 16:15:48.977 task-scheduler [140160541181696] id=0x7f79a40067e0: Running epoll_event_loop_unsubscribe_cleanup task with <Running> status
[DEBUG] 2021-09-11 16:15:48.977 task-scheduler [140160541181696] id=0x7f79a4006b30: Running on_channel_setup_complete task with <Running> status
[DEBUG] 2021-09-11 16:15:48.977 channel [140160541181696] id=0x7f79a40075f0: setup complete, notifying caller.
[DEBUG] 2021-09-11 16:15:48.977 channel [140160541181696] id=0x7f79a40075f0: no message pool is currently stored in the event-loop local storage, adding 0x7f79a4007a10 with max message size 16384, message count 4, with 4 small blocks of 128 bytes.
[DEBUG] 2021-09-11 16:15:48.977 channel-bootstrap [140160541181696] id=0xfab7a0: channel 0x7f79a40075f0 setup succeeded: bootstrapping.
[DEBUG] 2021-09-11 16:15:48.977 socket-handler [140160541181696] id=0x7f79a4018680: Socket handler created with max_read_size of 16384
[DEBUG] 2021-09-11 16:15:48.977 task-scheduler [140160541181696] id=0x7f79a40187e0: Scheduling tls_timeout task for future execution at time 98610013312033
[DEBUG] 2021-09-11 16:15:48.977 task-scheduler [140160541181696] id=0x7f79a4006060: Scheduling socket_written_task task for immediate execution
[DEBUG] 2021-09-11 16:15:48.977 task-scheduler [140160541181696] id=0x7f79a4006060: Running socket_written_task task with <Running> status
[DEBUG] 2021-09-11 16:15:49.061 task-scheduler [140160541181696] id=0x7f79a4006060: Scheduling socket_written_task task for immediate execution
[DEBUG] 2021-09-11 16:15:49.061 task-scheduler [140160541181696] id=0x7f79a4006060: Running socket_written_task task with <Running> status
[DEBUG] 2021-09-11 16:15:49.217 tls-handler [140160541181696] id=0x7f79a40187b0: Remote server name is my-bucket.s3.us-east-1.amazonaws.com
[DEBUG] 2021-09-11 16:15:49.217 channel-bootstrap [140160541181696] id=0xfab7a0: tls negotiation result 0 on channel 0x7f79a40075f0
[INFO] 2021-09-11 16:15:49.217 http-connection [140160541181696] id=0x7f79a401d3f0: HTTP/1.1 client connection established.
[DEBUG] 2021-09-11 16:15:49.217 connection-manager [140160541181696] id=0x7f79a0002c70: Received new connection (id=0x7f79a401d3f0) from http layer
[DEBUG] 2021-09-11 16:15:49.217 connection-manager [140160541181696] id=0x7f79a0002c70: Grabbing pooled connection (0x7f79a401d3f0)
[DEBUG] 2021-09-11 16:15:49.217 connection-manager [140160541181696] id=0x7f79a0002c70: snapshot - state=1, idle_connection_count=0, pending_acquire_count=0, pending_connect_count=0, vended_connection_count=1, open_connection_count=1, ref_count=1
[DEBUG] 2021-09-11 16:15:49.217 connection-manager [140160541181696] id=0x7f79a0002c70: Successfully completed connection acquisition with connection id=0x7f79a401d3f0
[INFO] 2021-09-11 16:15:49.217 S3Client [140160541181696] id=0x11ce610 Incoming connection has changed on VIP Connection 0x7f79a0002550.  Resetting local request count.
[DEBUG] 2021-09-11 16:15:49.217 http-stream [140160541181696] id=0x7f79a4006ea0: Created client request on connection=0x7f79a401d3f0: PUT https://my-bucket.s3.us-east-1.amazonaws.com/my-object HTTP/1.1
[DEBUG] 2021-09-11 16:15:49.217 S3MetaRequest [140160541181696] id=0x1179b30: Sending request 0x7f79a4000e80
[DEBUG] 2021-09-11 16:15:49.217 task-scheduler [140160541181696] id=0x7f79a401d4e8: Scheduling http1_connection_cross_thread_work task for immediate execution
[DEBUG] 2021-09-11 16:15:49.217 task-scheduler [140160541181696] id=0x7f79a401d4e8: Running http1_connection_cross_thread_work task with <Running> status
[DEBUG] 2021-09-11 16:15:49.217 task-scheduler [140160541181696] id=0x7f79a4006060: Scheduling socket_written_task task for immediate execution
[DEBUG] 2021-09-11 16:15:49.217 task-scheduler [140160541181696] id=0x7f79a4006060: Running socket_written_task task with <Running> status
[DEBUG] 2021-09-11 16:15:49.217 task-scheduler [140160541181696] id=0x7f79a401d480: Scheduling http1_connection_outgoing_stream task for immediate execution
[DEBUG] 2021-09-11 16:15:49.217 task-scheduler [140160541181696] id=0x7f79a401d480: Running http1_connection_outgoing_stream task with <Running> status
[DEBUG] 2021-09-11 16:15:49.309 S3MetaRequest [140160541181696] id=0x1179b30 Incoming headers for request 0x7f79a4000e80. VIP connection: 0x7f79a0002550.
[DEBUG] 2021-09-11 16:15:49.309 S3MetaRequest [140160541181696] id=0x1179b30 Incoming headers for request 0x7f79a4000e80. VIP connection: 0x7f79a0002550.
[DEBUG] 2021-09-11 16:15:49.309 S3MetaRequest [140160541181696] id=0x1179b30 Incoming headers for request 0x7f79a4000e80. VIP connection: 0x7f79a0002550.
[DEBUG] 2021-09-11 16:15:49.309 S3MetaRequest [140160541181696] id=0x1179b30 Incoming headers for request 0x7f79a4000e80. VIP connection: 0x7f79a0002550.
[DEBUG] 2021-09-11 16:15:49.309 S3MetaRequest [140160541181696] id=0x1179b30 Incoming headers for request 0x7f79a4000e80. VIP connection: 0x7f79a0002550.
[DEBUG] 2021-09-11 16:15:49.309 S3MetaRequest [140160541181696] id=0x1179b30 Incoming headers for request 0x7f79a4000e80. VIP connection: 0x7f79a0002550.
[DEBUG] 2021-09-11 16:15:49.309 S3MetaRequest [140160541181696] id=0x1179b30 Incoming headers for request 0x7f79a4000e80. VIP connection: 0x7f79a0002550.
[DEBUG] 2021-09-11 16:15:49.309 S3MetaRequest [140160541181696] id=0x1179b30 Incoming body for request 0x7f79a4000e80. Response status: 400. Data Size: 369. VIP connection: 0x7f79a0002550.
[DEBUG] 2021-09-11 16:15:49.310 http-stream [140160541181696] id=0x7f79a4006ea0: Client request complete, response status: 400 (Bad Request).
[INFO] 2021-09-11 16:15:49.310 http-connection [140160541181696] id=0x7f79a401d3f0: Shutting down connection with error code 0 (AWS_ERROR_SUCCESS).
[DEBUG] 2021-09-11 16:15:49.310 task-scheduler [140160541181696] id=0x7f79a40077f0: Scheduling channel_shutdown task for immediate execution
[DEBUG] 2021-09-11 16:15:49.310 S3MetaRequest [140160541181696] id=0x1179b30: Request 0x7f79a4000e80 finished with error code 9223 and response status 400
[ERROR] 2021-09-11 16:15:49.311 S3MetaRequest [140160541181696] id=0x1179b30 Meta request cannot recover from error 9223 (Invalid response status from request). (request=0x7f79a4000e80, response status=400)
[INFO] 2021-09-11 16:15:49.311 http-connection [140160541181696] id=0x7f79a401d3f0: Shutting down connection with error code 0 (AWS_ERROR_SUCCESS).
[DEBUG] 2021-09-11 16:15:49.311 channel [140160541181696] id=0x7f79a40075f0: Channel shutdown is already pending, not scheduling another.
[DEBUG] 2021-09-11 16:15:49.311 task-scheduler [140160541181696] id=0x11ce7a8: Scheduling s3_client_process_work_task task for immediate execution
[DEBUG] 2021-09-11 16:15:49.311 tls-handler [140160541181696] id=0x7f79a40187b0: Alert code 0
[DEBUG] 2021-09-11 16:15:49.311 channel [140160541181696] id=0x7f79a40075f0: Channel shutdown is already pending, not scheduling another.
[DEBUG] 2021-09-11 16:15:49.311 task-scheduler [140160541181696] id=0x7f79a40077f0: Running channel_shutdown task with <Running> status
[DEBUG] 2021-09-11 16:15:49.311 channel [140160541181696] id=0x7f79a40075f0: beginning shutdown process
[DEBUG] 2021-09-11 16:15:49.311 channel [140160541181696] id=0x7f79a40075f0: handler 0x7f79a4018680 shutdown in read dir completed.
[DEBUG] 2021-09-11 16:15:49.311 tls-handler [140160541181696] id=0x7f79a40187b0: Shutting down read direction with error code 0
[DEBUG] 2021-09-11 16:15:49.311 channel [140160541181696] id=0x7f79a40075f0: handler 0x7f79a40187b0 shutdown in read dir completed.
[DEBUG] 2021-09-11 16:15:49.311 channel [140160541181696] id=0x7f79a40075f0: handler 0x7f79a401d3f8 shutdown in read dir completed.
[DEBUG] 2021-09-11 16:15:49.311 task-scheduler [140160541181696] id=0x7f79a4007618: Scheduling (null) task for immediate execution
[DEBUG] 2021-09-11 16:15:49.311 task-scheduler [140160541181696] id=0x11ce7a8: Running s3_client_process_work_task task with <Running> status
[DEBUG] 2021-09-11 16:15:49.311 S3Client [140160541181696] id=0x11ce610 s_s3_client_process_work_default - Moving relevant synced_data into threaded_data.
[DEBUG] 2021-09-11 16:15:49.311 S3Client [140160541181696] id=0x11ce610 s_s3_client_process_work_default - Processing any new meta requests.
[DEBUG] 2021-09-11 16:15:49.311 S3Client [140160541181696] id=0x11ce610 Updating meta requests with 'conservative' flag.
[DEBUG] 2021-09-11 16:15:49.311 S3MetaRequest [140160541181696] id=0x1179b30 Meta request finished with error code 9223 (Invalid response status from request)
[ERROR] 2021-09-11 16:15:49.311 S3CrtClient [140160541181696] S3CrtClient received error response for s3_meta_request with response code: 400, with error_code: 9223
[DEBUG] 2021-09-11 16:15:49.311 S3MetaRequest [140160541181696] id=0x1179b30 Cleaning up meta request
[DEBUG] 2021-09-11 16:15:49.311 S3MetaRequest [140160541181696] id=0x1179b30 Calling virtual meta request destroy function.
[DEBUG] 2021-09-11 16:15:49.311 S3MetaRequest [140160541181696] id=(nil) Calling meta request shutdown callback.
[DEBUG] 2021-09-11 16:15:49.311 S3CrtClient [140160541181696] Request returned error. Attempting to generate appropriate error codes from response
[TRACE] 2021-09-11 16:15:49.311 AWSErrorMarshaller [140160541181696] Error response is <?xml version="1.0"?>
<?xml version="1.0" encoding="UTF-8"?>
<Error>
    <Code>InvalidArgument</Code>
    <Message>The encryption method specified is not supported</Message>
    <ArgumentName>x-amz-server-side-encryption</ArgumentName>
    <ArgumentValue/>
    <RequestId>611FCVHEFF39R9R9</RequestId>
    <HostId>u8K4BIjPbYlrC6EjkuYPBOHX4J7jCW5mJdYopntBgKtI4gjK6BkpLRxVj9Bma03ILvHijWQ63NY=</HostId>
</Error>

[WARN] 2021-09-11 16:15:49.311 AWSErrorMarshaller [140160541181696] Encountered Unknown AWSError 'InvalidArgument': The encryption method specified is not supported
[ERROR] 2021-09-11 16:15:49.312 AWSClient [140160541181696] HTTP response code: 400
Resolved remote host IP address:
Request ID: 611FCVHEFF39R9R9
Exception name: InvalidArgument
Error message: Unable to parse ExceptionName: InvalidArgument Message: The encryption method specified is not supported
7 response headers:
connection : close
content-type : application/xml
date : Sat, 11 Sep 2021 16:15:49 GMT
server : AmazonS3
transfer-encoding : chunked
x-amz-id-2 : u8K4BIjPbYlrC6EjkuYPBOHX4J7jCW5mJdYopntBgKtI4gjK6BkpLRxVj9Bma03ILvHijWQ63NY=
x-amz-request-id : 611FCVHEFF39R9R9
[DEBUG] 2021-09-11 16:15:49.312 S3MetaRequest [140160541181696] id=(nil) Meta request clean up finished.

Additional context

Setting ServerSideEncryption::NOT_SET works fine with S3 non-CRT API.

[KaibaLopez]

Hi @rvernica ,
thanks for pointing this out, it does seem to me like a missing feature on the s3-crt ,and we'll try to get it fixed.
On the mean time though, I wanted to clarify just in case, by default the S3-crt will not add server side encryption, and so if you don't want any you don't need to explicitly set it.

[rvernica]

Fully understood. The code we have is general and sets it every time. As a workaround, for now, I added an additional if branch to only set it if needed. Let me know when this gets fixed.

[github-actions]

Greetings! Sorry to say but this is a very old issue that is probably not getting as much attention as it deservers. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to open a new one.