So the short answer is 'Yes'.
cURL and S3 can live happily with AwareIM via a plugin. I still need to clean up a few things however it seems to work fine.
The longer answer is proven with the verbose result (removed ID from the output).
"Result:
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0*
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0*
100 2239 0 0 100 2239 0 1432 0:00:01 0:00:01 --:--:-- 1431
100 2239 0 0 100 2239 0 1453 0:00:01 0:00:01 --:--:-- 1452
< HTTP/1.1 200 OK
< HTTP/1.1 100 Continue
} [2239 bytes data]
- We are completely uploaded and fine
Trying 52.95.132.13...
Connected to s3-ap-southeast-2.amazonaws.com (52.95.132.13) port 80 (#0)
PUT /eighouh1/TA.tar.gz HTTP/1.1
Host: s3-ap-southeast-2.amazonaws.com
User-Agent: curl/7.47.0
Accept: /
x-amz-content-sha256: xxxxxxxxxxxxx
x-amz-date: 20170124T133401Z
Authorization: xxxxxxxxx Credential=xxxxxxxxx/20170124/ap-southeast-2/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=xxxxxxxxx
Content-Length: 2239
Expect: 100-continue
< x-amz-id-2: xxxxxxxxxxxxxxxxxxxx
< x-amz-request-id: xxxxxxxxxxxxxxxx
< Date: Tue, 24 Jan 2017 13:34:01 GMT
< ETag: "xxxxxxxxxxxxxxxx"
< Content-Length: 0
< Server: AmazonS3
<
- Connection #0 to host s3-ap-southeast-2.amazonaws.com left intact"