- What does rennokki/laravel-sns-events do?
- It is a Laravel-native package that receives incoming AWS SNS webhook messages at an HTTP endpoint and dispatches them as Laravel events. Subscription confirmations, notifications, and other SNS message types are routed to your own event listeners, so you avoid writing a custom webhook controller. It reduces boilerplate around SNS ingestion, signature verification, and subscription confirmation. It is an ingestion layer, not a full event bus or SNS publishing abstraction.
- How do I install laravel-sns-events?
- Install it with Composer using composer require rennokki/laravel-sns-events. You then publish and configure the package config, which controls the SNS endpoint route and topic settings. Finally, register your own listeners for the events the package dispatches. Confirm the package version matches your Laravel and PHP versions before installing.
- Which Laravel and PHP versions does 7.2.0 support?
- Version 7.2.0 adds Laravel 10.x and PHP 8.2 support while dropping Laravel 8.x and PHP 8.0. That makes it a breaking release for applications still on Laravel 8 or PHP 8.0. Because the release notes are sparse, verify the exact support matrix, including whether Laravel 9 remains supported, before rolling it out. Also validate PHP 8.2 compatibility across your full dependency tree, not just this package.
- Does it confirm the SNS subscription automatically?
- The package handles incoming SNS subscription confirmation messages and dispatches them so your application can react. Whether the confirmation is auto-confirmed or requires a manual action depends on the package version and configuration, so check the docs for your release. Test the confirmation flow against a real staging SNS topic before going to production. This is one of the key behaviors to validate during a canary rollout.
- How are SNS message signatures validated?
- Signature verification is part of the package's purpose: it validates incoming SNS messages so your endpoint does not process spoofed requests. You should still expose the endpoint only over HTTPS, as AWS SNS requires a publicly reachable HTTPS endpoint for subscriptions. Validate signature handling in staging with real SNS deliveries. Also test duplicate and replayed deliveries, since SNS can deliver the same message more than once.
- Can I use this package without live AWS SNS in tests?
- For local and CI testing you will typically fake or simulate the incoming SNS request payloads rather than connect to real AWS SNS. The package dispatches Laravel events, so you can test your own listeners in isolation using Laravel's event fakes. Confirm the exact testing approach against the package documentation for your version. A dedicated supported path for testing without live SNS is one of the questions to verify before adoption.
- Does it support multiple SNS topics or tenants?
- Multiple topic and tenant support, plus custom event mapping, is something to confirm against the package documentation for your version. The package routes SNS messages to Laravel events, so mapping logic may need configuration or custom listeners depending on your setup. Test multi-topic routing in staging before relying on it in production. If you need strict per-tenant isolation, verify behavior explicitly rather than assuming it.
- What queue and retry patterns should I use with SNS events?
- SNS delivery is at-least-once, so make your listeners idempotent and expect duplicates. Route heavy processing onto Laravel queues to avoid blocking the webhook endpoint and to protect against backpressure. Configure retries and a dead-letter queue for failed jobs, and add observability around dispatch and failures. These operational patterns matter more than the package itself for production reliability.
- What are the alternatives to laravel-sns-events?
- The main alternative is writing your own SNS webhook controller that validates signatures and dispatches events. This package mainly replaces that bespoke glue and centralizes validation and dispatch. A language-agnostic event gateway may fit better if you need non-Laravel consumers or a broader event bus. It is not a schema registry or an SNS publishing abstraction, so pair it with other tooling if you need those capabilities.
- Is laravel-sns-events well maintained and safe to adopt?
- Maintenance is relatively low-effort while you stay within the supported Laravel and PHP matrix, but package upgrades are coupled to Laravel and PHP upgrades. Release notes are sparse, so track the package's support policy and avoid drifting onto unsupported combinations. Treat 7.2.0 as breaking for Laravel 8 and PHP 8.0 environments. Support ownership should sit with the team that owns the Laravel service consuming SNS.