-
Notifications
You must be signed in to change notification settings - Fork 427
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: Update README.md #5975
chore: Update README.md #5975
Conversation
🍕 Here are the new binary sizes!
|
@build-with-aws-copilot would be nice to know if aws is or is not going to retire this codebase |
@bkaws Can you provide an update as to the status of this project? Should people be migrating off of Copilot? |
It does look like AWS has stopped adding new features to Copilot. Discussion (I published a few guides on how to use AWS Copilot based on my passion. But I'm not affiliated with AWS in any way.) |
Has anyone found a suitable replacement to Copilot? |
@afgallo I am actively working to replace it using terraform. Its way harder timewise but its somewhat of a standard. A solution for creating terraform from copilot:
You can also package pipelines to keep everything the same for each environment, as well but I am just creating the one terraform environment an using variables to segment environments and other features / config Instead we are using github actions to build images and deploy the terraform |
@SoundsSerious terraform is a solid choice. I've been considering something different, leveraging our existing CloudFormation templates and migrate infra related components (i.e mostly copilot environment stuff) to Spectre and use good old EC2 instances with Kamal. |
I have not used it but another alternative to look into would be sst which supports ECS Fargate using their cluster component https://sst.dev/docs/component/aws/cluster |
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the Apache 2.0 License.