Visual Asset Management System (VAMS) is a purpose-built, AWS native solution for the management and distribution of specialized visual assets used in spatial computing.
Apache License 2.0
83
stars
28
forks
source link
First time setup instructions don't work out of the box when using AWS CLI profiles #39
I had setup a organization account for setting up VAMS, and thus my default ~/.aws/credentials and ~/.aws/config values didn't work for the organization account. Thus, I created a IAM user under the organization account with AdministratorAccess (I think it would be wiser to define the permission boundary schema in the repository so that users could use that for this step) and created a new CLI profile in the aforementioned CLI config paths.
However, the step for cdk bootstrap only succeeded after giving the --profile option with the proper profile name. Similarly, the final step for deploying does not take CLI profiles into account, and I had to copy the actual command from infra/packages.json in order to get the deploy going.
Perhaps the Build & Deploy Steps could be checked over with a fresh environment to make sure it works? Additionally the final step for npm run deploy.dev could pass the --profile option to the cdk command.
I had setup a organization account for setting up VAMS, and thus my default
~/.aws/credentials
and~/.aws/config
values didn't work for the organization account. Thus, I created a IAM user under the organization account with AdministratorAccess (I think it would be wiser to define the permission boundary schema in the repository so that users could use that for this step) and created a new CLI profile in the aforementioned CLI config paths.However, the step for
cdk bootstrap
only succeeded after giving the--profile
option with the proper profile name. Similarly, the final step for deploying does not take CLI profiles into account, and I had to copy the actual command frominfra/packages.json
in order to get the deploy going.Perhaps the Build & Deploy Steps could be checked over with a fresh environment to make sure it works? Additionally the final step for
npm run deploy.dev
could pass the --profile option to thecdk
command.