Weave Code
Elasticache Bundle Laravel Package
igniter/elasticache-bundle
Laravel/Igniter bundle for integrating AWS ElastiCache, adding configuration and cache store support to connect applications to managed Redis or Memcached clusters for scalable, centralized caching.
A Laravel bundle that wires AWS ElastiCache into your application as a first-class cache and session backend. It provides ready-made drivers and configuration for both Redis and Memcached clusters, handling endpoint discovery, TLS connections, and sensible defaults so you can move from local caching to managed AWS infrastructure without rewriting service providers. Igniter CMS projects can enable it with minimal setup; standalone Laravel apps can register it manually.
- Preconfigured Redis and Memcached cache/session drivers
- Support for cluster mode and TLS-encrypted endpoints
- Environment-driven configuration for AWS credentials and regions
- Drop-in integration with Laravel's cache, session, and queue APIs
- Lightweight package with no runtime dependencies beyond Laravel
Frequently asked questions about Elasticache Bundle
- Is igniter/elasticache-bundle a Laravel package?
- No, it is a Symfony Bundle from 2015, with no service provider, facade, or config publishing. Laravel's container does not load Symfony bundles. Use Laravel's native config/cache.php and config/database.php redis settings instead.
- Can I install igniter/elasticache-bundle in Laravel 10 or 11?
- It will likely fail Composer resolution due to Symfony 2.x and PHP 5.x constraints conflicting with Laravel 10/11's Symfony 6/7 components. Forcing an install risks downgrading shared symfony/* dependencies. Even if installed, it is dead code at runtime. Adoption is not recommended.
- What is igniter/elasticache-bundle used for?
- It was a Symfony bundle that added AWS ElastiCache Redis or Memcached configuration and drivers. It targets Symfony's dependency injection and kernel lifecycle, not Laravel. Its purpose is already covered natively by Laravel's cache and Redis configuration.
- Does igniter/elasticache-bundle support Laravel's cache and session drivers?
- No. It has no illuminate/* contracts, no service provider, and no Laravel cache or session driver implementations. Laravel's built-in redis cache store and session driver handle ElastiCache endpoints through configuration. Do not expect this bundle to register Laravel drivers.
- How do I configure ElastiCache Redis in Laravel without this package?
- Set REDIS_HOST, REDIS_PASSWORD, REDIS_PORT, and REDIS_CLIENT in your .env file, then configure the redis block in config/database.php. Use predis or phpredis and enable TLS or cluster options as your ElastiCache setup requires. That is the maintained, first-class path and needs no extra package.
- Is igniter/elasticache-bundle maintained?
- No. The last release was 2015-10-14, with 3 stars and no dependents. There is no maintainer triage or security response. Unpatched code on PHP 8.1+ and Symfony 6/7 is a latent breakage risk, so avoid it for production.
- What are alternatives to igniter/elasticache-bundle for AWS ElastiCache in Laravel?
- Laravel's native Redis configuration with predis or phpredis is the primary alternative. The AWS SDK for PHP can help with ElastiCache cluster discovery or IAM authentication if needed. For cache and sessions, configure config/cache.php and config/session.php directly. No bridge package is required.
- Can igniter/elasticache-bundle handle ElastiCache cluster mode or IAM authentication?
- The evaluation notes it predates modern ElastiCache features and is unmaintained, so do not rely on it for cluster-mode slot discovery, reader endpoints, or IAM authentication. Laravel's Redis client options and the AWS SDK cover those cases. Test against your actual ElastiCache endpoint before committing to any approach.
- What are the production risks of using igniter/elasticache-bundle?
- The risks are high and asymmetric: abandoned since 2015, an unverified vendor namespace, and no security patching. You would own all transitive vulnerability patching indefinitely. Composer conflicts may force Symfony downgrades. Net functional gain over native Laravel configuration is essentially nil.
- Should I adopt igniter/elasticache-bundle for a new Laravel project?
- No. The technical evaluation verdict is do not adopt; integration effort is estimated at 3 to 5 engineer-days for glue with no reusable output. Use Laravel's native cache and database Redis configuration, which takes about 30 minutes. Revisit only if a concrete ElastiCache-aware requirement appears that native configuration cannot meet.
Weaver
How can I help you explore Laravel packages today?