For high availability, Multi-AZ deployments are recommended. All engine types support the ability to distribute data across two (or, in the case of Aurora, more) availability zones. This feature enables our database to survive any failures in one particular availability zone. The Multi-AZ feature allows us to access the database via a DNS name that automatically fails over to the secondary instance in case the primary fails. It also allows for ease of management as backend management functions do not affect the availability of the database.