I’ve finally gotten around to reinstalling my VPS w/ a supported system this time, and while poking around, I noticed that Route53 is supported. With some googling, I have managed to create an access token. At first, I was creating a root access token, but AWS cried about this and told me I was a bad boy. After some digging, I found that when I initially set up my AWS console eight years ago, I had created an access group in the IAM console with a privileged user. Attached to that user, I created my access key and plugged it into the R53 module, and promptly got told it was wrong.
Am I missing something? With the help of a friend, we did find some info here with similar language, but the solution there was for that user to migrate to AWS S3 backups (which doesn’t apply to me as I am not using any Cloud Storage).
OK, I didn’t know I needed to create a policy. Admittedly, I know the basics of creating and managing zones in Route53, but I know very little about what else I can do in my AWS Console, and the documentation is a bit much for me. I also don’t want to do something that will inadvertently cost me a ton of money I can’t afford.
That being said, is there documentation that will help walk me through creating the things I need to create so that the Route53 module will work correctly? I know there is AWS’s documentation, but that is overwhelmingly dense.
My config not correct yet as I get a error when I switch the the route53 on one of the virtual servers, I’m only testing as I use another service. Did you get it working?
I did this for all my domains/subdomains that I’ve added to my VPS. I also added a new subdomain that was not already in DNS, but the new subdomain was not added to my r53 zone for that domain. This leads me to believe that I’ve done something wrong on either Virtualmin, my r53 configuration in my Amazon acct, or both.
Thanks. Those screenshots were super helpful. I was able to add the AmazonRoute53FullAccess permissions group to my user.
I added my Access/SecretKeys to Backup and Restore -> Cloud Storage Providers (even though I am not using any S3 ObjectStorage solutions). I got this from reading a very old Virtualmin forum post from 2012 of all places.
Then, I added the same Access/Secret Keys to Address and Networking -> Cloud DNS Providers -> Amazon Route 53.
I went to DNS Settings -> DNS Options and selected Amazon Route 53 from the drop-down menu under Hosting for DNS Records (I did this for every domain/subdomain I’ve set up on this VPS).
Once I did it in that order, I no longer got error messages from the Amazon Route 53 module. Since then, I’ve added a new subdomain that was not already in DNS, Virtualmin has now successfully created a new zone file on Route53 of subdomain.mydomain.tld and populated that zone with 29 new records.
This problem arose because I needed to create a subdomain.subdomain.domain.tld, which is a child of subdomain.domain.tld (because they are related). Virtualmin successfully created the child domain, but all the DNS records appear to be local, I have no DNS Settings -> DNS Options menu item, just DNS Settings -> DNS Records.
So, half my problem has been resolved, but I think I might have found an incomplete portion of the module. Perhaps a bug? I don’t see any way to convert this subdomain.subdomain.domain.tld local DNS record into using the same zone file as subdomain.domain.tldor create a new zone file ofsubdomain.subdomain.domain.tldin my Route 53 account as it did forsubdomain.domain.tld`
EDIT: Also of note, Virtualman CAN now see records in an existing zone file on Route53; it just appears to give up on making any changes to the zone file unless it created it in the first place.
EDIT: I retract part of my statement. When I created the child subdomain.subdomain.domain.tld, Virtualmin, in fact, made changes to the zone file subdomain.domain.tld.
You can nest them. It looks like I got it all working now. I had to purchase a new domain for a project, and when I added it to Virtualmin, it was successfully added to Route53 with no issues.
