---
title: "Validate BYO-AWS credentials"
method: POST
path: "/v1/projectId/{projectId}/aws-check"
tags: ["BYO AWS"]
---

# Validate BYO-AWS credentials

`POST /v1/projectId/{projectId}/aws-check`

## Request

- Base URL: `https://api.bluefox.email`
- URL: `https://api.bluefox.email/v1/projectId/{projectId}/aws-check`
- Auth: HTTP bearer

Checks credentials directly against SES - confirms they work, every sender identity is actually verified in SES, and the requested limit is within the account's max send rate. Does not persist anything - pair with PATCH /v1/projectId/{projectId} to save. Only relevant for BYO-AWS projects; calling this with nothing stored and no override fields will fail since there is nothing to check - that is not itself a sign anything is misconfigured, most projects simply do not use BYO-AWS. Use GET .../production-access for a project on bluefox.email's shared infrastructure instead.

## Path parameters

- `projectId` string, required

## Request body

- AwsCheckInput: Every field is optional - omit any of them to check against what's already stored on the project instead.
  - `roleArn` string
  - `accessKeyId` string
  - `secretAccessKey` string
  - `region` string
  - `limit` integer
  - `senderIdentities` object[]
    - `_id` string
    - `name` string
    - `email` string

## Response `200`

OK

- object
  - `status` integer
  - `result` object
    - `success` boolean

## Other responses

- `400`: Invalid request body or query - every violation found (missing/invalid/unexpected fields) is reported in one response, semicolon-separated, not just the first one hit.
- `403`: Missing or invalid API key

---

[API](https://skmtc.dev/bluefox/apis/bluefox-email-public-api.md) · [All operations](https://skmtc.dev/bluefox/apis/bluefox-email-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/bluefox/apis/bluefox-email-public-api/revisions/fa1a0a835c7f?raw)