convez.ai
SkillDevOps & InfraestruturaAvançado
junxit

AWS SES Detailed Error Relay

junxit/claude-skill-aws-ses-detailed-error-relay

Captura e retransmite erros SES com códigos SMTP via Lambda + SNS

Ver no GitHub
InicialPluginScore · de 0 a 100

Skill para Claude Code que configura Amazon SES para capturar notificações detalhadas de bounce e complaint (incluindo códigos SMTP que o feedback padrão omite) e retransmitir um aviso limpo ao remetente original. Automatiza a configuração de SNS, Lambda e SQS para tratamento robusto de erros de entrega.

Instalação

$npx convez-ai junxit/claude-skill-aws-ses-detailed-error-relay

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
42%
Último commit
há 5 meses
Versão
—
Issues abertas
0
Contribuidores
1

Casos de uso

  • Monitorar entregas de email em produção com diagnósticos completos
  • Implementar fluxo de feedback de bounces/complaints em aplicações
  • Automatizar notificação de falhas de entrega aos operadores

Veredito

Ferramenta especializada e bem documentada para quem precisa gerenciar SES em produção. Reduz significativamente a complexidade de capturar e processar notificações de entrega, mas exige conhecimento sólido de AWS (IAM, Lambda, SNS, SQS) e está voltada para casos de uso específicos de email transacional.

README

A tradução para o português deste README ainda está na fila.

claude-skill-aws-ses-detailed-error-relay

Installs as the Claude Code skill aws-ses-bounce-notification-config — the install directory must use that name (Claude Code matches the directory to the skill's name:), even though the repo is named differently.

A Claude Code skill that configures Amazon SES to capture detailed bounce and complaint notifications — including the SMTP status code (e.g. 5.1.1) and the remote MTA diagnostic that SES's built-in email feedback forwarding leaves out — and relays a clean notice back to the original sender.

Invoke it from Claude Code:

/aws-ses-bounce-notification-config [target-directory]

The skill reasons with you about the design choices, validates your AWS permissions, generates a self-contained AWS-CLI project, deploys it after your confirmation, and verifies it end-to-end with the SES mailbox simulator. Nothing is hard-coded to one account or identity — the account is discovered at runtime.

What it sets up

flowchart LR
    SEND["SES send<br/>(verified identities)"]
    SEND -->|"bounce / complaint<br/>(identity notifications<br/>OR config-set destination)"| RT["SNS topic"]
    SEND -.->|"feedback forwarding<br/>(ON by default: body, no code)"| SENDER
    RT -->|invoke| L["Lambda relay<br/>(Python)"]
    L -->|"SES SendEmail<br/>from bounces@&lt;domain&gt;"| SENDER["Original sender<br/>(or a fixed ops inbox)"]
    L -.->|errors → retry| DLQ["SQS DLQ"]

Two capture approaches (you choose)

Topic per identityTopic per config set
Mechanismset-identity-notification-topic per identity (SES v1)one event destination on a configuration set
Scopeper identity (wire each)uniform across all identities using the config set
New identitiesmust be re-wiredrelay automatically
Disable forwardingalways supportedusually, not guaranteed
Needs a config setnoyes (sends must use it)

Full trade-off in reference/approaches.md.

What the skill does (workflow)

  1. Reason — discovers your identities/config sets, then settles region, capture mechanism, delivery mode (both-emails vs relay-only), and relay recipient with you.
  2. Generate — stamps the assets/ templates into a target project and writes config.env + a tailored README.md.
  3. Validate permissions — runs preflight.sh (identity, read probes, and a best-effort iam:SimulatePrincipalPolicy of the exact deploy actions).
  4. Deploy — after explicit confirmation, runs the idempotent deploy.sh.
  5. Verify — fires the mailbox simulator (no reputation impact), checks the logs and DLQ, confirms the relay arrived.

Layout

claude-skill-aws-ses-detailed-error-relay/   # repo root (installs into ~/.claude/skills/aws-ses-bounce-notification-config/)
├── SKILL.md                    # the orchestration runbook Claude follows
├── README.md                   # this file
├── reference/
│   ├── approaches.md           # topic-per-identity vs topic-per-config-set, deep dive
│   └── permissions.md          # required actions, validation, least-privilege role
└── assets/                     # parameterized templates the skill generates from
    ├── lambda_function.py      # the relay handler (Python; runs on Lambda)
    ├── config.env.example      # single source of truth every script sources
    ├── preflight.sh            # permission validation
    ├── deploy.sh               # idempotent AWS CLI provisioner (both capture modes)
    ├── teardown.sh             # idempotent reverse
    ├── enable_forwarding.sh    # → both emails (Option B)
    ├── disable_forwarding.sh   # → relay-only
    ├── send_simulator.sh       # mailbox-simulator end-to-end test
    ├── README.template.md      # README rendered into the generated project
    └── iam/                    # IAM/SNS policy templates (__TOKENS__ rendered at deploy)

Requirements

  • Claude Code (to invoke the skill).
  • On the machine that deploys: AWS CLI v2, jq, zip, and credentials for the target account (a scoped IAM user/role is preferred over root — preflight.sh warns on root).

Install (local)

Clone into the skill directory — its name must be the skill name (aws-ses-bounce-notification-config), not the repo name:

git clone <repo-url> ~/.claude/skills/aws-ses-bounce-notification-config
# or, from a local checkout of the repo:
cp -r ./claude-skill-aws-ses-detailed-error-relay/. ~/.claude/skills/aws-ses-bounce-notification-config/

It is auto-discovered (no restart needed) and available as /aws-ses-bounce-notification-config in any project. Verify with /help or by typing /aws- at the prompt.

Uninstall

Removing the skill just deletes its directory:

rm -rf ~/.claude/skills/aws-ses-bounce-notification-config

Important: uninstalling the skill does not touch any AWS resources you deployed with it. Those live in your AWS account, not here. To remove them, first run ./teardown.sh (add --logs to drop the log group too) inside the generated project the skill created for you, then delete the skill. If you had switched to relay-only mode, run ./enable_forwarding.sh before teardown to restore SES's forwarded notices. Deleting only the skill folder leaves the deployed relay running.

License

MIT — see LICENSE.

Ver o original no GitHub

Bom para

Relacionados