What problem does it solve? Running IBM Db2 on Amazon RDS involves managed-service constraints (no host access, no unfenced C/COBOL procedures, Secrets Manager password rotation) and complex workflows like IBM BYOL licensing, z/OS mainframe migration, TLS connectivity, and cross-region DR that are easy to get wrong without deep, scattered documentation. ## Core Features & Use Cases - Provisioning & Licensing: Create RDS for Db2 instances with IBM customer/site IDs, BYOL parameter groups, customer-managed KMS keys (BYOK), and GovCloud support. - Migration: Move from Db2 LUW (Linux, AIX, Windows, AS400) or z/OS mainframe using ADB2GEN schema conversion, Q Replication, DMS full load, and S3 backup/restore with rollforward. - Operations & Security: Configure TLS connectivity, Multi-AZ and cross-region standby replicas, self-managed Active Directory Kerberos, Db2 audit to S3, least-privilege IAM, and RDSADMIN stored procedures. - Use Case: A team migrating a Db2 for z/OS mainframe workload gets routed guidance on ADB2GEN (not SCT), EBCDIC-to-UTF-8 code page planning, and near-zero-downtime cutover via Q Replication. ## Quick Start Ask the assistant to provision an encrypted Amazon RDS for Db2 instance with BYOL licensing and connect to it over TLS from an EC2 client.