AWS | resources
Hoop could be configured to use the aws command line to manage resources in multiple accounts
Connection Configuration
Name | Type | Description |
AWS_ACCESS_KEY_ID | env-var | The access key credential |
AWS_SECRET_ACCESS_KEY | env-var | The secret key credential |
AWS_REGION | env-var | The AWS region |
Use an IAM credential with reduced scope to only create secrets and/or listing ecs services
Connection Command
- secretsmanager
shellhoop admin create conn secretsmanager -a <agent> \ -e AWS_ACCESS_KEY_ID=<key-id> \ -e AWS_SECRET_ACCESS_KEY=<key> \ -e AWS_REGION=us-east-1 \ -- aws secretsmanager create-secret
- list-services-prod
shellhoop admin create conn list-services-prod -a <agent> \ -e AWS_ACCESS_KEY_ID=<key-id> \ -e AWS_SECRET_ACCESS_KEY=<key> \ -e AWS_REGION=us-east-1 \ -- aws ecs list-services --cluster prod
How to Use
Now it’s possible to create credentials on AWS Secrets Manager service
shellhoop exec secretsmanager -- \ --name MyTestSecret --description "My test secret created with the CLI." \ --secret-string "{\"user\":\"diegor\",\"password\":\"EXAMPLE-PASSWORD\"}"
Or listing ECS Services from cluster
prod
shellhoop exec list-services-prod