user-profile-service.md

Back to main guide

---

Build and deploy User-Profile-Service

In this section we will build and deploy the user-profile-service as an ECS service. We will deploy the service on Container instances.

The ECS Task-Definition and Service-Definition are located in the user-profile-service folder.

---

Task 1 - Build user-profile-service docker image

1. Navigate to the user-profile-service folder

cd ../user-profile-service

2. Create ECR Repository for user-profile-service

# Note the repositoryUri - output of below command
aws ecr create-repository --repository-name ecs-workshop/user-profile-service

3. Build the Docker Image and push it to ECR

docker build -t <repositoryUri>:latest .

4. Login to Elastic Container Registry (ECR)

aws ecr get-login --no-include-email | bash

5. Push the Docker image to ECR

docker push <repositoryUri>:latest

---

Task 2 - Setup the ALB

You can create a listener with rules to forward requests based on the URL path. This is known as path-based routing. If you are running microservices, you can route traffic to multiple back-end services using path-based routing.

The Application Load Balancer(ALB), Listner and the necessary Target groups have been created by the ecs-workshop CloudFormation Stack deployed in the Lab Setup section. We will now add rules to the ALB Listener to enable path-based routing to the user-profile-service.

# Refer to ecs-workshop CloudFormation stack output to get values of:
# <ALBListenerArn>
# <UserProfileServiceALBTargetGroupArn>
aws elbv2 create-rule --listener-arn "<ALBListenerArn>" \
--priority 2 \
--conditions Field=path-pattern,Values='/users' \
--actions Type=forward,TargetGroupArn="<UserProfileServiceALBTargetGroupArn>"

aws elbv2 create-rule --listener-arn "<ALBListenerArn>" \
--priority 3 \
--conditions Field=path-pattern,Values='/uploadURL' \
--actions Type=forward,TargetGroupArn="<UserProfileServiceALBTargetGroupArn>"

Verify the ALB Listener rules have been created.

aws elbv2 describe-rules --listener-arn "<ALBListenerArn>"

---

Task 3 - Deploy the user-profile-service as ECS Service

1. Create a CloudWatch LogGroup to collect user-profile-service logs.

aws logs create-log-group --log-group-name ecs-workshop/user-profile-service

2. Let us now register the ECS Task Definition for the user-profile-service. A task-definition.json is located in the user-profile-service folder, replace the below parameter placeholders in the file with the values appropriate to your environment.

Parameters	Value
<repositoryUri>	ECR repository Uri of contacts-service
<AWS-REGION>	AWS Region e.g. us-east-1
<ImageS3BucketName>	ecs-workshop CloudFormation stack Output
<UserProfileDdbTable>	ecs-workshop CloudFormation stack Output
<ContactsDdbTable>	ecs-workshop CloudFormation stack Output
<CognitoUserPoolId>	ecs-workshop CloudFormation stack Output
<CognitoUserPoolClientId>	ecs-workshop CloudFormation stack Output
<CognitoIdentityPoolId>	ecs-workshop CloudFormation stack Output

aws ecs register-task-definition --cli-input-json file://task-definition.json

3. We will now deploy the ECS service. Replace the following parameter place holders in the service-definition.json.

Parameter	Value
<UserProfileServiceALBTargetGroupArn>	ecs-workshop CloudFormation stack Output

# Deploy the user-profile-service
aws ecs create-service --cli-input-json file://service-definition.json

# Verify the user-profile-service has been deployed successfully
# The command will wait till the service has been deployed. No output is returned.
aws ecs wait services-stable \
--cluster ecs-workshop-cluster \
--services user-profile-service

# Verify the desired and running tasks for the service
aws ecs describe-services \
--cluster ecs-workshop-cluster \
--services user-profile-service \
--query 'services[0].{desiredCount:desiredCount,runningCount:runningCount,pendingCount:pendingCount}'

---

Back to main guide