Getting "not implemented" errors on calls that work with s3cmd

[JetForMe]

I'm using soto to communicate with Digital Ocean’s S3-compatible spaces. I'm able to upload files okay, but now I'm trying to call getObjectAcl, and I get "not implemented" errors. I find it next to impossible to figure out where in the code the actual response is coming from, so I can examine it for further information. If I install a debug logger on the request, I get this:

(my logging): Checking asset USGS_13_n35w119_20240207.tif
2024-08-11T21:29:34-0700 debug S3Logger : aws-operation=GetObjectAcl aws-request-id=1 aws-service=s3 [SotoCore] AWS Request
2024-08-11T21:29:35-0700 debug S3Logger : aws-error-code=NotImplemented aws-error-message= aws-operation=GetObjectAcl aws-request-id=1 aws-service=s3 [SotoCore] AWS Error
2024-08-11T21:29:36-0700 debug S3Logger : aws-error-code=NotImplemented aws-error-message= aws-operation=GetObjectAcl aws-request-id=1 aws-service=s3 [SotoCore] AWS Error
2024-08-11T21:29:37-0700 debug S3Logger : aws-error-code=NotImplemented aws-error-message= aws-operation=GetObjectAcl aws-request-id=1 aws-service=s3 [SotoCore] AWS Error
2024-08-11T21:29:41-0700 debug S3Logger : aws-error-code=NotImplemented aws-error-message= aws-operation=GetObjectAcl aws-request-id=1 aws-service=s3 [SotoCore] AWS Error
2024-08-11T21:29:48-0700 debug S3Logger : aws-error-code=NotImplemented aws-error-message= aws-operation=GetObjectAcl aws-request-id=1 aws-service=s3 [SotoCore] AWS Error
(my logging): Asset check failed: NotImplemented: 

However, if I use s3cmd info on the object, it comes back immediately with plenty of info:

s3://simplishare/misc/posts/2024-08/<redacted> (object):
   File size: 457921971
   Last mod:  Sat, 10 Aug 2024 04:57:14 GMT
   MIME type: image/tiff
   Storage:   STANDARD
   MD5 sum:   <redacted>
   SSE:       none
   Policy:    none
   CORS:      none
   ACL:       *anon*: READ
   ACL:       2324324: FULL_CONTROL
   URL:       <redacted>

Digital Ocean claims to support GetObjectAcl: https://docs.digitalocean.com/products/spaces/reference/s3-compatibility/

Side note: getObjectAttributes takes 30 seconds to complete, and returns all nil values.

[adam-fowler]

Have you disabled HTTP2 on your HTTPClient? Digital Ocean's HTTP2 implementation for their spaces is borked you have to force the HTTP client to be http1.1 only. See #608

Use

AWSClient(
    ...
    httpClient: HTTPClient(
        eventLoopGroupProvider: .singleton,
        configuration: .init(httpVersion: .http1Only)
    )    
)

[JetForMe]

Ah, thank you for that information. I had to create like this (there’s no Configuration.init() that takes httpVersion in async-http-client v1.21.2):

			var config = HTTPClient.Configuration()
			config.httpVersion = .http1Only
			let client = AWSClient(
				credentialProvider: .static(accessKeyId: accessKey, secretAccessKey: secretKey),
				httpClient: HTTPClient(eventLoopGroupProvider: .singleton, configuration: config),
				logger: Logger(label: "S3Logger")
			)

The Acl request now returns. getObjectAttributes still takes a long time and returns all nils for the response. But headObject works, so I'll just use that.

For completeness, getObjectAttributes logs

2024-08-12T14:36:53-0700 debug S3Logger : aws-operation=GetObjectAttributes aws-request-id=1 aws-service=s3 [SotoCore] AWS Request
2024-08-12T14:36:53-0700 debug S3Logger : ahc-connection-id=0 ahc-el=NIOTransportServices.NIOTSEventLoop aws-operation=GetObjectAttributes aws-request-id=1 aws-service=s3 [AsyncHTTPClient] Request was scheduled on connection

And seemingly exactly one minute later returns a result like:

Attrs: GetObjectAttributesOutput(checksum: nil, deleteMarker: nil, eTag: nil, _lastModified: SotoCore.OptionalCustomCoding<SotoCore.HTTPHeaderDateCoder>(value: Optional(2024-08-10 04:57:14 +0000)), objectParts: nil, objectSize: nil, requestCharged: nil, storageClass: nil, versionId: nil)

Perhaps it's timing out, but I'd expect an error to be thrown in that case.

Looking at the list of supported calls, I don't see that one in there, but maybe it has a different name?

Is there a way to see the raw request and response (headers, and body if not too large)?

[adam-fowler]

You can add the Logging middleware which logs server requests/responses

let client = AWSClient(
    ...
    middlewares: AWSLoggingMiddleware(logger: logger, logLevel: .info)
    ...
)

[JetForMe]

Lovely!