v2.1.1

What's Changed

2.1.1

Patch Changes

• afb1388: The mysql proxy will now return an error to the client when it cannot connect to the target database.

Full Changelog: v2.1.0...v2.1.1

v2.1.0

What's Changed

2.1.0

Minor Changes

• a2d5af3: Added support for Audited EKS Cluster Access

Patch Changes

• a2d5af3: Replace error level of some logs with info logging to minimise noise levels
• 15f7c34: allow proxy task role to assume roles with a specific tag

Full Changelog: v2.0.6...v2.1.0

v2.0.6

What's Changed

2.0.6

Patch Changes

• caa4106: Only validate the database and role that the user is trying to connect to, rather than every single database and role.

Full Changelog: v2.0.5...v2.0.6

v2.0.5

What's Changed

2.0.5

Patch Changes

• 7159fcb: Relax common-fate/commonfate provider version constraint to ">= 2.25.3, < 3.0.0"

Full Changelog: v2.0.4...v2.0.5

v2.0.4

What's Changed

2.0.4

Patch Changes

• c540cf6: Fix version constraint for the Common Fate Terraform provider to allow minor version updates.

Full Changelog: v2.0.3...v2.0.4

v2.0.3

What's Changed

2.0.3

Patch Changes

• 31d9f46: Added the ability to specify an override for the rds endpoint per rds user to allow read roles to use a read only replica endpoint.

Full Changelog: v2.0.2...v2.0.3

v2.0.2

What's Changed

2.0.2

Patch Changes

• 1f03dcc: Fixes an issue where the mysql proxy would not report the correct server version, causing some clients to fail to connect due to using unsupported features. The proxy now correctly reports the version and charset of the target server.

Full Changelog: v2.0.1...v2.0.2

v2.0.1

What's Changed

2.0.1

Patch Changes

• 3b7fb60: Add "aurora-postgresql" and "aurora-mysql" as supported database engines.

Full Changelog: v2.0.0...v2.0.1

v2.0.0

What's Changed

2.0.0

Major Changes

• 4bcafbc: This new major version of the proxy seperates databases from the proxy infrastructure configuration.

Full Changelog: v1.4.1...v2.0.0

v1.4.1

What's Changed

1.4.1

Patch Changes

• 8156834: Fixes an issue where the Postgres proxy would not return an error to the database client when it tried to connect to an database or user that does not match the grant for the session. The previous behaviour was for the connection to be accepted however the underlying connection to the target database matched the grant but not what the user was expecting. The Proxy now correctly rejects the connection attempt and states clearly that the client can only connect to the target database and user on the grant for the session.
• 8156834: Fix version number not being included in container logs.

Full Changelog: v1.4.0...v1.4.1