AWS Copilot v1.28: Static Site service type is here!
Posted On: May 24, 2023
The AWS Copilot core team is announcing the Copilot v1.28 release. Special thanks to @interu, @0xO0O0, @andreas-bergstrom who contributed to this release. Our public сommunity сhat is growing and has over 400 people online and over 2.9k stars on GitHub. Thanks to every one of you who shows love and support for AWS Copilot.
Copilot v1.28 brings several new features and improvements:
- Static Site service type: You can now deploy and host static websites with AWS S3. See detailed section.
- Container Images Parallel Build: You can now build main container and sidecar container images in parallel. With parallel build, you can reduce the overall time it takes build and push container images to AWS ECR.
What’s AWS Copilot?
The AWS Copilot CLI is a tool for developers to build, release, and operate production ready containerized applications on AWS. From getting started, pushing to staging, and releasing to production, Copilot can help manage the entire lifecycle of your application development. At the foundation of Copilot is AWS CloudFormation, which enables you to provision infrastructure as code. Copilot provides pre-defined CloudFormation templates and user-friendly workflows for different types of micro service architectures, enabling you to focus on developing your application, instead of writing deployment scripts.
See the section Overview for a more detailed introduction to AWS Copilot.
Static Site service type
Copilot's newest workload type, Static Site, provisions and configures everything you need to create a static website hosted by Amazon S3 and fronted by an Amazon CloudFront distribution.
Let's say you want to launch a straightforward, read-only website. You don't need a backend or a database, you don't need to personalize the site based on the user or store any information. Make a static site! This workload type is relatively simple and quick to launch, and is highly performant.
Static Site Upload Experience
copilot init command, or
copilot svc init if you've already run
copilot app init and
copilot env init. You may use the
--sources flag to pass in the path(s) (relative to your project root) to your static asset directories and/or files. Alternatively, you may select the directories/files when prompted.
A manifest will be populated and stored in the
copilot/[service name] folder. There, you may adjust your asset specifications if you'd like. By default, all directories will be uploaded recursively. If that's not what you want, leverage the
reinclude fields to add filters. The available pattern symbols:
*: Matches everything
?: Matches any single character
[sequence]: Matches any character in sequence
[!sequence]: Matches any character not in sequence
# The manifest for the "example" service.
# Read the full specification for the "Static Site" type at:
# Your service name will be used in naming your resources like S3 buckets, etc.
type: Static Site
- source: src/someDirectory
- source: someFile.html
# You can override any of the values defined above by environment.
# - source: './blob'
# recursive: true
# destination: 'assets'
# exclude: '*'
# - '*.txt'
# - '*.png'
reinclude filters, go here.
copilot deploy or
copilot svc deploy command will provision and launch your static website: creating an S3 bucket and uploading your chosen local files to that bucket, and generating a CloudFront distribution with the S3 bucket as the origin. Under the hood, your Static Site service will have a CloudFormation stack, just like other Copilot workloads.
Server access logging for the Static Site S3 bucket is not enabled by default, because object uploading is managed by Copilot.