Usando AWS re:Post, accetti AWS re:Post Termini di utilizzo
AWS re:Postre:Post

SES Delegate Sender and ConfigurationSetDoesNotExist

0

I have a setup in which several AWS accounts need to send mails for a given domain. I configured SES on a shared account, and SES delegate sending on other accounts.

Everything worked fine, until I attached a Configuration Set to the SES identity (the domain) on the shared account. From that moment on:

  • Sending mails with credentials for the shared account keeps working as expected, including the functionalities of the Configuration Set
  • BUT sending mails from the delegate sender account started failing with ConfigurationSetDoesNotExist errors

I guess this is related to missing permissions, but I do not find how to grant (delegate) permissions for the Configuration Set for the account that is configured as delegate.

Anyone managed to get this working?

Thanks.

Argomenti
Front-end web e dispositivi mobiliApplicazioni aziendali
Tag
Amazon Simple Email Service
Lingua
English
rik2803
posta 2 anni fa959 visualizzazioni
1 Risposta
1
Risposta accettata

Hello, rik2803,

I reviewed your post and did some research internally here at AWS, noting a case opened (and closed) the same date this post was entered. I see from that case you believe you found the solution, but I wanted to provide a link to SES documentation on the topic of "Sending Authorization" (1) for reference. If you do need assistance, you can reopen the case you previously closed.

RESOURCES

  1. Using sending authorization with Amazon SES - https://docs.aws.amazon.com/ses/latest/dg/sending-authorization.html
  2. Sending emails for the identity owner for Amazon SES sending authorization - https://docs.aws.amazon.com/ses/latest/dg/sending-authorization-delegate-sender-tasks-email.html
AWS
TECNICO DI SUPPORTO
Ron_H
con risposta 2 anni fa
  • rik2803
    2 anni fa

    Thanks for the feedback Ron, that's exactly how I solved it. I wanted the notifications to be sent to the AWS account that owns the SES identity, but was a bit misled because the SES console does not allow SNS topics in other accounts when configuring the notification destination. Turned out that this is possible using the AWS CLI. Of course, I had to update the topic access policy.

    Everything is working as expected.

Accesso non effettuato. Accedi per postare una risposta.

Una buona risposta soddisfa chiaramente la domanda, fornisce un feedback costruttivo e incoraggia la crescita professionale del richiedente.

Linee guida per rispondere alle domande

Contenuto pertinente