Hi everyone, I’m running an ECS cluster on Fargate, and I’m trying to find the best way to manage application configuration. My current setup: Sensitive config (e.g. secrets, tokens): stored in SSM Parameter Store Non-sensitive config (e.g. feature flags, settings): stored in S3 These values are read by the ECS task during startup. However: Problems I’m facing: I manage all infrastructure using Terraform, so each time I update a config value, a new parameter or S3 file update triggers unnecessary Terraform churn. Over time, this has made the infra codebase bloated, and terraform plan has started to slow down. Also, when I update a config (in S3 or Parameter Store), I need to manually restart the ECS service to pick up the new values. Questions: Is there a better way to store and update ECS app configuration without creating new secrets every time? How can I make config updates apply without needing to restart ECS services manually? Should I separate config from Terraform entirely? If so, what’s the best practice for this? Appreciate any insights or patterns that have worked well for you!