En utilisant AWS re:Post, vous acceptez les AWS re:Post Conditions d’utilisation
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.

Sujets
Web et mobile front-endApplications commerciales
Balises
Simple service d’e-mail Amazon
Langue
English
rik2803
demandé il y a 2 ans960 vues
1 réponse
1
Réponse acceptée

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
INGÉNIEUR EN ASSISTANCE TECHNIQUE
Ron_H
répondu il y a 2 ans
  • rik2803
    il y a 2 ans

    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.

Vous n'êtes pas connecté. Se connecter pour publier une réponse.

Une bonne réponse répond clairement à la question, contient des commentaires constructifs et encourage le développement professionnel de la personne qui pose la question.

Instructions pour répondre aux questions

Contenus pertinents