Table of Contents
Goals of this project to automate Tomcat application server deployment on multi environment – Dev & Prod.
- Install Ansible control engine on development platform.
- Install Visual Code on development platform.
- Deploy Ansible Control Node, Dev Application server & Prod Application Server as per the above architecture.
Develop Ansible Role to provision tomcat application server on target environment as per below configuration
- Install common dependencies AWS-CLI, wget, curl, git
- Install Java 11
- Download and install tomcat into CATALINA HOME ‘/usr/local/tomcat’
- Configure systemd service to manage ‘tomcat’ service.
- Configure tomcat user ‘admin’ and assign manager & admin role access.
- Integrate Ansible vault to store the tomcat user ‘admin’ passwords.
- Restart Apache tomcat service only when tomcat configuration file changes.
- Run Ansible Playbook to invoke the Role and configure the Dev environment
- Run Ansible Playbook to invoke the Role and configure the Prod environment
- Access Tomcat page using curl from Ansible control node.
Note: Goal is to achieve the desired configuration on target nodes, this project not listed any specific best practices to follow, But recommended to apply variables, secure passwords, handlers, custom inventory path etc..
I completed assignment with configuring VPC end points to start the SSM session to connect to the control node which is running in Private subnet.
PR@ please let us know is there any way to connect to the instances in Private subnet.
Hi think that you will need to have a NAT in a public subnet, then configure a route table for that NAT GW, and probabily make some add in inboudns rules in SG. I hope that helps.