very well explained and also with lab. Anyone can understand easily. Route 53 role is a good and it is a good idea easily we can change the cname record.
9:45 Why is it not possible to handle the automatic region failover through a single endpoint when it comes to global databases? For example, in case of a failover to a read replica the application does not need to change the cluster endpoint in order to point to the new writer instance. Was this capability not possible to implement in case of global databases?
It's not possible as part of the managed service today. However, there is a custom solution you can implement, see below. aws.amazon.com/blogs/database/automate-amazon-aurora-global-database-endpoint-management/
very well explained and also with lab. Anyone can understand easily. Route 53 role is a good and it is a good idea easily we can change the cname record.
Very well explained. Thanks for the lab as well. Not many videos have it.
Thanks for this. The route 53 workaround is a good idea
Great explanation. Thank you!
9:45 Why is it not possible to handle the automatic region failover through a single endpoint when it comes to global databases?
For example, in case of a failover to a read replica the application does not need to change the cluster endpoint in order to point to the new writer instance. Was this capability not possible to implement in case of global databases?
It's not possible as part of the managed service today. However, there is a custom solution you can implement, see below.
aws.amazon.com/blogs/database/automate-amazon-aurora-global-database-endpoint-management/
AWS being lazy
I am getting DatabaseUnavailableException in query Editor of secondary rds while trying to fetch the data. Is there any solution for it?