Skip to content

MySQL IAM authentication fails when custom CAs are specified in config #39832

@kc9wwh

Description

@kc9wwh

Fleet version: 4.78.3
Web browser and operating system: N/A (Server-side issue)


💥 Actual behavior

When specifying custom Certificate Authorities (CAs) via the Fleet config, MySQL IAM authentication is effectively disabled, causing database connections to fail. This issue particularly affects customers in AWS GovCloud environments where the included RDS auth certificate chain doesn't work, requiring custom CAs to be specified.

The custom CA configuration overrides the IAM auth settings, preventing successful authentication to RDS instances that have IAM auth enabled.

🧑‍💻 Steps to reproduce

  1. Configure Fleet to connect to an AWS RDS MySQL database in GovCloud (or any environment requiring custom CAs)
  2. Enable MySQL IAM authentication on the RDS instance
  3. Specify custom CAs in the Fleet configuration to accommodate GovCloud requirements
  4. Attempt to connect Fleet to the database
  5. Observe that the connection fails due to IAM auth being disabled when custom CAs are provided

🕯️ More info (optional)

Metadata

Metadata

Assignees

Labels

#g-orchestrationOrchestration product group:releaseReady to write code. Scheduled in a release. See "Making changes" in handbook.P2Urgent: Supported workflow not functioning as intended, newly drafted feature with urgent Fleet needbugSomething isn't working as documentedcustomer-leolo~activation-blockerBlocks a customer activation~released bugThis bug was found in a stable release.

Type

No type

Projects

Status

Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions