Comment by Twirrim

That's actually a pretty long TTL by Amazon standards.

Amazon.com:

    ;; ANSWER SECTION:
    amazon.com.             60      IN      A       176.32.103.205
    amazon.com.             60      IN      A       176.32.98.166
    amazon.com.             60      IN      A       205.251.242.103

Or some AWS services

Glacier:

    ;; ANSWER SECTION:
    glacier.us-east-1.amazonaws.com. 60 IN  A       54.239.30.220

S3 has even shorter:

    ;; ANSWER SECTION:
    s3.ap-northeast-1.amazonaws.com. 5 IN   A       52.219.0.8

Or, say, DynamoDB:

    ;; ANSWER SECTION:
    dynamodb.us-east-1.amazonaws.com. 5 IN  A       52.94.2.72

The main reason to do so is to be nimble, it's to be able to react to incidents as fast as you can and change, and to make potential deployment patterns possible.

From time to time, you need to do something with customer facing infrastructure: Remove the DNS entry, watch the traffic drain over the next 5-10 minutes, and then do what you need to do on the device, test, and then add it back in the DNS again, from which you can watch traffic return to normal levels and verify everything is good.