AWS AmazonRDS documentation change
Summary
Updated documentation wording and corrected whitepaper reference link format
Security assessment
Changes involve phrasing improvements and link formatting updates without addressing security vulnerabilities or introducing security features.
Diff
diff --git a/AmazonRDS/latest/AuroraUserGuide/aurora-global-database-connecting.md b/AmazonRDS/latest/AuroraUserGuide/aurora-global-database-connecting.md index d7e3c090c..66ac382fe 100644 --- a//AmazonRDS/latest/AuroraUserGuide/aurora-global-database-connecting.md +++ b//AmazonRDS/latest/AuroraUserGuide/aurora-global-database-connecting.md @@ -26 +26 @@ Connecting to an Aurora Global Database depends on your need to read or write fr - * **Routing requests to the writer instance** : If you need to run data manipulation language (DML) and data definition language (DDL) statements, or need strong consistency between reads and writes, connect to the Aurora Global Database writer endpoint. That endpoint routes requests to the writer instance in your global database's primary cluster. This endpoint is automatically updated to route requests to the writer instance, eliminating the need to update your application each time you change the writer location in your global cluster. You can also use the global endpoint to send cross-Region read/write requests to your writer. + * **Routing requests to the writer instance** : Connect to the Aurora Global Database writer endpoint if you need to run data manipulation language (DML) and data definition language (DDL) statements, or if you need strong consistency between reads and writes. That endpoint routes requests to the writer instance in your global database's primary cluster. This endpoint is automatically updated to route requests to the writer instance, eliminating the need to update your application each time you change the writer location in your global cluster. You can also use the global endpoint to send cross-Region read/write requests to your writer. @@ -161 +161 @@ You can make effective use of the Aurora Global Database writer endpoints by fol - * The global writer endpoint update after a global database failover or switchover can take a long time depending upon your Domain Name Service (DNS) caching duration. See [DNS caching](https://docs.aws.amazon.com/whitepapers/latest/amazon-aurora-mysql-db-admin-handbook/dns-caching.html) to learn more. Aurora Global Database emits an RDS Event when it sees the DNS change on the global writer endpoint. You can use the event to devise strategies to ensure the DNS cache doesn't extend beyond the time after the event is generated. For more information, see [DB cluster events](./USER_Events.Messages.html#USER_Events.Messages.cluster). + * The global writer endpoint update after a global database failover or switchover can take a long time depending upon your Domain Name Service (DNS) caching duration. See [ Amazon Aurora MySQL Database Administrator's Handbook](https://docs.aws.amazon.com/pdfs/whitepapers/latest/amazon-aurora-mysql-db-admin-handbook/amazon-aurora-mysql-db-admin-handbook.pdf) to learn more. Aurora Global Database emits an RDS Event when it sees the DNS change on the global writer endpoint. You can use the event to devise strategies to ensure the DNS cache doesn't extend beyond the time after the event is generated. For more information, see [DB cluster events](./USER_Events.Messages.html#USER_Events.Messages.cluster).