Parse Server SES Adapter throwing errors and crashing container

parse-server-simple-ses-adapter throws an error and crashes the parse server

My package.json file :

  "name": "server",
  "version": "1.0.0",
  "type": "commonjs",
  "target": "esnext",
  "description": "Server API",
  "main": "index.js",
  "scripts": {
    "start": "env-cmd -e development nodemon --inspect= index.js",
    "start:dev": "node index.js",
    "start:prod": "node index.js"
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "env-cmd": "^10.1.0",
    "nodemon": "^2.0.15"
  "dependencies": {
    "archiver": "^5.3.1",
    "body-parser": "^1.20.0",
    "express": "^4.17.3",
    "method-override": "^3.0.0",
    "parse": "^3.4.1",
    "parse-server": "^5.2.1",
    "parse-server-simple-ses-adapter": "^1.1.1",
    "zip-stream": "^4.1.0"

  Type: 'Sender',
  Code: 'MessageRejected',
  Message: 'Email address is not verified. The following identities failed the check in region US-EAST-2: [email protected]'
          throw err;

[UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "#<Object>".] {
[nodemon] app crashed - waiting for file changes before starting...

AWS SES is throwing an error, because you try to send from/to an unverified email. This is a feature of SES to prevent spam. Check their docs on AWS SES on how to verify emails, this needs to be configured within the AWS account.

Yeah, as @Frank500 said, while you are in Sandbox mode, you need to verify the email addresses you want to send to. There’s a section called “verified identities” (or similar) where you can add the email address you’re trying to send to.

AWS will send you an email with a link. Once you’ve clicked on the link to verify it, you should be able to send.

Once you’re done developing and want to go to production, you’ll need to go through a verification process for your sending domain and obviously add some dns for that domain too.