AWS Copilot launches v1.8 with improved support for load balanced web services and VPCs

Today, [AWS Copilot](/containers/copilot/) announced the release of version 1.8\. With this release, AWS Copilot now allows you to configure a friendly DNS name for your load balanced web services deployed with [Amazon Elastic Container Service (Amazon ECS)](/ecs/) Customers can now provide a friendly DNS name, such as _api.example.com,_ directly in the manifest file and Copilot will provision and manage the necessary infrastructure to associate the domain name with the application load balancer. With this release, you can also import [Amazon Virtual Private Cloud](/vpc/) (VPCs) with no public subnets into your Amazon ECS applications deployed with AWS Copilot . This allows you to run your applications in fully isolated environments with Copilot. Additionally, you can also select more than 2 public and private subnets while importing your VPC to AWS Copilot. AWS Copilot v1.8 also provides you greater visibility into your application health status and enables you to display recently stopped tasks and the target health status for load balanced web services in addition to container health checks with the ‘copilot svc status’ command. You can deploy applications to Amazon ECS with AWS Copilot in all AWS Fargate-supported regions. Additionally, you can deploy applications with AWS Copilot using AWS App Runner in the following AWS Regions: US East (N. Virginia), US East (Ohio), US West (Oregon), Europe (Ireland), and Asia Pacific (Tokyo). You can refer to the Copilot release notes for v1.8 [here](https://github.com/aws/copilot-cli/releases/tag/v1.8.0). To get started, download AWS Copilot on Mac, Linux, or Windows [here](https://aws.github.io/copilot-cli/docs/getting-started/install/).