The root360 platform does provide a default set of environment variables already, e.g. details about other components (databases, cache layers, filesystems and so on) or the current environment (test, stage, prod, ….). Using those environment variables via install.sh you can configure your application with the appropriate endpoints of the environment.

You can enhance or extend this list of variables by adding new items yourself using the CLI-Suite (root360). The content will be added to an encrypted vault inside AWS SecretsManager.

To verify the values on the targets you’re setting the secrets for, you can run sudo get-application-env (see here) on these roles.

Preconditions

• You need access to jumphost with you personal Openssh access key. (Archived) How to access an environment via OpenSSH

• Secret value size must not exceed 64K (per secret)

List Secrets

As the secrets scope is per role, you must provide a role parameter.

~$ r3 secret list --role example
+-------------+-----------------------------------------------+
|   Secret    |                     Value                     |
+-------------+-----------------------------------------------+
| EXAMPLE_VAR | these-are-not-the-secrets-you-are-looking-for |
+-------------+-----------------------------------------------+

Add/Update secrets

Secrets must be added/updated for a specific role.

~$ r3 secret update --role example --name MYVAR --value "may-the-cloud-be-with-you"
2020-11-17 10:42:40 r3-11364 SUCCESS  Secret "MYVAR" successfully updated.
+-------------+-----------------------------------------------+
|   Secret    |                     Value                     |
+-------------+-----------------------------------------------+
| EXAMPLE_VAR | these-are-not-the-secrets-you-are-looking-for |
| MYVAR       | may-the-cloud-be-with-you                     |
+-------------+-----------------------------------------------+

Delete secrets

Secrets must be deleted for a specific role.

~$ r3 secret delete --role example --name MYVAR
2020-11-17 10:44:18 r3-11387 SUCCESS  Secret "MYVAR" successfully deleted.
+-------------+-----------------------------------------------+
|   Secret    |                     Value                     |
+-------------+-----------------------------------------------+
| EXAMPLE_VAR | these-are-not-the-secrets-you-are-looking-for |
+-------------+-----------------------------------------------+

Related tutorials

• Page:
  Container Routing based on Traefik
• Page:
  ECS container loops
• Page:
  Script Snippets
• Page:
  Usage and configuration of supervisord
• Page:
  Usage and configuration of PM2
• Page:
  Quickstart
• Page:
  Using deployment hooks
• Page:
  Using install.sh during deployments
• Page:
  Deployment via CLI-suite
• Page:
  Custom environment variables for your deployment/application using secrets
• Page:
  Composer Deployment for the Cloud
• Page:
  Usage of Amazon ECR-based container image registry
• Page:
  Usage of CLI-suite for container
• Page:
  Backup coverage and data retention

Related components

• Page:
  Build Server (root360)
• Page:
  CI/CD (root360)
• Page:
  App Server Single (root360)
• Page:
  App Server Auto Scaling (root360)
• Page:
  Code Deploy (root360)
• Page:
  CLI-Suite (root360)