使用 Amazon Copilot 在一小时内为连接微服务构建高效的 CI/CD 管道

git clone git@github.com:build-on-aws/automate-container-microservices-aws-copilot.git
cd automate-container-microservices-aws-copilot/code

.
├── backend
│ └── manifests
│ ├── backend
│ │ └── addons
│ ├── environments
│ │ └── development
│ └── pipelines
│ └── todobackend-main
└── frontend
 ├── manifests
 │ ├── environments
 │ │ └── development
 │ ├── frontend
 │ └── pipelines
 │ └── todofrontend-main
 └── webapp
 ├── public
 └── src
 ├── components
 └── modules

cd backend/

.
├── Dockerfile
├── app.py
└── requirements.txt

copilot app init todo

✔ Proposing infrastructure changes for stack todo-infrastructure-roles
- Creating the infrastructure for stack todo-infrastructure-roles [create complete] [39.0s]
 - A StackSet admin role assumed by CloudFormation to manage regional stacks [create complete] [16.0s]
 - An IAM role assumed by the admin role to create ECR repositories, KMS keys, and S3 buckets [create complete] [17.2s]
✔ The directory copilot will hold service manifests for application todo.

Recommended follow-up action:
 - Run `copilot init` to add a new service or job to your application.

Environment name: development
Credential source: [profile default]
Default environment configuration? Yes, use default.
✔ Wrote the manifest for environment development at copilot/environments/development/manifest.yml
- Update regional resources with stack set "todo-infrastructure" [succeeded] [0.0s]
- Update regional resources with stack set "todo-infrastructure" [succeeded] [125.6s]
 - Update resources in region "us-west-2" [create complete] [127.7s]
 - KMS key to encrypt pipeline artifacts between stages [create complete] [120.6s]
 - S3 Bucket to store local artifacts [create complete] [3.0s]
✔ Proposing infrastructure changes for the todo-development environment.
- Creating the infrastructure for the todo-development environment. [create complete] [41.5s]
 - An IAM Role for AWS CloudFormation to manage resources [create complete] [15.7s]
 - An IAM Role to describe resources in your environment [create complete] [16.3s]
✔ Provisioned bootstrap resources for environment development in region us-west-2 under application todo.
Recommended follow-up actions:
 - Update your manifest copilot/environments/development/manifest.yml to change the defaults.
 - Run `copilot env deploy --name development` to deploy your environment.

$ copilot env ls
development

Only found one environment, defaulting to: development
✔ Proposing infrastructure changes for the todo-development environment.
- Creating the infrastructure for the todo-development environment. [update complete] [73.1s]
 - An ECS cluster to group your services [create complete] [7.5s]
 - A security group to allow your containers to talk to each other [create complete] [0.0s]
 - An Internet Gateway to connect to the public internet [create complete] [17.1s]
 - Private subnet 1 for resources with no internet access [create complete] [3.4s]
 - Private subnet 2 for resources with no internet access [create complete] [3.3s]
 - A custom route table that directs network traffic for the public subnets [create complete] [10.9s]
 - Public subnet 1 for resources that can access the internet [create complete] [3.3s]
 - Public subnet 2 for resources that can access the internet [create complete] [0.0s]
 - A private DNS namespace for discovering services within the environment [create complete] [42.6s]
 - A Virtual Private Cloud to control networking of your AWS resources [create complete] [11.0s]

$ copilot svc init
Note: It's best to run this command in the root of your workspace.
Service type: Backend Service
Service name: backend
Dockerfile: ./Dockerfile
✔ Wrote the manifest for service backend at copilot/backend/manifest.yml
Your manifest contains configurations like your container size and port (:10000).

- Update regional resources with stack set "todo-infrastructure" [succeeded] [11.8s]
 - Update resources in region "us-west-2" [update complete] [6.3s]
 - ECR container image repository for "backend" [create complete] [2.2s]
Recommended follow-up actions:
 - Update your manifest copilot/backend/manifest.yml to change the defaults.
 - Run `copilot svc deploy --name backend --env test` to deploy your service to a test environment.

