The postman collection that executes successfully on Azure, GCP and IBM but fails on AWS
The following collection works successfully in GCP and IBM environments in the Platform Validation project. But it fails to run in Azure and AWS environments.
FileAPI_UploadDownload_CI-CD_v2.0.postman_collection.json
In Azure environment, @krveduru @ankurrawat Request 2.UploadFile by SignedURL fails with response code 400 An HTTP header that's mandatory for this request is not specified The API doc is not clear as to what needs to be specified and the same request works in GCP and IBM environment Reponse:
MissingRequiredHeader
An HTTP header that's mandatory for this request is not specified.
RequestId:3d3902d8-501e-0092-3544-50f68a000000
Time:2022-04-14T21:15:09.4287412Z
x-ms-blob-type
In AWS environment, @fhoueto.amz Request 3. Create File Metadata R3 fails with response code 500 Internal Server Error Reponse: { "error": { "code": 500, "message": "Internal server error", "errors": [ { "domain": "global", "reason": "internalError", "message": "Internal server error" } ] } }
The file being uploaded is a las file (7004_a1501_1978_comp.las) from TNO data. FYI - @dzmitry_malkevich @anujgupta @debasisc @ChrisZhang