Yenfry Herrera Feliz

Hi @neophytte, thanks for opening this issue. That regular expression it is actually a valid one, it is just that the forward slash is not coming with the escaping character...

Hi @nprasovict, thanks for opening this issue. Could you please try with the latest version?, which is @aws-sdk/[email protected]. I did test it and I got not issues. Also you can...

Hi @llh-check, thanks for opening this issue. Could you please provide more details about how exactly you are getting this error? Thanks!

Hi @dmarczydlo, thanks for opening this issue. I was trying to reproduce the reported behavior but by using the code below I was able to use custom endpoint. Please see:...

Hi @DahShahar, thanks for opening this issue. I tried multiple times to reproduce the reported behavior, but in my tests I got successful results each try. I know you mentioned...

Hi @spencerwilson, thanks for opening this issue. Some of the headers are not signed by default to prevent signature mismatch errors. However, you can specify which headers you would like...

> If there's a good reason for omitting it by default, could the default behavior + rationale be documented? @spencerwilson I will bring this to discussion to the team to...

Hi @spencerwilson, after doing some researches I found that that header "content-type" along with others are black listed by default to prevent signature mismatch errors. I could not find any...

Hi @batflarrow, thanks for reaching out. By looking at the error that you provided, seems like at the time the request is being made not credential provider was available, and...

>Currently we are using IAM policy to provide the credentials so should this be added in addition to that? Also assuming our service is deployed in ecs then should we...