I have been using the mule-uploader plugin for a long time now - it was working beautifully up until a day ago (last I used it) and all of a suddenly it just stopped working. I have been combing through my code to see if it is something I introduced but found nothing - so I looked at the mule uploader demo and I'm receiving the same error when an upload initiates.
I get a SignatureDoesNotMatch error and if I load the S3 bucket call in a separate tab I get this:
<Code>InvalidRequest</Code>
<Message>
Key is not expected for the GET method ?uploads subresource
</Message>
<RequestId>FB2372E06BFF0480</RequestId>
<HostId>
Fmp0aQ3TRSfb/KyH1cAuiY00IIdrpIoPxQ+VukMLoKfmPqfn+jgofmvTyXbNmaC4
</HostId>
</Error>```
Any thoughts? I saw a post about something involving an S3 user being added to a group with proper permissions? Is this an IAM thing?
Never mind...as quickly as it didn't work last night, it now works just fine this morning for my project and the mule uploader. Weird...must something on the AWS side?
I have been using the mule-uploader plugin for a long time now - it was working beautifully up until a day ago (last I used it) and all of a suddenly it just stopped working. I have been combing through my code to see if it is something I introduced but found nothing - so I looked at the mule uploader demo and I'm receiving the same error when an upload initiates.
I get a SignatureDoesNotMatch error and if I load the S3 bucket call in a separate tab I get this: