Skip to content

Write up ECS Preparation Checklist for the java services #2614

@terrywbrady

Description

@terrywbrady

Guidance on when to use SSM

  • A setting is so volatile that you intended to dynamically reload the value while your service is running
  • For credentials

Mechanism for passing SSM

  • Under EC2, we resolved SSM values after parsing a yaml file
  • Under ECS, we should explore container definition secrets (decided we will not pursue this)

Guidance on when to use values

  • Value is very unlikely to change
  • Value is appropriate to include in a public repository
  • A code change is likely to occur when the value needs to change

Guidance on when to use ENV

  • Under ECS, most config will be defined with ENV
  • The ENV settings will be captured in the mrt-sceptre repo, so the values will be saved in a private location

Recommended yaml updates

  • Share the same config for ecs-stg, ecs-prd and ideally ecs-dev
  • Continue to have special config for docker compose and ecs-ephemeral

Special consideration - cloud node table

  • Cloud note yaml table should be read from a config S3 repo rather than from the classpath

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions