One of my clients has _exactly_ 13 registered domains in their AWS Route 53 service. Thirteen!
I advised them to either get rid of one or register a new one—otherwise, bad luck might strike.
One of my clients has _exactly_ 13 registered domains in their AWS Route 53 service. Thirteen!
I advised them to either get rid of one or register a new one—otherwise, bad luck might strike.
I realized that I was spending 50¢ every month for 7 Route53 hosted zones at AWS, when I really don't need to do that for some of them. I'm using name.com
as my registrar, and they'll do basic #DNS service for free as a part of that.
I didn't want to spend an hour clicking and copy/pasting DNS records, so like any good geek I spent about 6 hours writing a script to do it for me.
It's a bit of a specialized need. If you're not hosted in #Route53 and not looking to go to name.com
, this is not useful to you at all, except as a curiosity of how badly I write python.
But if (a) you're cheap like me, and (b) you've made the same choices as me, this script will save you some time.
The punchline on my #DNS reconfiguration is that nothing went wrong because I didn’t actually make any changes that took effect. I do a weird config to have reliable DNS:
I have a hidden master that uses dnsmadeeasy as the public servers. They answer authoritatively but they’re getting records from my #powerdns server.
Well, one problem I have is using CDNs at the apex zone. I use #AWS #cloudfront as my #CDN. This is fine when you use #Route53 as your DNS. They can put alias records in at the apex. But it doesn’t work with dnsmadeeasy secondary zones. The way I run them.
Name dot com is my registrar. They can do alias records. So I think they also do DNS for free. I’m going to migrate my Route53 zones to the free DNS instead of paying $0.50 per zone per month. All this effort will save me about $6.50/month.
#homelab #selfhosting
Delete a DNS Record in a Hosted Zone with the AWS CLI
~~
It’s not as simple as you might imagine (as far as I know at the time of this writing)
~~
by Teri Radichel | July 13, 2023
#aws #dns #hostedzone #record #delete #route53
https://medium.com/cloud-security/delete-a-dns-record-in-a-hosted-zone-with-the-aws-cli-ea2e8bfc78a2
I just finished some functions for updating an NS record for a subdomain using the AWS CLI. The documentation is not exactly clear and…JSON. Will be converting this to CloudFormation later.
~~~
#dns #aws #subdomain #route53 #cli
Had some strange charges in GCP so had to deal with that. Also setting up a role to manage NS records for static website and thoughts on a Cloud Center of Excellence.
~~
#gcp #cloud #security #aws #route53 #domains #nameservers #centerofexcellence
~~
https://medium.com/cloud-security
I had such a nice time setting up a new domain on #AWS #Route53 with @arcserverless I've decided to transfer all my #domains away from #GoogleDomains!
Say what you will about #Amazon, they've built a very workable cloud platform.
An #EventBridge + #StepFunctions #nocode workflow that "changes the behavior of #ECS" and registers a single task/container public IP in a #Route53 A record.
https://github.com/aws/containers-roadmap/issues/737#issuecomment-1410169740
Transferring Files in S3 Between AWS Accounts: ACM.129 Migrating web site files and configuration before transferring domain names
~~~~~~
by Teri Radichel | Jan, 2023
#cloudsecurity #cybersecurity #aws #s3 #route53 #website #domainname
https://medium.com/cloud-security/transferring-files-in-s3-between-aws-accounts-8258397af095
I deployed my first fully #AWS website tonight using @enhance_dev #Route53 #APIGateway #Certificates #DNS #serverless
Who needs Netlify and Zeit!? I'm an ADULT! I can pay my own AWS bills!
(thanks for the help @brianleroux , @tbeseda @Kj on the Discord w/e they are on the fediverse)