datatools-server
datatools-server copied to clipboard
Refactor ec2 startup script (potentially into a new project into a scripting language)
Observed behavior
When deploying to an ELB instance, at least the 2 following items could be improved:
- The download of all assets for the bundle occurs on the datatools-server instance and then needs to be uploaded to s3 and then downloaded again to the graph-building instance.
- There isn't great error reporting in the user data startup script. IE, if something fails, the failure reason can't be immediately be derived.
Expected behavior
- The graph-building instance could create the bundle instead to decrease the amount of time it takes to wait for the bundle to be uploaded and then downloaded.
- It may be best to have a separate project that has a startup script that can be downloaded onto the ec2 instance and then perform all of the startup tasks.
Steps to reproduce the problem
n/a
Any special notes on configuration used
A datatools-server with ec2 deployments enabled.
Version of datatools-server and datatools-ui if applicable (exact commit hash or branch name)
f49d482dc5feaf3fb82da94fb6cfbdccf1ebeefc