⚡️ Features and Enhancements
-
Support user-written environment addons
You can now deploy addons associated with your environments. Addons are additional AWS resources that are not integrated in Copilot by default - for example, DynamoDB, RDS, etc. Environment addons resources have their lifecycle managed at the environment level. Hence, resources can be shared across services or jobs and won't be deleted unless the environment is deleted.
If you are already familiar with workload addons, then good news - the experience of managing environment addons is pretty similar.
You just need to store your CFN templates under
copilot/environments/addons
folder, and then runcopilot env deploy
- your addons will the be deployed along with the environment.For an example walk-through, see our blog post !
-
Support static content delivery through an existing S3 bucket
You can now bring your own S3 bucket to work with CloudFront for faster static content delivery.
You can use CloudFront with an S3 bucket as the origin by configuring the environment manifest as below:cdn: static_assets: location: cf-s3-ecs-demo-bucket.s3.us-west-2.amazonaws.com alias: example.com path: static/*
Read the blog post for more!
🐛 Bug Fixes
- Render CFN template with
SslPolicy
instead ofSSLPolicy
(#4278)