AWS End User Messaging SMS plugin for Mautic 7: native SMS transport with IAM and consent controls

3rd Party Addons
1

Hi Mautic community,

I am sharing an open-source plugin that adds AWS End User Messaging SMS as a native SMS transport for Mautic 7.

GitHub:

Installation guide:

Current features:

  • Native SMS transport inside Mautic.
  • Uses the IAM role attached to the Mautic server.
  • AWS access keys are not stored in Mautic.
  • Canary mode for testing with one approved phone number.
  • Production mode restricted to approved audiences.
  • SMS consent validation.
  • Approved Mautic segment validation.
  • E.164 phone number normalization.
  • Configurable daily and per-minute delivery limits.
  • Message length and emoji safeguards.
  • Works with Mautic’s native SMS workflow without requiring n8n.

Requirements:

  • Mautic 7.x.
  • PHP 8.2 or newer.
  • AWS End User Messaging SMS.
  • An approved AWS origination identity.
  • An IAM role with the required SMS permissions.

The current release focuses on text SMS. MMS, RCS, inbound replies, and delivery-event webhooks are not included yet.

I am looking for feedback from Mautic users and developers, especially around compatibility, installation, delivery monitoring, and additional safeguards.

Issues and support:

Please do not include credentials, AWS account IDs, ARNs, phone numbers, or contact records in issue reports.

2

Thank you very much! That is great - didn’t even remember, AWS provides SMS too.
Does it have an own editor included or makes use of the mautic editor?

Is AWS also providing RCS (successor of SMS)?

3

Thanks, Dirk. The plugin does not include a separate message editor. It registers AWS End User Messaging as a native Mautic SMS transport, so messages are created and edited through Mautic’s normal SMS area and can be used in segments and campaigns.

AWS now also supports RCS, including rich and interactive messages. However, this plugin currently focuses on text SMS only. RCS, MMS, inbound replies, and delivery-event webhooks are outside the current scope. Adding RCS would require support for RCS agents, rich message payloads, fallback handling, and delivery events.