Skip to content

Conversation

@Skullbock
Copy link

Amazon AWS SES Driver.

Notes

I've tried as much as possible to detail the needs in the readme since aws (as usual) is pretty complicated in the setup of the workflow. Here are some gotchas:

  • Automated the whole process as much as possible, from creating a configuration set, to the sns topic, to the validation of the webhook
  • You basically need to add some extra configuration keys to the services.ses configuration key and have a user that, besides being able to send emails with ses (as per core laravel config) can also create sns topics
  • Some extra optional dependencies are requires (same as the laravel ses driver basically)

Tested on a dev project and seems to work. I have some troubles running the tests, for some reason testbench doesn't seem to pickup the testing database...

@Baspa Baspa requested a review from markvaneijk April 17, 2025 13:03
@drahosistvan
Copy link

I’m very interested in the AWS SES provider support. I’ll be testing your code in a side project soon and will share my feedback on this PR.

@Skullbock
Copy link
Author

Thanks! Let me know for any changes or feedback

@markvaneijk
Copy link
Contributor

Hi @Skullbock, thanks for your PR. I will look into this and craft this a little bit further.

Happy to receive also your feedback @drahosistvan.

@Skullbock
Copy link
Author

Thanks, let me know if i can help

@lloricode
Copy link

+1

@Skullbock
Copy link
Author

Hi! Is there any way i can help speed this up? :)

@markvaneijk
Copy link
Contributor

We're making this a priority and will add this PR after some changes this month!

@MACscr
Copy link

MACscr commented Oct 22, 2025

Great! We really need this asap too.

@MACscr
Copy link

MACscr commented Oct 22, 2025

@markvaneijk If you need me to, I can probably fork this PR and work on it and resubmit it after its completed and tests are passing. Maybe I can work on it while you work on getting github working with PR testing? Seems like its failing with everything right now and obviously we want all PR's to be passing tests before merged, etc.

@markvaneijk
Copy link
Contributor

That would be awesome @MACscr

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants