Victor Lyuboslavsky
abaeeec6b8
<!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #38889 This is preparatory work before incrementally converting datastore/mysql files to directly use *slog.Logger. This will be done by using `logger.SlogLogger()` to get the underlying `*slog.Logger` # Checklist for submitter - [ ] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. - Changes file already exists from previous PR ## Testing - [x] Added/updated automated tests - [x] QA'd all new/changed functionality manually <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Updated internal logging infrastructure to use a standardized platform logging package across database and utility components. This consolidates logging dependencies and improves system consistency without affecting user-facing functionality. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
RDS IAM Authentication Test Tools
This directory contains test tools for validating Fleet's AWS RDS IAM authentication implementation.
Prerequisites
- AWS CLI configured with appropriate credentials (via
AWS_PROFILEorAWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEY)
Usage
Deploy Test Environment
# Set AWS credentials and region
export AWS_PROFILE=your-profile # or use AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY
export AWS_REGION=us-east-2
./deploy-test-env.sh
This will:
- Create all RDS instances with IAM authentication enabled
- Create an EC2 instance with necessary IAM permissions
- Create database users for IAM authentication
- Output connection information
Clean Up
./cleanup-test-env.sh
This will destroy the AWS resources.