Amazon Route 53

Announcing blockchain snapshots on, oh, shut up.

Amazon Route 53 now supports registrations, transfers, and renewals for premium domains.

Your database is about to get some fancy new options for table names.

Amazon TimeSync service adds support for microsecond accurate time on 153 additional EC2 instance types in all commercial regions.

So what would happen is that someone would spin up an account, they would go ahead and create a zone.

They would create a public registrar with, say, AWS, uh, Route 53, and voila.

You know, they would, you know, they would go on with this now, right? Like-

Yeah

Yeah.

But here's something that we missed.

You know, the Route 53 records associated with those destinations still pointed to accounts that we own.

Oh.

It does.

It even reaches out to Route 53 to dynamically update your DNS records so traffic flows to the newly created load balancers.

That level of automation is incredible.

But looking at the text, there is an architectural decision here that feels counterintuitive to me.

And frankly, in modern microservice architectures, the applications themselves don't rely on static IP addresses either because containers are constantly spinning up, crashing, and being replaced with new IPs.

We need a dynamic phone book.

Which brings us to the traffic cops of the cloud, DNS and Route 53.

Route 53 is Amazon's highly available DNS web service, but the text makes a point to emphasize that Route 53 is not just for registering public web domains like mycoolstartup.com.

Aurora Postgresquille now supports direct querying of Apache, Iceberg, and Parquet data in your data lake.

This is DuckDB support being integrated into Aurora Postgresquille and the great unwashed hordes of database folks who have yet to discover the one true database, Route 53.

Announcing the AWS Well-Architected Agent, which is an AI-powered intelligence to optimize your cloud environment in preview, which means they don't know what it's going to cost yet, evaluates your environment as an experienced cloud architect would, is now being offered through the magic of AI to accounts that can't get a solutions architect on the phone.

If this thing works, what are 5,000 undifferentiated AWS partners left to do? Introducing filtered export from DynamoDB to S3.

A network load balancer with TCP listeners.

Option B, route 53 weighted routing.

Option C, path-based routing on an application load balancer.

And option D, a NAT gateway.

A network load balancer with TCP listeners operate at layer 4 and doesn't understand HTTP paths, so it can't do path-based routing.

Option B.

Route 53 weighted routing splits traffic by assigned weights at the DNS level.

It distributes by proportion, not by URL path, so it can't send specific paths to specific targets.

This audio is presented by Hacker Noon, where anyone can learn anything about any technology.

Configuring Route 53, Subdomain Delegation with Terraform, by Lucas Tonelli.

DNS is one of those things that works so well in the background that nobody thinks about it until someone accidentally deletes in a record 5 minutes before a demo.

As infrastructure grows and more environments show up, dumping every record for every environment into one giant Hasik's zone starts to feel a lot like that moment, just waiting to happen.

Since a separate zones usually means separate state, changes to one environment don't require locking or touching the state of another.

And when something does go wrong, the change history for a single small zone is a lot easier to reason about than digging through a zone with hundreds of unrelated records.

Delegating a zone with Route 53.

Delegation itself is done through NS records.