Feature/postgres mcp kiro integration

[kennthhz]

Fixes

Summary

This is a new feature commitment to AWS CEO in AI area, and the release date is Dec 15. The test code is still being written but dev code is ready for early review in PR.

Aurora Power is our integration package that seamlessly connects Aurora Postgres with Kiro, including a curated set of steering files and a local Aurora Postgres MCP server. Once installed, developers can build applications using Aurora Postgres as their underlying storage in any programming language, without writing a single line of SQL or touching the RDS console. With just an AWS account, Kiro handles all infrastructure setup through the MCP server, including provisioning the Aurora Postgres cluster, creating databases, and generating tables. The package provides intelligent guidance for database schema design, table structures, and index optimization, incorporating built-in best practices. All interactions and infrastructure provisioning happen seamlessly within the Kiro environment through natural conversation, making database-backed application development intuitive and efficient.

Changes

• Support creating regular cluster and cluster with express configuration. Cluster with expression configuration is a new Aurora feature that allows creation to be done under 30 seconds. This is the key feature for Kiro integration as vibe coder needs to quickly create Aurora database cluster.
• Support dynamic connection to multiple Aurora Postgres endpoints and MCP can switch connections with tool calls from LLM. Internally, MCP tools caches endpoint authentication credentials and keys to map them.
• Support IAM authentication MCP. This is needed to connect to cluster with expression configuration

User experience

You use following LLM prompts to interact with MCP:

• create a new Aurora Postgres cluster in region us-west-2 named TestCluster with database name postgres
• create a new Aurora Postgres cluster in region us-west-2 named TestCluster2 with express configuration with database name postgres
• connect to database postgres in TestCluster

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• I have reviewed the contributing guidelines
• I have performed a self-review of this change
• Changes have been tested
• Changes are documented

Is this a breaking change? (Y/N)

RFC issue number:

Checklist:

• Migration process documented
• Implement warnings (if it can live side by side)

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.64%. Comparing base (083cfeb) to head (29e86f8).
⚠️ Report is 5 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1863      +/-   ##
==========================================
+ Coverage   90.42%   90.64%   +0.21%     
==========================================
  Files         851      843       -8     
  Lines       63317    62935     -382     
  Branches    10253    10197      -56     
==========================================
- Hits        57254    57047     -207     
+ Misses       3772     3606     -166     
+ Partials     2291     2282       -9     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.