At this stage:
In this section, you will launch your Cloudformation template and review the deployment process in AWS console.
In your web server, run suggested command from “app2container generate app-deployment” output. Update the <java-app-id> with your ID.
aws cloudformation deploy --template-file /root/app2container/<java-app-id>/EcsDeployment/ecs-master.yml --capabilities CAPABILITY_NAMED_IAM --stack-name a2c-<java-app-id>-ECS
The process will take few mins. Go back to AWS Console to review the background activities during the deployment.
root@ip-10-0-0-202:/home/ubuntu# aws cloudformation deploy --template-file /root/app2container/<java-app-id>/EcsDeployment/ecs-master.yml --capabilities CAPABILITY_NAMED_IAM --stack-name a2c-<java-app-id>-ECS Waiting for changeset to be created.. Waiting for stack create/update to complete ...
Navigate to the Cloudformation console
After ALB stack and Cluster stack have been completed, Navigate to ECS Service.
Notice that your container is deployed into FARGATE. This has been selected in deployment.json file in extract and containerize steps. You can change it to "EC2", if you prefer to have the control on the host servers and manage them.
<a href="https://aws.amazon.com/fargate" target="_blank">AWS FARGATE</a> is a serverless compute engine for containers. With FARGATE, you dont need to provision and manage servers and you only pay for the resources required to run your containers.
After the cluster is created, under Services tab, you will see your application deployed and service status is “ACTIVE”
Click Tasks tab. Here you can see that Task has been created and is running.
Click Clusters and when you are inside the clusters, Click Services tab and go into Service.
Notice that , VPC, subnet and Security Groups are also defined. You can update those based on your environment requirements.
Inside the Target Groups, Review the Target Group configuration
In the Loadbalancers section, Review the Loadbalancer configurations for your application.