Weave Code
Aws Ses Bundle Laravel Package
idci/aws-ses-bundle
Symfony bundle that integrates Amazon SES so your application can send email through AWS. Provides service configuration, transport wiring, and a mailer-friendly setup for delivering messages via SES in Symfony projects.
A bundle that embed the php library php-aws-ses from daniel-zahariev into Symfony 2
Frequently asked questions about Aws Ses Bundle
- Can I install idci/aws-ses-bundle in a Laravel application?
- No. idci/aws-ses-bundle is a Symfony 2 bundle, not a Laravel package, and it depends on Symfony's Bundle, dependency injection, and configuration model. Those concepts do not map to Laravel service providers. For Laravel, use the native SES mail transport or a custom transport built on aws/aws-sdk-php.
- Does idci/aws-ses-bundle support Laravel 10 or Laravel 11?
- No. Symfony 2 and the underlying php-aws-ses library target the PHP 5.3 through 7.x era, while Laravel 10 and 11 require PHP 8.1 or newer. Composer dependency resolution will fail against a modern Laravel app, and a forced install would still risk runtime incompatibilities. Use Laravel's built-in SES mail driver instead.
- How do I install and configure idci/aws-ses-bundle in Symfony 2?
- It is installed through Composer and registered as a Symfony bundle, then configured through Symfony service and dependency injection configuration. The bundle wires SES credentials and sender defaults into the embedded php-aws-ses client. However, that client expects static access and secret keys and uses AWS Signature Version 2, so it is not suitable for modern SES deployments.
- Why does idci/aws-ses-bundle fail when sending email through Amazon SES?
- The wrapped php-aws-ses client uses AWS Signature Version 2, which AWS has been retiring and which is not supported in regions launched after January 2014. It also expects static access and secret keys rather than a modern credential chain. In practice it will fail in many current regions and with modern IAM or STS credential flows. Use aws/aws-sdk-php with SigV4 instead.
- What are alternatives to idci/aws-ses-bundle for sending SES email in Laravel?
- Use Laravel's native ses or ses-v2 mail transport configured through config/mail.php and config/services.php with aws/aws-sdk-php. That gives you SigV4 signing, the AWS credential chain, retries, and typed exceptions. If you truly need a custom raw SES payload, implement Illuminate\Mail\Transport\Transport and register it with Mail::extend().
- Is idci/aws-ses-bundle maintained and safe for production?
- There are strong abandonment signals: the repository shows 0 stars and 0 dependents, and the license is NOASSERTION, meaning the actual terms are unverified. Mail is a high-blast-radius surface with delivery, reputation, and compliance risk. Shipping unclear-licensed, unmaintained code into a production mail path is an audit finding waiting to happen. Treat this bundle as reference material only.
- What credentials does idci/aws-ses-bundle require for AWS SES?
- It expects static AWS access key and secret key values in configuration. It does not provide an instance profile, ECS task role, SSO, or credential refresh flow. That is a non-starter for most cloud-native deployments. Modern Laravel SES integrations should rely on the official AWS SDK credential chain instead.
- Can I port idci/aws-ses-bundle or php-aws-ses code to Laravel?
- You can port the intent, but not the Symfony wiring. The embedded php-aws-ses request-signing code is small and readable, but it uses Signature Version 2, so rewriting around the official AWS SDK is the better path. Port only configuration concepts such as region, credentials, and sender defaults into Laravel config and environment variables. If a custom raw API shape is required, implement a Laravel mail transport and register it with Mail::extend().
- How should I test an SES integration before replacing idci/aws-ses-bundle?
- Run a short spike in a non-production environment using aws/aws-sdk-php and Laravel's native SES transport. Add integration tests against the SES sandbox and verify sending, errors, and credential handling end to end. If you are migrating existing traffic, use shadow sends or a parallel run and compare delivery outcomes before decommissioning the bundle.
- Does idci/aws-ses-bundle use the official AWS SDK for PHP?
- No. It embeds daniel-zahariev/php-aws-ses, a small hand-rolled SES client that signs requests itself rather than using aws/aws-sdk-php. That means it lacks modern SDK features such as SigV4, credential refresh, retries, and typed exceptions. It also does not expose newer SES capabilities like templated sending, configuration sets, event publishing, SMTP credentials, or reputation metrics.
Weaver
How can I help you explore Laravel packages today?