Deployment consideration
If you are in a shop where you roll out multiple RDS instances, then my advice would be to consider the following architecture in the overall design for your RDS DB instance deployment. In this architecture, you have a public-facing bastion and RDS Admin Hub in the private subnet. The RDS Admin Hub could be a Linux or Windows machine, ensuring that it has an IAM role assigned which can interact with the RDS using CLI. You then host all your RDS instances in the private subnet. You may also think of integrating the RDS Admin Hub with your bastion. In that case, your bastion and RDS Admin Hub could be the same EC2 instance. It's up to you. I chose to keep RDS Admin Hub in the private subnet, as it is another critical access point to interact with RDS databases and is considered an extra layer of defense. This deployment consideration will allow you to have a standing DBA box all the time to troubleshoot any issues that you may encounter with RDS and also allow you...