Deploy tasks using AWS CLI about aws-microservices-deploy-options

[arun-gupta]

Only taskdefs have been created with #106 but the deployment is still missing.

[arun-gupta]

Deployment is still missing and is being worked upon

[arun-gupta]

Creating cluster using CloudFormation and deploying the services using AWS CLI is not the recommended pattern. Here is the text for deploying to AWS CLI so far:

. Register task definitions:
.. In `webapp.json`, update the `INTERNAL_ALB_URL_GOES_HERE` to the value of `ALBPrivateCNAME`.
.. Register taskdefs:

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

. Create services. Replace the value in the following command with the output from the CloudFormation template, and create the services
.. `greeting` service:

  aws ecs create-service \
    --cluster <cluster-name> \
    --service-name greeting-service \
    --task-definition greeting \
    --desired-count 1 \
    --launch-type "FARGATE" \
    --load-balancer "targetGroupArn=<greeting-target-group-ARN>,containerName=greeting,containerPort=8081" \
    --health-check-grace-period-seconds 60 \
    --network-configuration "awsvpcConfiguration={subnets=[<private-subnet-name1>,<private-subnet-name-2>],securityGroups=<sg-namehere>,assignPublicIp=ENABLED}"

.. `name` service:

  aws ecs create-service \
    --cluster <cluster-name> \
    --service-name name-service \
    --task-definition name \
    --desired-count 1 \
    --launch-type "FARGATE" \
    --load-balancer "targetGroupArn=<name-target-group-ARN>,loadBalancerName=<private-ALB-name>,containerName=name,containerPort=8082" \
    --health-check-grace-period-seconds 60 \
    --network-configuration "awsvpcConfiguration={subnets=[<private-subnet-name1>,<private-subnet-name-2>],securityGroups=<sg-namehere>,assignPublicIp=ENABLED}"

.. `webapp` service:

  aws ecs create-service \
    --cluster <cluster-name> \
    --service-name webapp-service \
    --task-definition webapp \
    --desired-count 1 \
    --launch-type "FARGATE" \
    --load-balancer "targetGroupArn=<webapp-target-group-ARN>,containerName=webapp,containerPort=8080" \
    --health-check-grace-period-seconds 60 \
    --network-configuration "awsvpcConfiguration={subnets=[<private-subnet-name-1>,<private-subnet-name-2>],securityGroups=<sg-namehere>,assignPublicIp=ENABLED}"

Access the service:

curl http://<public-ALB-CNAME>

Closing the issue for now.