Observed behavior

ELB OTP deployments are not set up correctly to handle deploying new EC2 machines (or writing to S3 buckets) in external AWS accounts. In other words, if Data Tools is running on AWS account # 12345 and needs to spin up servers in account # 67890, it cannot do so at the moment.

Expected behavior

We need a way to handle the delegation of access via an AWS role defined in the third party account: https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_cross-account-with-roles.html

Steps to reproduce the problem

N/A

Any special notes on configuration used

N/A (ELB Deployments must be enabled)

Version of datatools-server and datatools-ui if applicable (exact commit hash or branch name)

N/A