You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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