From 63736633444e4242d29f9f3cf74a0f8225e1e253 Mon Sep 17 00:00:00 2001 From: Daniel Hensby Date: Mon, 23 Nov 2015 11:21:40 +0000 Subject: [PATCH] DOCS Renaming incorrect constant --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 6aee2e9..f1e2812 100644 --- a/README.md +++ b/README.md @@ -14,28 +14,28 @@ If you wish to store sessions in DynamoDB, set the following environment variabl // the name of the DynamoDB table to store sessions in define('AWS_DYNAMODB_SESSION_TABLE', 'mysession'); - + // the region that the DynamoDB table will live in (in this example here it uses Sydney) define('AWS_REGION_NAME', 'ap-southeast-2'); - + Once these are in place, this module will configure DynamoDB and register that as the session handler. You will **need** to create the specified table using the AWS DynamoDB console for the region. ## Using DynamoDB outside of AWS Sometimes you'll want to test that DynamoDB sessions work on your local development environment. You can make that -happen by defining `AWS_ACCESS_KEY` and `AWS_ACCESS_SECRET`. Please don't define these constants in the environment file +happen by defining `AWS_ACCESS_KEY` and `AWS_SECRET_KEY`. Please don't define these constants in the environment file in EC2 instances, as credentials are automatically handled by the IAM role inside of AWS. // the AWS access key and secret. This is optional if you've configured an instance with an IAM role // http://docs.aws.amazon.com/aws-sdk-php/guide/latest/credentials.html#caching-iam-role-credentials define('AWS_ACCESS_KEY', ''); - define('AWS_ACCESS_SECRET', ''); + define('AWS_SECRET_KEY', ''); ## Garbage collecting sessions Inactive sessions are garbage collected by `GarbageCollectSessionCronTask` if [silverstripe-crontask](https://github.com/silverstripe-labs/silverstripe-crontask) -is setup on your instance. The time when a session should be collected after inactivity can be changed by setting +is setup on your instance. The time when a session should be collected after inactivity can be changed by setting `Session::$timeout`. For example, in your application's config YAML file, this sets a 20 minute session timeout: