AWS Copilot launches v1.4 with support for ECS exec and more

Today, [AWS Copilot](/containers/copilot/) launched version 1.4 which now provides more operational capabilities for applications hosted on [Amazon Elastic Container Service](/ecs/) (Amazon ECS). This allows you to directly access a container to troubleshoot and run commands with ECS exec. AWS Copilot also added the ability to deploy applications from a Bitbucket repository and attach [Amazon Elastic File Service](/efs/) (EFS) volumes. You can now access your containers directly from your command-line shell using AWS Copilot’s exec command powered by the [ECS exec](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-exec.html) feature. This lets you safely debug your applications while they’re running in the cloud. AWS Copilot also supports adding a deployment pipeline to safely deploy resources from Bitbucket repositories, in addition to the existing GitHub and [AWS CodeCommit](/codecommit/) options. You may also quickly connect your application to an existing EFS file system using the new 'storage' field in your application's AWS Copilot manifest. To get started, see the following resources: * Refer to the AWS Copilot release notes for v1.4 [here](https://github.com/aws/copilot-cli/releases/tag/v1.4.0). * Read the documentation for AWS Copilot exec for [services](https://aws.github.io/copilot-cli/docs/commands/svc-exec) and [tasks](https://aws.github.io/copilot-cli/docs/commands/task-exec). * See the blog post of using ECS Exec with AWS Copilot [here](https://aws.amazon.com/blogs/containers/connecting-to-an-interactive-shell-on-your-containers-running-in-aws-fargate-using-aws-copilot). * AWS Copilot can deploy applications to AWS Fargate supported regions and is available for download on Mac and Linux [here](https://github.com/aws/copilot-cli/wiki/Installation).