image:
 build: backend/Dockerfile
 # Port exposed through your container to route traffic to it.
 port: 10000
 healthcheck:
 command: ["CMD-SHELL", "curl -f http://localhost:10000/ishealthy || exit 1"]
 interval: 10s
 retries: 2
 timeout: 6s 
 start_period: 10s

@app.route('/ishealthy')
def receive_health_check():
 return "Health check succeed\n"

$ copilot storage init
Storage type: DynamoDB
Only found one workload, defaulting to: backend
Storage resource name: todotable
Lifecycle: Yes, the storage should be created and deleted at the same time as backend
Partition key: TodoId
Partition key datatype: Number
Sort key? No
✔ Wrote CloudFormation template at copilot/backend/addons/todotable.yml

Recommended follow-up actions:
 - Update backend's code to leverage the injected environment variable TODOTABLE_NAME.
 For example, in JavaScript you can write:
```
const storageName = process.env.TODOTABLE_NAME
```
 - Run `copilot deploy --name backend` to deploy your storage resources.

table_name = os.getenv('TODOTABLE_NAME')

✔ Proposing infrastructure changes for stack todo-development-backend
- Creating the infrastructure for stack todo-development-backend [create complete] [325.6s]
 - An Addons CloudFormation Stack for your additional AWS resources [create complete] [42.5s]
 - An IAM ManagedPolicy for your service to access the todotable db [create complete] [18.6s]
 - An Amazon DynamoDB table for todotable [create complete] [11.4s]
 - Service discovery for your services to communicate within the VPC [create complete] [0.0s]
 - Update your environment's shared resources [create complete] [0.0s]
 - An IAM role to update your environment stack [create complete] [20.4s]
 - An IAM Role for the Fargate agent to make AWS API calls on your behalf [create complete] [20.4s]
 - A CloudWatch log group to hold your service logs [create complete] [0.0s]
 - An ECS service to run and maintain your tasks in the environment cluster [create complete] [245.3s]
 Deployments 
 Revision Rollout Desired Running Failed Pending 
 PRIMARY 1 [completed] 1 1 0 0 
 - An ECS task definition to group your containers and run them on ECS [create complete] [3.2s]
 - An IAM role to control permissions for the containers in your tasks [create complete] [18.5s]
✔ Deployed service backend.
Recommended follow-up action:
 - You can access your service at backend:10000 with service connect.

Found only one deployed service backend in environment development
Task Summary

 Running ██████████ 1/1 desired tasks are running

Tasks

 ID Status Revision Started At
 -- ------ -------- ----------
 121b23ed RUNNING 1 12 minutes ago

