* How other sites charge for a domain name
- The domain (abc.com) is available
---- Price => $14

* How AWS charges
- Your domain (abc.com) is available
--- Domain name => $18.99
--- DNS resolution => $17.88
--- Hosted zone (1) => $10.97
--- Route53 Interface => $45.67
--- Network ACL => $63.90
--- Security Group => $199.78
--- NAT Gateway (1) => $78.99
--- IP linking => $120.89
--- Peer Connection => $67.00
--- Reverve Endpoint => $120.44
--- DNS Propagation => $87.00
--- Egress Gateway => $98.34
--- DNS Queries (1m) => $0.40
--------------------------------
---- TOTAL => $2903.99
(Pay for what you use... learn more)
--------------------------------

Sooooo.. Aws's route53 and ELB outage nuked all our environments. 503 here, 503 there, 5xx everywhere.

Just sitting and picking nose for we've got nothing else to do now.. Who on the fucking earth thought it might be a great idea to centralize the whole fucking internet into 3 companies' hands!?!

How's your day?

I moved my website to aws and I managed to use cloudflare, load balancer (to skip around route53), ec2 and RDS with no programming skills. Starting to enjoy this :D

Vendor lock-in for cloud providers is really small, and you don't notice it until you need it. Route53 has an "import zone file" button, but they don't have an "export zone file" button. Yes, there are other tools and scripts to do it, but bit-by-bit AWS, GCP, and Azure make it difficult to leave.

!rant

Anyone here experienced with Route53?

I have a small issue I'm trying to think through on how to achieve with minimum effort and maintenance, essentially set once and walk away and never care about it again solution.

Basically what I have is:

sub.domain.com

and I need to get it to redirect over to

otherdomain.com/folderToGetTo/

Using a 301 would be ideal but how for the life of me do I go about serving a 301 redirect over a dns entry - short answer is I can't unless I'm missing something!

Both domains are owned by the same company so no issue in hijacking a subdomain... well besides internal politics but that's just another day 😏

First thoughts include setting up a S3 bucket with hosting and forcing the dns to that and then, redirect out of the bucket... seems overkill but will work.

Hoping to find a smaller solution that I don't have to justify a S3 bucket being used for a single file - audits suck alright🤷‍♂️

Oh and setting up a redirect at the originating domain will take longer then it's worth to setup and get approvals for so not worth the effort internally.

Yes I will accept "fuck off @C0D4" as an answer.

<3 Route53 DNS today.

So I have purchased the domain studioentropy.com. It's taken me all afternoon but I've set up and configured aws s3 buckets and route 53 zone an entries and my shite asse site is now online, hooray... My question is with regards to https. Given that ny site is really only going to be a single page site with relatively static content, no eccomerce of any kind, no passing of sensative information is required, is it really worth going through the pain of configuring cloudfront so the site uses https instead of http?

Do you know Route53 can be used as a DB?

Im trying to attach my ECS Fargate Load Balancer to route53 but the domain is dead.

LB dns name works perfectly fine. Its healthy. Backend is deployed and working fine through ecs fargate

But for some reason my domain doesnt work.

- attached the LB as an A record
- Alias to application and classic load balancer
- region correct
- chose a dualstack... Load balancer

Domain cant open

This site can't be reached
api.domain.com's DNS address could not be found. Diagnosing the problem.
DNS_PROBE_POSSIBLE

There are literally 0 fucking error logs in my ecs, task definition, load balancer target groups security groups vpc etcc.

What the fuck is the problem please how do i fix this?

Why is cloudformation the way it is?

My stacks take over 10 minutes to execute, only for it to fail because of a small misconfiguration.

Why does it take 10 minutes to create a route53 record set through cloudformation, but takes less than a second to create through the web console? That is pathetic.

The people working on cloudformation should be absolutely ashamed of themselves.