4

I have successfully deployed a Flask application to AWS Elastic Beanstalk. The application uses an SQLAlchemy database, and I am using Flask-Security to handle login/registration, etc. I am using Flask-Migrate to handle database migrations.

The problem here is that whenever I use git aws.push it will push my local database to AWS and overwrite the live one. I guess what I'd like to do is only ever "pull" the live one from AWS EB, and only push in rare circumstances.

Will I be able to access the SQLAlchemy database which I have pushed to AWS? Or, is this not possible? Perhaps there is some combination of .gitignore and .elasticbeanstalk settings which could work?

I am using SQLite.

b_g
  • 299
  • 1
  • 4
  • 14

2 Answers2

10

Yes, your database needs to not be in version control, it should live on persistent storage (most likely the Elastic Block Storage service (EBS)), and you should handle schema changes (migrations) using something like Flask-Migrate.

The AWS help article on EBS should get you started, but at a high level, what you are going to do is:

  • Create an EBS volume
  • Attach the volume to a running instance
  • Mount the volume on the instance
  • Expose the volume to other instances using a Network File System (NFS)
  • Ensure that when new EBS instances launch, they mount the NFS

Alternatively, you can:

  • Wait until Elastic File System (EFS) is out of preview (or request access) and mount all of your EB-started instances on the EFS once EB supports EFS.
  • Switch to the Relational Database Service (RDS) (or run your own database server on EC2) and run an instance of (PostgreSQL|MySQL|Whatever you choose) locally for testing.
Sean Vieira
  • 155,703
  • 32
  • 311
  • 293
  • No upvotes? This answer is a lot more informative than the other one and it should come first! – Manuel Jun 23 '15 at 19:18
2

The key is hosting your database outside of your Elastic Beanstalk environment. If not, as the load increases different instances of your Flask app will be writing to their own local DB. There won't a "master" database that will contain all the commits.

The easiest solution is using the AWS Relational Database Service (RDS) to host your DB as an outside service. A good tutorial that walks through this exact scenario:

Deploying a Flask Application on AWS using Elastic Beanstalk and RDS

SQLAlchemy/Flask/AWS is definitely not a waste of time! Good luck.

manychairs
  • 149
  • 3
  • Please describe here a little of the content of the tutorial – abarisone Apr 16 '15 at 11:52
  • The tutorial is an step-by-step example of how to deploy a simple Flask app with a database on AWS. It assumes no prior familiarity with AWS, and the Flask code is provided via GitHub. The original poster would be helped by steps 3 and 4 from the tutorial, which show how to set up a SQL database in AWS and tie it into your Flask application. – manychairs Apr 16 '15 at 14:58