I have spent at least a year working with Customer Support and Dev on the most basic of REST calls POST/GET to AWS. It does not work. The first ticket that I entered I performed a sid by side test using Postman and Soapui Pro.
Providing both with identilcle Secret/Key. Postman worked perfectly fine while SoapUI failed to execute. The initial bug was that Soapui dynamic generation of the authitication header was nonexistant. Begging the question, how did it ever work to begin with. After 6 to 8 monthes I recieved a build with a fix. The next failure was in performing a GET. Apparently AWS published an issue for GETS, as they have no payloads. SoapUI doesn't handle this issue either. Its been 3 to 4 months of chasing down this issue and I'm waiting for th enext release which shold have the fix in it.
I'm puzzled how anyone doing cloud testing with AWS has done anything with this tool in the past year. Is there something unique about serverles testing and the use of S3 buckets.
Solved! Go to Solution.
Thank you richie!
Hi @sprice090161 , that would be great if you could expand your description a little. Please provide us with the additional info richie is requesting and the Community will try to help you further. Thank you.
Here is the initial case that I submitted. There was a defect found as I said before pertaining the dynamic generation of the header value.
From Customer Support
"Development has created a defect of RIA-11463 for this issue as the x-amz-security-token header isn't signed in the AWS signature. "