copilot version: 1.21.0 and 1.21.1
AWS Region: cn-northwest-1
Demo APP:
https://docs.aws.amazon.com/zh_cn/AmazonECS/latest/developerguide/getting-started-aws-copilot-cli.html
Process and Error：
$ git clone https://github.com/aws-samples/amazon-ecs-cli-sample-app.git demo-app
$ cd demo-app/
$ ls
CODE_OF_CONDUCT.md CONTRIBUTING.md Dockerfile index.html LICENSE README.md
$ copilot init
Welcome to the Copilot CLI! We're going to walk you through some questions
to help you get set up with a containerized application on AWS. An application is a collection of
containerized services that operate together.
Workload type: Load Balanced Web Service
Service name: demo
Dockerfile: ./Dockerfile
parse EXPOSE: no EXPOSE statements in Dockerfile ./Dockerfile
Port: 80
Ok great, we'll set up a Load Balanced Web Service named demo in application test listening on port 80.
✔ Proposing infrastructure changes for stack test-infrastructure-roles
- Creating the infrastructure for stack test-infrastructure-roles [create complete] [31.0s]
- A StackSet admin role assumed by CloudFormation to manage regional stacks [create complete] [9.9s]
- An IAM role assumed by the admin role to create ECR repositories, KMS keys, and S3 buckets [create complete] [12.5s]
✔ The directory copilot will hold service manifests for application test.
✔ Wrote the manifest for service demo at ../copilot/demo/manifest.yml
Your manifest contains configurations like your container size and port (:80).
✔ Created ECR repositories for service demo.
All right, you're all set for local development.
Deploy: Yes
✔ Manifest file for environment test already exists at ../copilot/environments/test/manifest.yml, skipping writing it.
✔ Linked account 456370280007 and region cn-northwest-1 to application test.
✔ Proposing infrastructure changes for the test-test environment.
- Creating the infrastructure for the test-test environment. [create complete] [32.5s]
- An IAM Role for AWS CloudFormation to manage resources [create complete] [11.9s]
- An IAM Role to describe resources in your environment [create complete] [11.6s]
✔ Provisioned bootstrap resources for environment test in region cn-northwest-1 under application test.
✔ Provisioned bootstrap resources for environment test.
✔ Proposing infrastructure changes for the test-test environment.
✘ deploy environment test: check if changeset is empty: create change set copilot-bc6a4f6f-026c-4945-9702-2b85776f7949 for stack test-test: ValidationError: Template error: resource InternalWorkloadsHostedZone does not support attribute type Id in Fn::GetAtt
status code: 400, request id: 9779d95f-f574-48a7-a44e-7f7e03378dff: describe change set copilot-bc6a4f6f-026c-4945-9702-2b85776f7949 for stack test-test: ChangeSetNotFound: ChangeSet [copilot-bc6a4f6f-026c-4945-9702-2b85776f7949] does not exist
status code: 404, request id: a0e077f9-0a41-4e0d-8de8-6ebda017b3ea
copilot version: 1.21.0 and 1.21.1
AWS Region: cn-northwest-1
Demo APP:
https://docs.aws.amazon.com/zh_cn/AmazonECS/latest/developerguide/getting-started-aws-copilot-cli.html
Process and Error：
$ git clone https://github.com/aws-samples/amazon-ecs-cli-sample-app.git demo-app
$ cd demo-app/
$ ls
CODE_OF_CONDUCT.md CONTRIBUTING.md Dockerfile index.html LICENSE README.md
$ copilot init
Welcome to the Copilot CLI! We're going to walk you through some questions
to help you get set up with a containerized application on AWS. An application is a collection of
containerized services that operate together.
Workload type: Load Balanced Web Service
Service name: demo
Dockerfile: ./Dockerfile
parse EXPOSE: no EXPOSE statements in Dockerfile ./Dockerfile
Port: 80
Ok great, we'll set up a Load Balanced Web Service named demo in application test listening on port 80.
✔ Proposing infrastructure changes for stack test-infrastructure-roles
✔ The directory copilot will hold service manifests for application test.
✔ Wrote the manifest for service demo at ../copilot/demo/manifest.yml
Your manifest contains configurations like your container size and port (:80).
✔ Created ECR repositories for service demo.
All right, you're all set for local development.
Deploy: Yes
✔ Manifest file for environment test already exists at ../copilot/environments/test/manifest.yml, skipping writing it.
✔ Linked account 456370280007 and region cn-northwest-1 to application test.
✔ Proposing infrastructure changes for the test-test environment.
✔ Provisioned bootstrap resources for environment test in region cn-northwest-1 under application test.
✔ Provisioned bootstrap resources for environment test.
✔ Proposing infrastructure changes for the test-test environment.
✘ deploy environment test: check if changeset is empty: create change set copilot-bc6a4f6f-026c-4945-9702-2b85776f7949 for stack test-test: ValidationError: Template error: resource InternalWorkloadsHostedZone does not support attribute type Id in Fn::GetAtt
status code: 400, request id: 9779d95f-f574-48a7-a44e-7f7e03378dff: describe change set copilot-bc6a4f6f-026c-4945-9702-2b85776f7949 for stack test-test: ChangeSetNotFound: ChangeSet [copilot-bc6a4f6f-026c-4945-9702-2b85776f7949] does not exist
status code: 404, request id: a0e077f9-0a41-4e0d-8de8-6ebda017b3ea