Skip to main content

What is this integration?

Amazon RDS makes it easy to set up, operate, and scale relational databases in the cloud.

What Monk manages

  • DB instance, subnet group, security group

What the Agent can do and how to use it

  • Database Creation: Provision MySQL, PostgreSQL, MariaDB, Oracle, and SQL Server instances
  • Backup & Recovery: Configure automated backups, point-in-time recovery, and manual snapshots
  • Scaling: Modify instance types, storage, and enable read replicas for scaling
  • High Availability: Set up Multi-AZ deployments for automatic failover
  • Security: Configure VPC isolation, security groups, and encryption at rest
  • Maintenance: Schedule and manage automated maintenance windows
  • Monitoring: Enable Enhanced Monitoring and Performance Insights
  • Parameter Groups: Customize database engine parameters and configurations
Steps:
  1. Ensure AWS provider is added: monk cluster provider add -p aws
  2. monk update <namespace>/<name>

Obtaining AWS Credentials

AWS RDS uses your AWS account credentials. You’ll need AWS access keys with appropriate permissions.

What You’ll Need

  • AWS Access Key ID
  • AWS Secret Access Key
  • Optional: Default region (e.g., us-east-1)

Step-by-Step

  1. Log into AWS Console at https://console.aws.amazon.com
  2. Navigate to IAMUsers
  3. Select your IAM user or Create user for Monk
  4. Go to Security credentials tab
  5. Click Create access key
  6. Choose use case: “Third-party service”
  7. Click NextCreate access key
  8. Copy Access Key ID and Secret Access Key
  9. Save them securely - secret key shown only once

Required IAM Permissions

Attach these AWS managed policies to the user:
  • AmazonRDSFullAccess - For RDS management
  • AmazonEC2FullAccess - For VPC and security groups
  • IAMReadOnlyAccess - For verification
Or create a custom policy with: RDS, EC2 (VPC, security groups), and IAM read access.

Providing to Monk

When deploying with AWS RDS, ask Monk:
Monk will request AWS credentials if not already configured.

Security Best Practices

Use IAM user for Monk - Not your personal admin account ✅ Enable MFA on the account managing the IAM user ✅ Rotate keys every 90 daysMonitor with CloudTrail - Track API usage ✅ Use minimal permissions - Only grant what Monk needs

Auth

  • Uses AWS provider credentials (Access Key ID and Secret Access Key)

Getting Started

  1. Provide AWS credentials to Monk when deploying:

CLI Reference (Advanced)

For manual provider configuration:
  1. Define an RDS instance (save as rds.yaml):
  1. Create/update:

Backup & Snapshot Actions