Skip to content
This repository was archived by the owner on Feb 7, 2018. It is now read-only.
This repository was archived by the owner on Feb 7, 2018. It is now read-only.

Is sharing a dynamodb session table across many otherwise-isolated apps a security issue? #47

Description

@trauts2

We're considering giving separate deployments their own table within dynamodb to avoid customers in app 1 accidentally (or intentionally) gaining access to session data from another app that happens to use the same sessionid. Before we do, is this a realistic concern? Is it impossible or just unlikely?

Second, if we have to go this route, we'd like to keep the Beanstalk images the same. To override it dynamically I can see how the config.xml could be modified by a beanstalk .ebextensions file. But that feels really ugly. Is there a better way to tell a particular beanstalk environment to use a unique dynamodb table name?

Sorry, may not really an issue. Hope that's ok

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions