Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

#595 migrate to sesv2 #1336

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Conversation

dominik-kovacs
Copy link
Contributor

@dominik-kovacs dominik-kovacs commented Jan 31, 2025

📢 Type of change

  • Bugfix
  • New feature
  • Enhancement
  • Refactoring

📜 Description

Migration of AWS SES from v1 to v2

💡 Motivation and Context

Amazon SES API v1 accepts messages up to 10MB in size including any images and attachments that are part of the message. SES API v2 accepts up to 40MB.

Issue #595

💚 How did you test it?

Unit tests
I don't have localstack pro, so no integration tests

📝 Checklist

  • I reviewed submitted code
  • I added tests to verify changes
  • I updated reference documentation to reflect the change
  • All tests passing
  • No breaking changes

🔮 Next steps

@github-actions github-actions bot added component: ses SES integration related issue type: documentation Documentation or Samples related issue labels Jan 31, 2025
@maciejwalkowiak
Copy link
Contributor

@dominik-kovacs thanks for a PR. To avoid breaking changes, we need to keep the current integration working. Perhaps it's makes sense to have a new module for v2? @MatejNedic any opinions?

@dominik-kovacs
Copy link
Contributor Author

The only breaking change I encountered was merging sourceArn and fromArn to a single parameter fromEmailAddressIdentityArn https://repost.aws/en/questions/QUjSyC3Az8TmeMc3_D5CcVfg#ANZRULQLHKTEmZj1WllxW6Rw

we could keep all 3 and deprecate sourceArn and fromArn

  • I'm not sure if this is a breaking change but ses v2 is only supported in localstack pro.

@MatejNedic
Copy link
Member

I would move it to a new module as well. If someone does not want to migrate sdk, it is better if you ask me.

This is major change lets wait few versions before deprecating old module.

How does this sound?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: ses SES integration related issue type: documentation Documentation or Samples related issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants