使用 Amazon Migration Hub Refactor Spaces 和 Amazon Copilot 将单体应用程序分解为多个微服务

brew install aws/tap/copilot-cli

cd ./amazon-ecs-nodejs-microservices/
copilot app init

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

$ copilot env init
Environment name: monolith

Which credentials would you like **to** use **to** create api?  [Use
arrows **to** move, type **to** filter, ? **for** more help]
   Enter temporary credentials
  > [profile default]

Environment name: monolith
Credential source: [profile default]

 Would you like to use the default configuration for a new environment?
 - A new VPC with 2 AZs, 2 public subnets and 2 private subnets 
 - A new ECS Cluster
 - New IAM Roles to manage services and jobs in your environment
 [Use arrows to move, type to filter]
 > Yes, use default.
 Yes, but I'd like configure the default resources (CIDR ranges, AZs).
 No, I'd like to import existing resources (VPC, subnets).

Environment name: monolith
Credential source: [profile default]
Default environment configuration? Yes, use default.
✔ Wrote the manifest for environment api at copilot/environments/api/manifest.yml
- Update regional resources with stack set "api-infrastructure" [succeeded] [0.0s]
- Update regional resources with stack set "api-infrastructure" [succeeded] [130.8s]
 - Update resources in region "us-east-1" [create complete] [130.4s]
 - ECR container image repository for "monolith" [create complete] [2.5s]
 - KMS key to encrypt pipeline artifacts between stages [create complete] [124.5s]
 - S3 Bucket to store local artifacts [create complete] [2.4s]
✔ Proposing infrastructure changes for the api-api environment.
- Creating the infrastructure for the api-api environment. [create complete] [56.0s]
 - An IAM Role for AWS CloudFormation to manage resources [create complete] [22.4s]
 - An IAM Role to describe resources in your environment [create complete] [25.0s]
✔ Provisioned bootstrap resources for environment api in region us-east-1 under application api.

$ copilot env deploy --name monolith

✔ Proposing infrastructure changes for the api-api environment.
- Creating the infrastructure for the api-api environment. [update complete] [78.3s]
 - 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] [1.4s]
 - An Internet Gateway to connect to the public internet [create complete] [16.0s]
 - Private subnet 1 for resources with no internet access [create complete] [1.7s]
 - Private subnet 2 for resources with no internet access [create complete] [1.7s]
 - 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.1s]
 - Public subnet 2 for resources that can access the internet [create complete] [6.0s]
 - A private DNS namespace for discovering services within the environment [create complete] [46.3s]
 - A Virtual Private Cloud to control networking of your AWS resources [create complete] [11.6s]

$ copilot svc init

Note: It's recommended to run this command in the root of your Git repository.
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.


 Which workload type represents your architecture? [Use arrows to move, type to filter, ? for more help]
 Request-Driven Web Service (App Runner)
 > Load Balanced Web Service (Internet to ECS on Fargate)
 Backend Service (ECS on Fargate)
 Worker Service (Events to SQS to ECS on Fargate)
 Scheduled Job (Scheduled event to State Machine to Fargate)

Workload type: Load Balanced Web Service

What do you want to name this service? [? for help] monolith

Choose Enter custom path for your Dockerfile.

Workload type: Load Balanced Web Service
Service name: monolith

 Which Dockerfile would you like to use for monolith? [Use arrows to move, type to filter, ? for more help]
 > Enter custom path for your Dockerfile

Service type: Load Balanced Web Service
Service name: monolith
Dockerfile: Enter custom path for your Dockerfile
Dockerfile: 2-containerized/services/api/Dockerfile

✔ Wrote the manifest for service monolith at copilot/monolith/manifest.yml

The manifest for the "monolith" service.
Read the full specification for the "Load Balanced Web Service" type at:
 https://aws.github.io/copilot-cli/docs/manifest/lb-web-service/
Your service name will be used in naming your resources like log groups, ECS services, etc.
name: monolith
type: Load Balanced Web Service

Distribute traffic to your service.
http:
 # Requests to this path will be forwarded to your service.
 # To match all requests you can use the "/" path.
 path: '/'
 # You can specify a custom health check path. The default is "/".
 # healthcheck: '/'

$ copilot svc deploy --name monolith
Only found one service, defaulting to: monolith
Only found one environment, defaulting to: monolith
Building your container image: docker build -t 837028011264.dkr.ecr.us-east-1.amazonaws.com/api/monolith --platform linux/x86_64 /Users/sparaaws/github/spara/amazon-ecs-nodejs-microservices/2-containerized/services/api -f /Users/sparaaws/github/spara/amazon-ecs-nodejs-microservices/2-containerized/services/api/Dockerfile
[+] Building 43.3s (10/10) FINISHED
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 36B 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [internal] load metadata for docker.io/mhart/alpine-node:7.10.1 5.6s
=> [auth] mhart/alpine-node:pull token for registry-1.docker.io 0.0s
=> [internal] load build context 0.0s
=> => transferring context: 392B 0.0s
=> [1/4] FROM docker.io/mhart/alpine-node:7.10.1@sha256:d334920c966d440676ce9d1e6162ab544349e4a4359c517300391c877bcffb8c 0.0s
=> => resolve docker.io/mhart/alpine-node:7.10.1@sha256:d334920c966d440676ce9d1e6162ab544349e4a4359c517300391c877bcffb8c 0.0s
=> CACHED [2/4] WORKDIR /srv 0.0s
=> [3/4] ADD . . 0.0s

✔ Proposing infrastructure changes for stack api-api-monolith
- Creating the infrastructure for stack api-api-monolith [create complete] [360.8s]
- Service discovery for your services to communicate within the VPC [create complete] [0.0s]
- Update your environment's shared resources [update complete] [149.9s]
- A security group for your load balancer allowing HTTP traffic [create complete] [5.9s]
- An Application Load Balancer to distribute public traffic to your services [create complete] [123.0s]
- A load balancer listener to route HTTP traffic [create in progress] [198.5s]
- An IAM role to update your environment stack [create complete] [23.5s]
- An IAM Role for the Fargate agent to make AWS API calls on your behalf [create complete] [19.9s]
- A HTTP listener rule for forwarding HTTP traffic [create complete] [3.5s]
- A custom resource assigning priority for HTTP listener rules [create complete] [5.1s]
- A CloudWatch log group to hold your service logs [create complete] [1.5s]
- An IAM Role to describe load balancer rules for assigning a priority [create complete] [23.5s]
- An ECS service to run and maintain your tasks in the environment cluster [create complete] [117.0s]
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 [create complete] [15.0s]
- An ECS task definition to group your containers and run them on ECS [create complete] [0.0s]
- An IAM role to control permissions for the containers in your tasks [create complete] [23.5s]
✔ Deployed service monolith.
Recommended follow-up action:
- You can access your service at http://api-a-Publi-DU44D9VOSXLA-792918025.us-east-1.elb.amazonaws.com over the internet

{"id":3,"username":"pb","name":"Bonnibel Bubblegum","bio":"Scientist, bearer of candy power, ruler of the candy kingdom"}

{"id":2,"title":"Party at the candy kingdom tomorrow","createdBy":3}

[{"thread":1,"text":"Has anyone checked on the lich recently?","user":4},{"thread":1,"text":"I'll stop by and see how he's doing tomorrow!","user":2},{"thread":2,"text":"Come party with the candy people tomorrow!","user":3},{"thread":2,"text":"Mathematical!","user":2},{"thread":2,"text":"I'll bring my guitar","user":1},{"thread":3,"text":"I need a new guitar to play the most savory licks in Ooo","user":1}]

[{"thread":1,"text":"Has anyone checked on the lich recently?","user":4},{"thread":1,"text":"I'll stop by and see how he's doing tomorrow!","user":2}]

aws cloudformation deploy --template-file rs.yaml --stack-name <<Stack Name>> --parameter-override MonolithUrl=<<MonolithUrl>>

