Step two of setting up Ansible in AWS is going to start with creating your other services, specifically databases.
We are going to take advantage of the RDS instances instead of standing up an EC2 instance and installing PostgreSQL there. You could do that if required but it will fall outside the scope of this guide.
I recommend two RDS Instances. One for your Tower database and one for your Automation Hub database.
Set up your database using your normal settings. Be sure to chose PostgreSQL version 12 or higher. I went with 13.7 so I wouldn’t have to upgrade as soon.
Also make sure you assign the security group you created in the last article. If not, its easy enough to change. I’ll be honest, I missed it the first time because the RDS screen calls it a VPC security group and it’s below the section about connecting to EC2 instances.
Before hitting the Create database button, expand the Additional Configuration. Be sure to specify your initial database name, this will save you from having to connect to the RDS and manually create it.
Once your database is created browse out to its Connectivity & security tab and grab the endpoint. You’ll need this when you create the inventory file for the AAP install.
If you didn’t get your security group added now’s the time to change it.
You can also jump over to the Configuration tab and double check your DB name and details if you didn’t record them.
That’s all there is to configuring the database, repeat the process for your Automation Hub database and you’ll be ready to go from that stand point.
Installing AAPv2 on AWS – Part 1 – Security Groups
Installing AAPv2 on AWS – Part 2 – Databases <- you are here
Pingback: Installing Ansible Automaton Platform on AWS part 1 - Eric's Custom Works
Pingback: Installing Ansible Automaton Platform on AWS part 3 - Load Balancers - Eric's Custom Works