You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of now, the user is expected to generate and add passwords to the environment of their CI/CD pipeline.
It would be better to have AWS SSM SecretManager with CloudFormation, as showed here
Acceptance Criteria
the value of parameter GrafanaDatabasePassword in cloudformation/10-aurora-backend.yml must be generated and managed by SSM SecretManager
the value of parameter GrafanaServiceAdminPassword in cloudformation/20-grafana-ecs-service.yml must be generated and managed by SSM SecretManager
the value of parameter GrafanaDatabasePassword in cloudformation/20-grafana-ecs-service.yml must be resolved via SSM SecretManager
DO NOT CHANGE USER NAME FOR THE DATABASE please
The text was updated successfully, but these errors were encountered:
Have SSM generate and inject passwords
As of now, the user is expected to generate and add passwords to the environment of their CI/CD pipeline.
It would be better to have AWS SSM SecretManager with CloudFormation, as showed here
Acceptance Criteria
GrafanaDatabasePassword
incloudformation/10-aurora-backend.yml
must be generated and managed by SSM SecretManagerGrafanaServiceAdminPassword
incloudformation/20-grafana-ecs-service.yml
must be generated and managed by SSM SecretManagerGrafanaDatabasePassword
incloudformation/20-grafana-ecs-service.yml
must be resolved via SSM SecretManagerThe text was updated successfully, but these errors were encountered: