Skip to end of banner
Go to start of banner

copyRestore Bridge Infrastructure

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

versioncomment
2021/08/23Reviewed. Added this table.
2017/10/27Created

This documents how you might restore the infrastructure for the AWS Bridge account and apps.  Most of the Bridge infra (but not all) has been automated with AWS cloudformation templates located in a few different repos.  This doc attempts to guide you thru the steps needed to recover the AWS environment to support the bridge server.

Step-by-step guide

Bridge-infra Repo

  1. Manually setup resources: Hosted Zones (*.sagebridge.org) and SSL Certs (requires manual approval). 
  2. Clone Sage-Bionetworks/Bridge-infra repo
  3. git-crypt unlock the repo. The key to unlock is in Lastpass
  4. Run cloudformation and create a bootstrap stack with cf_template/boostrap.yml 
  5. Modify the env_vars and env_vars.secret files to match your environment.
  6. Source the env vars (i.e. `source env_vars && source env_vars.secret`)
  7. Change update_cf_stack.sh to 'create-stack' instead of 'update-stack'
  8. Execute ./update_cf_stack.sh


BridgePF Repo

  1. Clone Sage-Bionetworks/BridgePF repo
  2. View the wiki and do the bootstrapping steps required for the app to run (create DynamoDB tables, RDS, buckets, etc..).
  3. Build the app (i.e. sbt clean dist).  The built binary is in target/universal/bridgepf-0.1-SNAPSHOT.zip

BridgePF-infra Repo

  1. Clone Sage-Bionetworks/Bridge-infra repo
  2. git-crypt unlock the repo. The key to unlock is in Lastpass
  3. Modify the env_vars and env_vars.secret files to match your environment.
  4. Source the env vars (i.e. `source env_vars && source env_vars.secret`)
  5. Change update_cf_stack.sh to 'create-stack' instead of 'update-stack'
  6. Execute ./update_cf_stack.sh
  7. The EB environment will be in an Error state because the app has not been deployed yet.
  8. Repeat steps #3-4, This time update the autoscaling and elasticache vars.
  9. Execute ./update_cf_stack.sh to setup the new vars in EB.
  10. Deploy the bridge app (from build in BridgePF repo) using either AWS console or CLI.
  11. Check cloudwatch logs if EB fails to deploy the app.



  • No labels