boto3.client('ses') vs boto3.client('sesv2')

[umarbutler]

Describe the issue

What is the difference between the two? Which one should we use? It is really unclear.

Links

Here an AWS engineer notes:

After digging into this - the only information I could find on the difference between the two was this blog post which is only a month old. The entire corpus of SES documentation has absolutely zero mention of the differences between the two that I could find. Their FAQ is equally void of such information.

[SamRemis]

Hi @umarbutler,

I've contacted the SES team, and they suggest that everyone should ideally use the SESv2 client as the SES client is no longer being updated with new features. Much of the core functionality is the same between the two clients, but SESv2 has an improved and more customer-friendly API. We have asked the SES team to add more information to their documentation to help customers choose the right client.

[umarbutler]

Hi @umarbutler,

I've contacted the SES team, and they suggest that everyone should ideally use the SESv2 client as the SES client is no longer being updated with new features. Much of the core functionality is the same between the two clients, but SESv2 has an improved and more customer-friendly API. We have asked the SES team to add more information to their documentation to help customers choose the right client.

Thanks, I think this definitely needs to be made known more widely.

There are 1.9k files on Github that use boto3.client('ses') (https://github.com/search?q=%22boto3.client%28%27ses%27%29%22&type=code) and just 51 that use boto3.client('sesv2') (https://github.com/search?q=%22boto3.client%28%27sesv2%27%29%22&type=code). 'ses' seems much more popular even today.

None of the boto3 documentation that I've seen advises the use of one over the other. I ended up using 'ses' simply because its more popular and I'd not have my 'sesv2' code break later on or become deprecated.

[RyanFitzSimmonsAK]

Converting this into a discussion as it is a guidance issue.