o6rvhiz-1055935381.us-west-2.elb.amazonaws.com/api

Waiting for changeset to be created..
Waiting for stack create/update to complete

aws cloudformation describe-stacks --stack-name <<Stack Name>> --query "Stacks[].Outputs"

[
 [
 {
 "OutputKey": "rsProxyURL",
 "OutputValue": "https://zx8lisag1a.execute-api.us-east-1.amazonaws.com/prod",
 "Description": "The API Gateway Proxy URL for the Refactor Spaces Application"
 },
 {
 "OutputKey": "VPCId",
 "OutputValue": "vpc-05d73902a4d92",
 "Description": "The ID of the VPC that this stack is deployed in"
 },
 {
 "OutputKey": "appId",
 "OutputValue": "env-xA8QIyk4|app-1b8Omyo2",
 "Description": "The ID of Refactor Spaces App"
 },
 {
 "OutputKey": "envId",
 "OutputValue": "env-xA8QIyk4",
 "Description": "The ID of Refactor Spaces Env"
 },
 {
 "OutputKey": "rsServiceId",
 "OutputValue": "svc-3yXgDEnW9",
 "Description": "The ID of Refactor Spaces Monolith"
 }
 ]
]

$ copilot env init --name posts --profile default

Would you like to use the default configuration for a new environment?
 - A new VPC with 2 AZs, 2 public subnets and 2 private subnets
 - A new ECS Cluster
 - New IAM Roles to manage services and jobs in your environment
 [Use arrows to move, type to filter]
 > Yes, use default.
 Yes, but I'd like configure the default resources (CIDR ranges, AZs).
 No, I'd like to import existing resources (VPC, subnets).

Default environment configuration? Yes, use default.
✔ Wrote the manifest for environment posts at copilot/environments/posts/manifest.yml
- Update regional resources with stack set "api-infrastructure" [succeeded] [10.7s]
✔ Proposing infrastructure changes for the api-posts environment.
- Creating the infrastructure for the api-posts environment. [create complete] [35.5s]
 - An IAM Role for AWS CloudFormation to manage resources [create complete] [14.3s]
 - An IAM Role to describe resources in your environment [create complete] [15.2s]
✔ Provisioned bootstrap resources for environment posts in region us-east-1 under application api.
Recommended follow-up actions:
 - Update your manifest copilot/environments/posts/manifest.yml to change the defaults.
 - Run `copilot env deploy --name posts` to deploy your environment.

✔ Proposing infrastructure changes for the api-posts environment.
- Creating the infrastructure for the api-posts environment. [update complete] [74.2s]
 - An ECS cluster to group your services [create complete] [2.7s]
 - A security group to allow your containers to talk to each other [create complete] [4.1s]
 - An Internet Gateway to connect to the public internet [create complete] [14.4s]
 - Private subnet 1 for resources with no internet access [create complete] [1.3s]
 - Private subnet 2 for resources with no internet access [create complete] [1.3s]
 - A custom route table that directs network traffic for the public subnets [create complete] [8.6s]
 - Public subnet 1 for resources that can access the internet [create complete] [1.3s]
 - Public subnet 2 for resources that can access the internet [create complete] [1.3s]
 - A private DNS namespace for discovering services within the environment [create complete] [48.9s]
 - A Virtual Private Cloud to control networking of your AWS resources [create complete] [12.8s]

copilot env init --name users

copilot env deploy --name users

copilot env init --name threads

copilot env deploy --name threads

$ copilot svc init --name posts --app api --dockerfile 3-microservices/services/posts/Dockerfile --svc-type "Load Balanced Web Service"

Note: It's best to run this command in the root of your workspace.
Note: Architecture type arm64 has been detected. We will set platform 'linux/x86_64' instead. If you'd rather build and run as architecture type arm64, please change the 'platform' field in your workload manifest to 'linux/arm64'.
✔ Wrote the manifest for service posts at copilot/posts/manifest.yml
Your manifest contains configurations like your container size and port (:3000).


