Description
Currently, environment variables are manually configured in AWS Systems Manager Parameter Store. This introduces additional operational overhead, increases the risk of misconfiguration, and makes deployments less reproducible across environments (e.g., dev, staging, production). It also creates a gap between infrastructure defined in code and the actual runtime configuration, which can lead to inconsistencies and harder onboarding for new team members.
Describe the solution you'd like
Define all required environment variables directly within the CDK stack. This ensures that parameters are automatically created, updated, and versioned as part of the deployment process. By managing them as infrastructure-as-code, we improve consistency, reduce manual steps, and make deployments more predictable and repeatable across environments.
Describe alternatives you've considered
No response
Additional context
No response
Validations
Description
Currently, environment variables are manually configured in AWS Systems Manager Parameter Store. This introduces additional operational overhead, increases the risk of misconfiguration, and makes deployments less reproducible across environments (e.g., dev, staging, production). It also creates a gap between infrastructure defined in code and the actual runtime configuration, which can lead to inconsistencies and harder onboarding for new team members.
Describe the solution you'd like
Define all required environment variables directly within the CDK stack. This ensures that parameters are automatically created, updated, and versioned as part of the deployment process. By managing them as infrastructure-as-code, we improve consistency, reduce manual steps, and make deployments more predictable and repeatable across environments.
Describe alternatives you've considered
No response
Additional context
No response
Validations