mirror of
https://github.com/fleetdm/fleet
synced 2026-04-21 13:37:30 +00:00
<!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #40054 # Checklist for submitter - [ ] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. - Already present in 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** * Migrated logging to a structured, context-aware backend for clearer, richer diagnostics and consistent log formatting. * Introduced broader context propagation and adjusted internal interfaces to support the new logging approach (no end-user behavior changes). <!-- end of auto-generated comment: release notes by coderabbit.ai --> |
||
|---|---|---|
| .. | ||
| cf-template.yaml | ||
| cleanup-test-env.sh | ||
| deploy-test-env.sh | ||
| iam_auth.go | ||
| README.md | ||
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.