Making your Amazon Aurora database (DB) uniformly accessible by following certain recommendations is considered one of the best practices to ensure that your infrastructure is fault tolerant.
What is Amazon Aurora?
Aurora is the relational database service which is available as a part of AWS RDS (Relational Database Service). It does not require the user to provide database storage and can automatically allocate database storage in the increments of 10 GB. The storage can go up to a maximum capacity of 64 TB. Aurora is more beneficial than RDS database engines as it also provides comprehensive performance metrics such as latency, query throughput, etc.
Accessibility of your Aurora database instances should be uniform
It is important to ensure that the accessibility of your Amazon Aurora database instances within the cluster should be uniform throughout the infrastructure. If one of your Aurora database instances has public accessibility, then every Aurora instance in your cloud infrastructure should have public accessibility as well.
Or if any one of them has private accessibility, then it should be the same for the rest of the instances. This is because, in case of failover, an instance might go from having public access to private access which can disrupt the connectivity of your database cluster.
Centilytics provides a dedicated insight for Amazon Aurora database cluster accessibility and warns you if the database instance is not publicly accessible. Though it is usually the case that your resources should not be publicly accessible to avoid security breaches but uniform accessibility is important to cope up from sudden outages.
Insight Descriptions:
There can be two possible scenarios:
| Severity | Description |
 OK |
This indication will be displayed when the Aurora database instance is publicly accessible. |
 WARNING |
This indication will be displayed when the Aurora database instance is not publicly accessible. |
Description of further columns are as follows:
- Account Id: This column shows the respective account ID of the user.
- Account Name: This column shows the corresponding account name.
- Region: This column shows the region in which the resource exists.
- Database (DB) instance identifier: This column shows the name of your Aurora database instance.
- DB name: This column shows the name of your Aurora database.
- Instance class of DB: This column shows the instance class of your database instance.
- Identifier: This column shows the unique ARN (Amazon Resource Number) of your Aurora database instance.
Filters Applicable:
| Filter Name | Description |
| Account Id | Applying the account Id filter will display data for the selected account Id. |
| Region | Applying the region filter will display data corresponding to the selected region |
| Severity | Applying severity filter will display public snapshots according to the selected severity type i.e. selecting critical will display all resources with critical severity. Same will be the case for Warning and Ok severity types. |
| Resource Tags | Applying resource tags filter will display those resources which have been assigned the selected resource tag. For e.g., A user has tagged some public snapshots by a resource tag named environment. Then selecting an environment from the resource tags filter will display all those resources tagged by the tag name environment. |
| Resource Tags Value | Applying resource tags value filter will display data which will have the selected resource tag value. For e.g. – Let’s say a user has tagged some resource by a tag named environment and has a value say production (environment: production).
Hence, the user can view data of all the resources which have “environment:production” tag assigned. The user can use the tag value filter only when a tag name has been provided. |