Name: BridgePF-infra
Owner: Sage Bionetworks
Description: Infrastructure for BridgePF
Created: 2017-07-10 20:43:01.0
Updated: 2017-09-05 21:04:52.0
Pushed: 2018-01-17 22:40:51.0
Homepage: null
Size: 205
Language: Shell
GitHub Committers
User | Most Recent Commit | # Commits |
---|
Other Committers
User | Most Recent Commit | # Commits |
---|
Install and configure the AWS Infrastructure for the BridgePF application.
--profile aws-admin --region us-east-1 cloudformation create-stack \
stack-name foo-develop \
capabilities CAPABILITY_NAMED_IAM \
template-body cf_templates/eb_bridgepf.yml \
parameters \
rameterKey=AppDeployBucket,ParameterValue=org-sagebridge-bridgepf-deployment-foo-develop \
rameterKey=AwsDefaultVpcId,ParameterValue=vpc-1d69caf3 \
rameterKey=EC2InstanceType,ParameterValue=t2.micro \
[Rest of the parameters from update_cf_stack.sh]
The above should create the infrastructure required for BridgePF, it does not actually deploy the app it only installs and configures the required AWS infrastructure for it. The AWS appilcation health check is enabled therefore the EB environment will start in an error state since the app has not been deployed. The environment status should turn green once the is successfully deployed.
Check for additional bootstrapping steps in BridgePF repo[1]
Once the infrastructure for BridgePF app has been setup you can deploy the app file to the stack. This can be done by using either the AWS console[2] or using the AWS CLI[3][4].
[1] https://github.com/Sage-Bionetworks/BridgePF/wiki
[2] https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.deploy-existing-version.html
[3] https://docs.aws.amazon.com/cli/latest/reference/elasticbeanstalk/create-application-version.html
[4] https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/eb3-deploy.html
[5] https://github.com/AGWA/git-crypt
[6] https://help.github.com/articles/generating-a-new-gpg-key