mkdir todobackend
mv automate-container-microservices-aws-copilot/code/backend/* todobackend/

.
├── Dockerfile
├── app.py
├── copilot
│ ├─ backend
│ │ ├─ addons
│ │ │ └── todotable.yml
│ │ └── manifest.yml
│ └── environments
│ └── development
│ └── manifest.yml
├─ manifests
│ ├─ backend
│ │ ├─ addons
│ │ │ └── todotable.yml
│ │ └── manifest.yml
│ └── environments
│ └── development
│ └── manifest.yml
└── requirements.txt

cd todobackend
aws codecommit create-repository --repository-name todobackend --repository-description "My todoapp repository"
git init
git switch -c main
git remote add origin https://git-codecommit.$(aws configure get region).amazonaws.com/v1/repos/todobackend

Only one git remote detected. Your pipeline will follow 'https://git-codecommit.us-west-2.amazonaws.com/v1/repos/todobackend'.
fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
Your pipeline will follow branch 'main'.

Pipeline name: todobackend-main
What type of continuous delivery pipeline is this? Workloads
1st stage: development

✔ Wrote the pipeline manifest for todobackend at 'copilot/pipelines/todobackend-main/manifest.yml'
The manifest contains configurations for your pipeline.
Update the file to add stages, change the tracked branch, add test commands or manual approval actions.
✔ Wrote the buildspec for the pipeline's build stage at 'copilot/pipelines/todobackend-main/buildspec.yml'
The buildspec contains the commands to push your container images, and generate CloudFormation templates.
Update the "build" phase to unit test your services before pushing the images.

Required follow-up actions:
- Commit and push the copilot/ directory to your repository.
- Run `copilot pipeline deploy` to create your pipeline.

$ copilot pipeline deploy
Only found one pipeline; defaulting to: todobackend-main
✔ Successfully added pipeline resources to your application: todo
✔ Successfully created a new pipeline: todobackend-main

git add -A
git commit -m 'initial commit'
git push origin main

.
├── Dockerfile
├── backend.conf.template
├── nginx.conf
└── webapp
 ├── README.md
 ├── package.json
 ├── public
 │ ├── index.html
 │ ├── manifest.json
 │ └── robots.txt
 ├── src
 │ ├── App.css
 │ ├── App.test.tsx
 │ ├── App.tsx
 │ ├── Types.ts
 │ ├── components
 │ │ ├── TableOperation.tsx
 │ │ ├── TaskInput.tsx
 │ │ ├── TaskItem.tsx
 │ │ ├── TaskList.tsx
 │ │ └── util.ts
 │ ├── index.css
 │ ├── index.tsx
 │ ├── modules
 │ │ └── tasksModule.ts
 │ ├── react-app-env.d.ts
 │ ├── reportWebVitals.ts
 │ ├── rootReducer.ts
 │ ├── setupTests.ts
 │ └── store.ts
 └── tsconfig.json

Use existing application: Yes
Application name: todo
✔ Proposing infrastructure changes for stack todo-infrastructure-roles
✔ The directory copilot will hold service manifests for application todo.

Recommended follow-up action:
 - Run `copilot init` to add a new service or job to your application.

Note: It's best to run this command in the root of your workspace.
Service type: Load Balanced Web Service
Service name: frontend
Dockerfile: ./Dockerfile
✔ Wrote the manifest for service frontend at copilot/frontend/manifest.yml
Your manifest contains configurations like your container size and port (:80).

- Update regional resources with stack set "todo-infrastructure" [succeeded] [10.2s]
 - Update resources in region "us-west-2" [update complete] [9.0s]
 - ECR container image repository for "frontend" [create complete] [4.4s]
Recommended follow-up actions:
 - Update your manifest copilot/frontend/manifest.yml to change the defaults.
 - Run `copilot svc deploy --name frontend --env test` to deploy your service to a test environment.

✔ Proposing infrastructure changes for stack todo-development-frontend
- Creating the infrastructure for stack todo-development-frontend [create complete] [299.3s]
 - Service discovery for your services to communicate within the VPC [create complete] [0.0s]
 - Update your environment's shared resources [update complete] [115.4s]
 - A security group for your load balancer allowing HTTP traffic [create complete] [2.5s]
 - An Application Load Balancer to distribute public traffic to your services [create complete] [88.2s]
 - A load balancer listener to route HTTP traffic [create in progress] [154.6s]
 - An IAM role to update your environment stack [create complete] [18.7s]
 - An IAM Role for the Fargate agent to make AWS API calls on your behalf [create complete] [16.3s]
 - An HTTP listener rule for path `/` that forwards HTTP traffic to your tasks [create complete] [3.3s]
 - A custom resource assigning priority for HTTP listener rules [create complete] [2.6s]
 - A CloudWatch log group to hold your service logs [create complete] [0.0s]
 - An IAM Role to describe load balancer rules for assigning a priority [create complete] [14.7s]
 - An ECS service to run and maintain your tasks in the environment cluster [create complete] [125.2s]
 Deployments 
 Revision Rollout Desired Running Failed Pending 
 PRIMARY 1 [completed] 1 1 0 0 
 - A target group to connect the load balancer to your service on port 80 [create complete] [17.1s]
 - An ECS task definition to group your containers and run them on ECS [create complete] [2.2s]
 - An IAM role to control permissions for the containers in your tasks [create complete] [17.1s]
✔ Deployed service frontend.
Recommended follow-up action:
 - You can access your service at http://todo-Publi-14BEAZOWSOFPS-1809648126.us-west-2.elb.amazonaws.com over the internet.

Service: frontend
Task Summary

 Running ██████████ 1/1 desired tasks are running
 Health ██████████ 1/1 passes HTTP health checks

Tasks

 ID Status Revision Started At HTTP Health
 -- ------ -------- ---------- -----------
 fc25084a RUNNING 1 2 hours ago HEALTHY

mkdir todofrontend
mv automate-container-microservices-aws-copilot/code/frontend/* todofrontend/

.
├── Dockerfile
├── backend.conf.template
├── manifests
│ ├── environments
│ │ └── development
│ │ └── manifest.yml
│ └─── frontend
│ └── manifest.yml
├── nginx.conf
└── webapp
 ├── README.md
 ├── package.json
 ├── public
 │ ├── index.html
 │ ├── manifest.json
 │ └── robots.txt
 ├── src
 │ ├── App.css
 │ ├── App.test.tsx
 │ ├── App.tsx
 │ ├── Types.ts
 │ ├── components
 │ │ ├── TableOperation.tsx
 │ │ ├── TaskInput.tsx
 │ │ ├── TaskItem.tsx
 │ │ ├── TaskList.tsx
 │ │ └── util.ts
 │ ├── index.css
 │ ├── index.tsx
 │ ├── modules
 │ │ └── tasksModule.ts
 │ ├── react-app-env.d.ts
 │ ├── reportWebVitals.ts
 │ ├── rootReducer.ts
 │ ├── setupTests.ts
 │ └── store.ts
 └── tsconfig.json

cd todofrontend
aws codecommit create-repository --repository-name todofrontend --repository-description "My todoapp frontend repository"
git init
git switch -c main
git remote add origin https://git-codecommit.$(aws configure get region).amazonaws.com/v1/repos/todofrontend

Only one git remote detected. Your pipeline will follow 'https://git-codecommit.us-west-2.amazonaws.com/v1/repos/todofrontend'.
fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
Your pipeline will follow branch 'main'.
Pipeline name: todofrontend-main
What type of continuous delivery pipeline is this? Workloads
1st stage: development

✔ Wrote the pipeline manifest for todofrontend at 'copilot/pipelines/todofrontend-main/manifest.yml'
The manifest contains configurations for your pipeline.
Update the file to add stages, change the tracked branch, add test commands or manual approval actions.
✔ Wrote the buildspec for the pipeline's build stage at 'copilot/pipelines/todofrontend-main/buildspec.yml'
The buildspec contains the commands to push your container images, and generate CloudFormation templates.
Update the "build" phase to unit test your services before pushing the images.

Required follow-up actions:
- Commit and push the copilot/ directory to your repository.
- Run `copilot pipeline deploy` to create your pipeline.

Only found one pipeline; defaulting to: todofrontend-main
✔ Successfully added pipeline resources to your application: todo
✔ Successfully created a new pipeline: todofrontend-main

git add -A
git commit -m 'initial commit'
git push origin main

$ copilot app delete
Sure? Yes
✔ Delete stack todo-development-backend
- Update regional resources with stack set "todo-infrastructure" [succeeded] [7.9s]
 - Update resources in region "us-west-2" [update complete] [7.0s]

✔ Deleted service backend from application todo.
✔ Delete stack todo-development-frontend
- Update regional resources with stack set "todo-infrastructure" [succeeded] [6.7s]
 - Update resources in region "us-west-2" [update complete] [3.8s]

✔ Deleted service frontend from application todo.
✔ Retained IAM roles for the "development" environment
✔ Delete environment stack todo-development
✔ Deleted environment "development" from application "todo".
✔ Cleaned up deployment resources.
✔ Deleted pipeline todofrontend-main from application todo.
✔ Deleted pipeline todobackend-main from application todo.
✔ Deleted regional resources for application "todo"
✔ Delete application roles stack todo-infrastructure-roles
✔ Deleted application configuration.
✔ Deleted local .workspace file.

aws codecommit delete-repository --repository-name todofrontend
aws codecommit delete-repository --repository-name todobackend