4 ms·
I'd like to add, if using Elastic Beanstalk, don't directly attach an RDS instance when creating the environment. If you do, you won't be able to destroy your e
by elwell 11y ago
I'd like to add, if using Elastic Beanstalk, don't directly attach an RDS instance when creating the environment. If you do, you won't be able to destroy your environment without also deleting the RDS instance. Instead, create the RDS instance separately, and just add the proper security group for the environment to be able to access the host. Then you can easily create a new eb environment with any config changes (there are some config changes you can't make to an eb environment without creating a new one from scratch) and then connect to your existing db.
- gwintrob 11y agoIs there a site that collects these sorts of tips? Seems like there are a lot of potential pitfalls that can be hard to find in docs like: http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/java-rds.html http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/java-r...
- softdev12 11y agointeresting. i was under the impression you could just create a snapshot (before destroying the environment) and then restore as needed. am i missing something? Edit: http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_RestoreFromSnapshot.html http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_R...
- sdroy 11y agoIf you can take the database instance offline and if you do not need to access it from outside of the beanstalk app then that is fine.