An implementation of a session handler for storing sessions in AWS's DynamoDB, but with no dependencies on the AWS SDK, Guzzle etc
An implementation of a session handler for storing sessions in dynamoDB, but with no dependencies on the AWS SDK, Guzzle etc. As a bonus it's also faster!
The Idealstack AWS hosting platform uses this to provide transparent support for DynamoDB sessions, so users don't need to change anything in their code.
See our blog post about it for instructions on how to use it, setup the required tables etc
- Essentially a drop-in replacement for the official session handler in the AWS SDK
- Dependency-free - does not depend on any other composer packages. Only requires the core curl and json extensions be enabled in PHP
- Does not require an autoloader (although will work fine with one, eg composer)
- Supports most common AWS authentication methods (eg instance profiles, ECS task roles, .aws config files, environment variables)
- Compatible with all major PHP versions (even PHP 5.6, for all you luddites out there)
- Does not support locking (that's just because we don't need it, a PR is welcome or raise an issue if you need it)
Possibly you don't. The AWS SDK includes a session handler that is maintained by AWS and might be a better choice for most people.
Why do you want to store sessions in dynamodb? If you are running PHP in a clustered environment the default file-based session handler won't work.
You can store sessions in an SQL database, or Redis, but in many ways dynamodb is a better choice on AWS. It automatically scales to any number of reads/writes, can be distributed globally, has an elastic pricing model that is cheaper for small sites etc etc.
Here's a couple of reasons why you might want to use this code over the AWS SDK:
- If you aren't using the AWS SDK for other things, the session handler is going to include a large number of PHP classes on every page load that aren't needed. This potentially slows things down, uses more RAM, IO and Opcache etc
- It's faster. About 30% faster. We're talking about the difference between 30ms and 20ms here, so it's unlikely that sessions are the bottleneck slowing your app down. Still, faster is always good.
- If you choose to include this automatically using php's auto_prepend_file - you can get funny side-effects if you use the AWS SDK version. It requires an autoloader, which can mess with your project's own autoloading. Also it 'pollutes' the namespace. If your code uses a different version of the SDK from the one the sessions use, you should expect problems. This is the reason why we developed this for Idealstack as we make dynamodb sessions transparent to our users code.
composer require idealstack/dynamodb-sessions-dependency-free
or clone this repository
Configuration is the same as the AWS SDK version, so read their docs:
You configure the DynamoDB table the same as the AWS SDK docs recommend. However we'd suggest you also use the DynamoDB 'ttl' capability to garbage collect your sessions. Set that on the 'expires' field (this also works with the native SDK). See the notes in our blog post about how to setup the table.
use Idealstack\DynamoDbSessionHandlerDependencyFree; // or if you don't want to use composer auto-loader, try: // require(__DIR__ .'/vendor/idealstack/dynamodb-session-handler-dependency-free/src/DynamoDbSessionHandler.php'); (new Idealstack\DynamoDbSessionsDependencyFree\DynamoDbSessionHandler( [ 'table_name' => 'your-session-table-name', 'region' => 'local', 'endpoint' => 'http://localhost:8000', // Credentials. In production we recomend you use an instance role so you do not need to hardcode these. // At least make sure you don't hardcode them and commit them to github! 'credentials' => [ 'key' => 'AAAAAAAAAAAAAAAAAAAAAA', 'secret' => 'BBBBBBBBBBBBBBBBBBBBBBBBBBBBBB' ], // These are all defaults. // // Base64 encode data when reading and writing. Avoids problems with binary data, Note this is // // not the behaviour of the AWS SDK, so set to false if you require compatibility with existing // // sessions created with the SDK // 'base64' => true, // 'hash_key' => 'id', // // // The lifetime of an inactive session before it should be garbage collected. If it isn't provided, // // the actual lifetime value that will be used is ini_get('session.gc_maxlifetime'). // 'session_lifetime' => 86400, // 24 hours // 'consistent_reads' => true, //You almost certainly want this to be true // 'session_locking' => false, //True is not supported ] ))->register();