• Aurora involves a cluster of DB instances instead of a single instance.
  • Each connection is managed by a specific DB instance.
  • During connection to Aurora, host name and port point to endpoint.
  • endpoint mechanism abstracts these connections.
  • Hence, no need to hardcode hostnames or logic for load-balancing and rerouting connections if DB instances aren’t available.
  • With endpoints, map each connection to appropriate instance or group of instances based on use case.
  • endpoint is represented as an Aurora-specific URL having
    • a host address
    • a port.
  • Aurora Endpoints Types
    • Cluster endpoint – connects to the current primary DB instance for that DB cluster. Each Aurora DB cluster has one cluster endpoint and one primary DB instance.
    • Reader endpoint – connects to one of the available Aurora Replicas for that DB cluster. Each Aurora DB cluster has one reader endpoint.
    • Custom endpoint – It represents a set of DB instances that you choose. After connecting, Aurora performs load balancing.
    • Instance endpoint – connects to a specific DB instance within an Aurora cluster.
Menu