Yes, you read that right there’s even more to Aurora. First off you’ve got custom endpoints, as I mentioned in my last post you have your write endpoint and your read endpoint well you can set a custom endpoint and add your Aurora instances to it, this is useful if you perhaps have a set of more powerful databases you send your more complicated queries to. Next up is Aurora multi-master, this allows you to have more than one master instance rather than just one, multiple read/write across AZ, much quicker failover than if your primary master fails and you need to wait for a read replica to get promoted to master instance. Now we have Aurora server-less, this service autoscales based on usage and usage alone, no need to provision capacity ahead of time, you simply connect to proxy fleet and that service will scales Aurora instances up and down based on usage. Regional Aurora, you can set up Aurora in multiple regions for failover purposes. Regional Aurora can be even more in depth you can have Aurora Global Database setup. With this service you have one read/write region and up to 5 secondary read regions. The replication is under a second cross-region. You can have up to 16 read replicas per secondary region. If you have a DB service you need to offer across the world this can decrease latency significantly if you utilized Auroral Global Database. You can even connect Aurora to machine learning offerings to analyze queries, services such as SageMaker and Comprehend.