# AWS Authentication Problem with POST/PUT but GET/DELETE work fine

**URL:** <https://community.postman.com/t/aws-authentication-problem-with-post-put-but-get-delete-work-fine/1343>\
**Category:** Help Hub\
**Created:** [March 31, 2018, 6:30pm UTC](https://community.postman.com/t/aws-authentication-problem-with-post-put-but-get-delete-work-fine/1343 "2018-03-31T18:30:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mr.curtis.olson](https://avatars.discourse-cdn.com/v4/letter/m/8c91f0/32.png) [@mr.curtis.olson](https://community.postman.com/u/mr.curtis.olson)\
**Post date:** [March 31, 2018, 6:30pm UTC](https://community.postman.com/t/aws-authentication-problem-with-post-put-but-get-delete-work-fine/1343/1 "2018-03-31T18:30:06Z")

</div>

I have a small set of API end points using AWS API Gateway & Lamda developed with the Serverless framework. All work fine from using the Serveless CLI tool Though Postman, I get this error with POST and PUT commands.

```
{
    "message": "The request signature we calculated does not match the signature you provided. Check 
    your AWS Secret Access Key and signing method. Consult the service documentation for details."
}

```

However, GET and DELETE commands work fine. I have the authentication set at Collection level so all 4 types of queries use the same authentication. It has to be that POST and PUT have a request body and the other two don’t. The requests must be getting assembled differently.

I saw one POSTMAN bug reported about a year ago with a similar issue trying to upload an attachment. It doesn’t look like that bug got fixed.

Anyone else able to connect to AWS API Gateway with API Key and Secret key?

---

<div class="post-metadata">

**Author:** ![danny-dainton](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/danny-dainton/32/29401_2.png) [@danny-dainton](https://community.postman.com/u/danny-dainton)\
**Post date:** [April 29, 2025, 3:55pm UTC](https://community.postman.com/t/aws-authentication-problem-with-post-put-but-get-delete-work-fine/1343/2 "2025-04-29T15:55:41Z")

</div>

Closed on April 29, 2025, 3:55pm UTC