# AWS Credentials - POST Request

**URL:** <https://community.n8n.io/t/aws-credentials-post-request/212745>\
**Category:** Questions\
**Created:** [October 28, 2025, 7:13am UTC](https://community.n8n.io/t/aws-credentials-post-request/212745 "2025-10-28T07:13:14Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joshua\_F](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/joshua_f/32/132837_2.png) [@Joshua\_F](https://community.n8n.io/u/Joshua_F)\
**Post date:** [October 28, 2025, 7:13am UTC](https://community.n8n.io/t/aws-credentials-post-request/212745/1 "2025-10-28T07:13:14Z")

</div>

**Hey everyone 👋**

**tl;dr:**  
Postman AWS Signature → works ✅  
n8n AWS auth → `InvalidSignatureException: Credential should be scoped to a valid region.` 😤

I’ve been working on an n8n workflow that creates shipments by sending a POST request to an AWS API Gateway endpoint.

It works perfectly in Postman, but when I run it in n8n, I keep getting the following error:

```auto
{
  "message": "Credential should be scoped to a valid region."
}

```

In Postman, I’m using **AWS Signature (SigV4)** auth with the same access key, secret key, region (`ca-central-1`), and service (`execute-api`), and it works perfectly.

In n8n, I’m using the built-in AWS credentials, and while the request signs and sends, AWS rejects it with the “invalid region scope” error.

**Current n8n HTTP Request Node setup:**

```auto
- Authentication: Predefined Credential Type → AWS
- Region: ca-central-1
- Service: execute-api
- Method: POST
- URL: https://lzj4acib8d.execute-api.ca-central-1.amazonaws.com/prod/shipments
- Headers:
    Content-Type: application/json
    x-api-key: <API key>

```

I know the JSON payloads are valid — I manually posted them from Postman successfully.  
The API key is correct (you can see it in the screenshots).  
I even tried switching the region to `us-east-1` as some suggested, but that didn’t fix it either.

[![r/n8n - AWS Credentials - POST Request|526.4672036823936xauto](https://europe1.discourse-cdn.com/n8n/original/3X/4/b/4b8fc629bda0233259e72f6bf834554419d0a78d.png)](https://preview.redd.it/aws-credentials-post-request-v0-9vm3yzziopxf1.png?width=610&format=png&auto=webp&s=bcd8e8ac53549673f24811c5df6a0634f7fefe21 "Image from r/n8n - AWS Credentials - POST Request")

# Additional context

I actually **had this same setup working in our demo environment** (screenshot below).  
In that case, the request succeeded when I used a **Bearer token + API key** , both sent through headers.

For production, the Bearer token is _not required_, since I’m already authenticated via AWS keys.

[![r/n8n - AWS Credentials - POST Request|542.2297297297298xauto](https://europe1.discourse-cdn.com/n8n/original/3X/f/a/fad07a4c1f8afda899ab24b523cc44739872a52d.png)](https://preview.redd.it/aws-credentials-post-request-v0-v94to385qpxf1.png?width=642&format=png&auto=webp&s=c6190031a8951794d455c9935a9d75bf48d28e16 "Image from r/n8n - AWS Credentials - POST Request")

My theory: n8n might not be properly scoping the signature to `ca-central-1/execute-api`,  
or API Gateway expects a slightly different canonical header order than n8n generates.

Any help or working example configs would be super appreciated — I’m 99% sure the setup is right, but AWS keeps saying my signature is scoped wrong 😅

---

<div class="post-metadata">

**Author:** ![Jinki](https://avatars.discourse-cdn.com/v4/letter/j/df788c/32.png) [@Jinki](https://community.n8n.io/u/Jinki)\
**Post date:** [November 17, 2025, 10:59am UTC](https://community.n8n.io/t/aws-credentials-post-request/212745/2 "2025-11-17T10:59:57Z")

</div>

I’m experiencing the same issue.

It looks like n8n is not generating the standard headers correctly. It used to work fine for me before, so I hope this can be fixed/updated quickly.

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/system/32/195824_2.png) [@system](https://community.n8n.io/u/system)\
**Post date:** [February 15, 2026, 11:00am UTC](https://community.n8n.io/t/aws-credentials-post-request/212745/3 "2026-02-15T11:00:19Z")

</div>

Closed on February 15, 2026, 11:00am UTC

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.