- Update regional resources with stack set "api-infrastructure" [succeeded] [9.1s]
 - Update resources in region "us-east-1" [update complete] [6.8s]
 - ECR container image repository for "posts" [create complete] [4.1s]
Recommended follow-up actions:
 - Update your manifest copilot/posts/manifest.yml to change the defaults.
 - Run `copilot svc deploy --name posts --env test` to deploy your service to a test environment.

copilot svc init --app api --dockerfile 3-microservices/services/users/Dockerfile --name users --svc-type "Load Balanced Web Service"

copilot svc init --app api --dockerfile 3-microservices/services/threads/Dockerfile --name threads --svc-type "Load Balanced Web Service

# Distribute traffic to your service.
http:
 # Requests to this path will be forwarded to your service.
 # To match all requests you can use the "/" path.
 path: 'api/posts'

$ copilot svc deploy --name posts --env posts
Building your container image: docker build -t 929897017989.dkr.ecr.us-east-1.amazonaws.com/api/posts:latest --platform linux/x86_64 --label com.aws.copilot.image.builder=copilot-cli --label com.aws.copilot.image.container.name=posts --label com.aws.copilot.image.version=v1.27.0 /Users/theheman/Library/CloudStorage/WorkDocsDrive-Documents/Downloads/amazon-ecs-nodejs-microservices-master/3-microservices/services/posts -f /Users/theheman/Library/CloudStorage/WorkDocsDrive-Documents/Downloads/amazon-ecs-nodejs-microservices-master/3-microservices/services/posts/Dockerfile
[+] Building 16.5s (9/9) FINISHED docker:desktop-linux
 => [internal] load build definition from Dockerfile 0.0s
 => => transferring dockerfile: 238B 0.0s
 => [internal] load .dockerignore 0.0s
 => => transferring context: 2B 0.0s
 => [internal] load metadata for docker.io/mhart/alpine-node:7.10.1 1.2s
 => [1/4] FROM docker.io/mhart/alpine-node:7.10.1@sha256:d334920c966d440676ce9d1e6162ab544349e4a4359c517300391c877bcffb8c 0.0s
 => [internal] load build context 0.0s
 => => transferring context: 617B 0.0s
 => CACHED [2/4] WORKDIR /srv 0.0s
 => [3/4] ADD . . 0.0s
 => [4/4] RUN npm install 15.2s
 => exporting to image 0.0s
 => => exporting layers 0.0s
 => => writing image sha256:c31c780560d4ab8e347fac4671e56731ee5dd1065936a4bfbf5f161bf633fed3 0.0s 
 => => naming to 929897017989.dkr.ecr.us-east-1.amazonaws.com/api/posts:latest 0.0s 
 
What's Next? 
 View summary of image vulnerabilities and recommendations → docker scout quickview
Login Succeeded
The push refers to repository [929897017989.dkr.ecr.us-east-1.amazonaws.com/api/posts]

copilot svc deploy --name threads --env threads
copilot svc deploy --name users --env users

aws cloudformation deploy \
 --template-file rs-service.yaml \
 --stack-name <<stackname>> 
 --parameter-override EnvironmentId=<<14 digit envID env-xxxxxxxxxx>> ApplicationID=<<14 digit appId app-xxxxxxxxxx>> PostsUrl=http://<<PostsUrl>>.elb.amazonaws.com UsersUrl=http://<<UsersUrl>>.elb.amazonaws.com ThreadsUrl=http://<<ThreadsUrl>>.elb.amazonaws.com \
 --output table

$ copilot svc delete --name monolith
Sure? Yes
✔ Delete stack api-monolith-monolith
- Update regional resources with stack set "api-infrastructure" [succeeded] [8.7s]
 - Update resources in region "us-east-1" [update complete] [8.5s]


✔ Deleted service monolith from application api.
Recommended follow-up action:
 - Run `copilot pipeline deploy` to update the corresponding pipeline if it exists.

copilot app delete --name api