henry3260 commented on issue #57964:
URL: https://github.com/apache/airflow/issues/57964#issuecomment-3513378764
> > > Could someone clarify, why email operator is SES incompatible? We are
using it - it works without problems
> >
> >
> > In the latest Airflow version, the EmailOperator doesn’t support AWS SES
yet.
>
> Ok, maybe I suppose another sense of the word `incompatible`. In Airflow
3.1.0 using AWS connection and some env vars in its helm chart:
>
> ```
> - name: AIRFLOW__EMAIL__EMAIL_BACKEND
> value: "airflow.providers.amazon.aws.utils.emailer.send_email"
> - name: AIRFLOW__EMAIL__EMAIL_CONN_ID
> value: "aws_conn"
> - name: AIRFLOW__EMAIL__FROM_EMAIL
> value: "..."
> ```
>
> and this code somewhere in the DAG:
>
> ```
> send_email = EmailOperator(
> task_id="send_email",
> to=self.dag_config.recipients,
> subject=f"Airflow: {self.dag_config.dag_description}:
" + "{{ ds }}",
> html_content="...",
> )
> ```
>
> we are receiving emails from Amazon SES successfully.
Yes, you are right, that setup works perfectly. The limitation is that
EmailOperator itself doesn't expose all the advanced parameters that the
underlying SesHook (which it calls in the background) actually supports.
So you can't use SES-specific features like return_path or reply_to, even
though the hook could handle them."
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
