Gerda Ilger created CAMEL-19761:
-----------------------------------
Summary: camel-aws2-ses: Upgrade to SESV2Client
Key: CAMEL-19761
URL: https://issues.apache.org/jira/browse/CAMEL-19761
Project: Camel
Issue Type: Improvement
Components: camel-aws2
Affects Versions: 4.x
Reporter: Gerda Ilger
As [discussed on January 16,
2023|https://lists.apache.org/thread/vywggwhj2v48j6j4v9rx49bq1kbks5h5]:
aws2-ses is based on Amazon' AWS v2 SES v1 client, which has a 10 MB per
message limit.
In order to send messages up to 40 MB, we'll need to switch to Amazon’s
SESV2Client. [[1] |[https://docs.aws.amazon.com/ses/latest/dg/quotas.html]]
Duplicating the aws2-ses component and upgrading the SES client seems to do the
trick. It would look something like this:
[https://github.com/gerdailger/camel/compare/master...feat_camel_aws2_ses2]
As suggested by Andrea Consentino, creating a JIRA issue to discuss the best
way to merge & whether it would be better to have only one component based on
SESV2Client.
Note that while SESV2Client has been working very well & exactly like the v1
client (only better - supporting 40 MB messages) for us for the last 8 months,
I don't know if there may be (edge) cases where it behaves differently and
breaks things for others.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
