05_RDS

create rds box ir engine is backed by a sql server we use mariadb in development, but it has also been run on aws with aurora without issue most other versions of sql should work but have not been explicitly tested accessing rds box from an external machine by default, an rds box is only accessible from within the vpc it's located if you want to be able to connect to it from outside that vpc, you'll need to either set up a bastion box and ssh into that box, or make the rds box publicly accessible setting up a bastion box is not covered here at this time the steps to make it public will be noted below by make rds public create rds instance go to rds and click the create database button most options can be left at their default values under settings, give a more descriptive db cluster identifier the master username can be left as admin; enter a master password and then enter it again in confirm password under db instance class, pick an option that best meets your pricing needs under availability and durability, it's recommended that you leave it on the default of making an aurora replica in another az under connectivity, make sure that it's in the vpc that was made as part of the eks cluster make rds public if you want to be able to access it externally, you should set public access to 'yes' under vpc security group, select the ones titled eksctl \<eks cluster name> cluster clustersharednodesecuritygroup \<random string> and eks clustersg \<eks cluster name> \<random string> open the top level additional configuration dropdown (not the one within connectivity) under database options > initial database name, name the default database and save this for later use in the helm config file finally, click the create database button at the very bottom of the page make rds public you will need to add a security group to the rds instance that allows traffic over port 3306 (or whatever port you chose to run it on) you can have this sg only let in traffic from your ip address(es) if you want to be very secure about this, or from anywhere (0 0 0 0/0) if you're less concerned about someone getting access some values to note for dev/prod template values yaml sql database will be what you entered for initial database name sql user and sql password will be the name and password of the admin user sql host will be the endpoint of the rds instance/cluster; find this by going to rds > databases, clicking on either the lone db identifier (if made in a single az) or the top level regional cluster identifier (if set up in a multi az deployment); the look for endpoint (single az) or, if multi az, the endpoint name that has type 'writer instance'