Route 53 – Records TTL (Time To Live)

High TTL (e.g., 24 hours)

• Reduces DNS query volume to Route 53.

• Risk of serving outdated IPs if the target changes.

• Best for stable, rarely changing resources.

Low TTL (e.g., 60 seconds)

• Increases DNS query volume (and potentially cost).

• Records update quickly for clients.

• Best for frequently changing resources or planned migrations.

Notes

• TTL is required for all DNS records except Alias records.

• Clients cache DNS results for the TTL duration.

• Short TTL → flexibility, Long TTL → efficiency.