Amazon RDS
Include the selected RDS cluster or database instance in the context for a deployment review.
Identify the database resource
Proofline uses read-only RDS control-plane APIs, scoped to the configured account, region, and cluster or instance. When an instance reports Aurora cluster membership, the evidence retains the cluster identifier.
For Aurora, the membership record lets a review identify the cluster an instance belongs to. The account and region keep that resource distinct from similarly named databases elsewhere.
Keep database conclusions grounded
When reviewing a migration or a change to connection handling, start by identifying the instance or cluster the application targets. Its control-plane record establishes that resource context.
The connector receives no SQL credentials and does not inspect tables or application data. Questions about query behavior, lock contention, or existing rows need evidence beyond this connection.
Connect your AWS account
Choose the AWS account and region for the environment under review. Apply the connection’s scoped read-only role, verify access, and check the environment’s evidence coverage.
Get started with GitHub