Amazon SES
Amazon SES for fancy-flow — as four imported, versioned packages, one per runtime. Not vendored source: a copy cannot be upgraded, and third-party APIs change.
| Runtime | Package | Install |
|---|---|---|
| Authoring surface (every host) | @particle-academy/amazon-ses-ui |
npm install @particle-academy/amazon-ses-ui |
| Node | @particle-academy/amazon-ses-js |
npm install @particle-academy/amazon-ses-js |
| PHP 8.4+ | particle-academy/amazon-ses-php |
composer require particle-academy/amazon-ses-php |
| Python 3.11+ | fancy-amazon-ses |
pip install fancy-amazon-ses |
The ui package is the editor surface and is React on every host — a PHP or
Python project installs it and its own runtime package, and never the js one.
What it costs you
One dependency: @particle-academy/fancy-connector-core (or
particle-academy/fancy-connector-core on Composer), which the js and php
packages pull in themselves. The Python package has zero runtime
dependencies.
No Amazon SES SDK. Plain HTTP, deliberately: a vendor SDK is third-party code subject to the kit's full approval bar, and one per provider is hundreds of dependencies nobody is tracking.
Setting it up
Everything below is generated from provider/manifest.json, so it cannot disagree with what the packages do.
Credentials
A Amazon SES connection holds 3 values.
Every value here is account scope: one per connected account, not one per installation.
| Field | Scope | Secret | Where it comes from |
|---|---|---|---|
| Access key ID | per connected account | not secret | AKIA... from an IAM user or role with ses:SendEmail. Not secret on its own -- it identifies the key, and the secret below is what proves it. |
| Secret access key | per connected account | secret | Shown ONCE when the key is created. It is never sent: it derives the signing key, and only the signature goes over the wire. |
| Region | per connected account | not secret | Part of the HOST and part of the SIGNATURE, so a mismatch fails as a signature error rather than as a wrong-endpoint one. Verified identities are per-region: a domain verified in us-east-1 does not exist in eu-west-1. |
The estate
Amazon SES has NO test estate that can be selected. Same credentials, same endpoints, same estate — only the AUDIENCE is restricted. A run against it looks completely successful and reaches nobody.
A new SES account is in the SANDBOX, and it is the reason
restricted-reachexists as a value. The endpoint is identical, the credentials are identical, the request is identical, and the API answers 200 with a MessageId -- but the mail only reaches addresses you have verified. Anyone else is silently discarded. So a sandbox run looks completely successful and reached nobody, which is whyrestricted-reachcannot be selected as a mode: there is nothing to select. You leave the sandbox by asking AWS for production access, not by pointing at a different host.
What it can do
Actions
email_send — Send email
Send an email through Amazon SES.
POST /v2/email/outbound-emails · unsafe to replay — a retried durable run does it TWICE
| Input | Required | What it is |
|---|---|---|
from |
yes | Must be a VERIFIED identity in this region. An address verified in another region does not exist here. |
to |
yes | One address, a comma-separated list, or an expression. While the account is in the SES sandbox, anything not verified is accepted by the API and silently never delivered. |
cc |
no | Cc |
replyTo |
no | Reply-To |
subject |
yes | Subject |
text |
no | Plain-text body |
html |
no | HTML body |
configurationSet |
no | Optional. SES routes engagement events (bounces, complaints, opens) through the set you name. |
Run it before you have credentials
Every operation ships a faker, whether or not Amazon SES has a sandbox. Set a
node's mode to fake and it returns the shape Amazon SES actually publishes — the
same field names, deterministically — so you can wire the downstream nodes before
touching an account, a key, or a network.
This repository is generated
provider/ is the source. Everything under packages/ is emitted from it and
must not be hand-edited — CI regenerates and diffs on every push, and the
next protocol sync destroys anything it finds. See AGENTS.md.
Two namespaces, which do not match on purpose
The repo is github.com/Fancy-Friends/amazon-ses; the packages publish under
particle-academy. Nothing derives one from the other — the names come from
weaver's friends.json and nowhere else.
Licence
MIT.
Metadata
Release files for fancy-amazon-ses 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| fancy_amazon_ses-0.4.0.tar.gz | 25.5 kB | Without provenance | Details for fancy_amazon_ses-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| fancy_amazon_ses-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for fancy_amazon_ses-0.4.0-py3-none-any.whl |
Total release size: 49.8 kB
Release files / fancy_amazon_ses-0.4.0.tar.gz
| Download URL | fancy_amazon_ses-0.4.0.tar.gz |
|---|---|
| Size | 25.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7f9f58559f1744fc99ec7d46ee8af8689234f6d96d9e98770802f771547ee6d8
|
|
BLAKE2b-256 checksum How to use checksums |
73c7ba2f59649b4850af58ef5ddbaf28f368abaea3f7c114771f54361b44bcc1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.18
|
Release files / fancy_amazon_ses-0.4.0-py3-none-any.whl
| Download URL | fancy_amazon_ses-0.4.0-py3-none-any.whl |
|---|---|
| Size | 24.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
310074251606ace20e455bcb1236d748e78cadbea9e21aac29aff4b773e2c410
|
|
BLAKE2b-256 checksum How to use checksums |
20c21c64df4880f93b1c4abd0044fa4b356071f4c9332bf14c6633f672db459f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.18
|
Security for fancy-amazon-ses 0.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.