https://github.com/aidansteele/ses-sidecar
An SMTP server sidecar to allow AWS SES usage with IAM roles
https://github.com/aidansteele/ses-sidecar
aws aws-ses smtp
Last synced: 6 months ago
JSON representation
An SMTP server sidecar to allow AWS SES usage with IAM roles
- Host: GitHub
- URL: https://github.com/aidansteele/ses-sidecar
- Owner: aidansteele
- Created: 2023-02-07T02:12:40.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2023-02-07T02:52:58.000Z (over 2 years ago)
- Last Synced: 2025-03-28T18:51:59.545Z (6 months ago)
- Topics: aws, aws-ses, smtp
- Language: Go
- Homepage:
- Size: 4.88 KB
- Stars: 17
- Watchers: 3
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# ses-sidecar
## Usage
```
docker run -it \
-p 1025:1025 \
-e ADDR=0.0.0.0:1025 \
-e AWS_ACCESS_KEY_ID \
-e AWS_SECRET_ACCESS_KEY \
-e AWS_SESSION_TOKEN \
-e AWS_REGION \
ghcr.io/aidansteele/ses-sidecar:latest
```
This will start an SMTP server listening on port 1025 that uses the AWS SES
SendRawEmail API to deliver email. In practice, you wouldn't pass credentials
like this example, you would associate an IAM role with the container via your
orchestration system, e.g. an ECS task IAM role or EKS IRSA service account role.
That role needs `ses:SendRawEmail` permission.
This is a proof-of-concept, but it works and can be deployed as a sidecar to
your application. It exists because (as of the time of writing) the SES SMTP
service doesn't work with temporary credentials, which are a security best-practice.
File an issue if you have any problems / feature requests.