How to Turn The Legacy Atlas On

Database Server

• Create a new MariaDB RDS instance from the image (ARN: arn:aws:rds:us-east-1:175502771271:snapshot:decommission-snapshot).
  • Must be at least a t2.medium, otherwise it ends up being slow.
  • Make sure to disable backing up when setting up the new db instance
    • If you don't do this, it will run a backup when first launched and slow down config
  • The name of the instance should be atlas-db-2014-newindexes-mariadb2 so that the hostname for the instance ends up being the value that the webserver expects.
  • The security group settings should be such that the web server instance should be to connect to it.
    • sg-9ef7fafb should work

Web Server

• Turn on the web server instance in EC2: i-078287acf3302aec3. It should be off but ready to go, and the software should load automatically on boot.
  • If it doesn't, you might have to check /var/log/django/debug.log or the nginx logs.
  • If the webserver hostname changed, you might have to go to /srv/atlas/django_files/observatory/settings_local.py and change the hostname there, then restart the python processes with sudo supervisorctl restart all.
• Once you're done, don't forget to terminate (not stop) the RDS instance because it'll restart again in 7 days otherwise. And stop the webserver too.

Note: legacyatlas.cid-labs.com will be broken, so use the IP given in the AWS console to reach the site