启动Amazon Aurora遇问题：访问Performance Insights被拒 - InvalidParameterCombination

Hey there, let's tackle this frustrating issue you're having with launching Amazon Aurora. That InvalidParameterCombination error tied to Performance Insights usually boils down to permission misconfigurations or unsupported settings—here's a step-by-step breakdown to get you sorted:

1. Double-Check Your IAM Permissions #

The "Access Denied" part is a big clue here. Make sure the IAM user/role you're using to create the Aurora cluster has these critical permissions (add them via an IAM policy if missing):

• rds:CreateDBCluster (the base permission to create Aurora clusters)
• pi:EnablePerformanceInsights (allows enabling Performance Insights for the cluster)
• pi:GetResourceMetrics (grants access to PI's monitoring data)
  Also, watch out for any Deny policies attached to your identity—these override Allow permissions, so even if you have the above allows, a Deny can block the action.

2. Confirm Performance Insights Supports Your Aurora Setup #

Not all Aurora configurations work with Performance Insights. Verify these details:

• Engine Version:
  • Aurora MySQL: Needs v5.6.10a+, v5.7.mysql_aurora.2.03.2+, or Aurora MySQL 8.0+
  • Aurora PostgreSQL: Needs v10.7+
• Instance Type: PI supports most modern instance families like db.r4, db.r5, db.m5, db.t3—older or specialized types (like db.t2.micro in some cases) might not be compatible.

3. Test by Disabling Performance Insights Temporarily #

A quick way to isolate the issue is to create the cluster without enabling Performance Insights first:

• When launching the Aurora cluster, go to the Monitoring section
• Toggle "Enable Performance Insights" to No
  If the cluster launches successfully, you know the problem is specifically tied to PI. You can then go back and re-enable PI once you've fixed the underlying issue.

4. Check Region and Service Quotas #

• Region Availability: While rare, some AWS regions (like certain GovCloud or edge regions) might have limited PI support. Confirm your target region supports Performance Insights for Aurora.
• PI Quotas: If your account has hit the maximum number of PI-monitored resources in the region, you'll get this error. Head to the Service Quotas console, search for "Performance Insights", and check if you need to request a quota increase.

Once you've worked through these steps, you should be able to launch your Aurora cluster with (or without, if you choose) Performance Insights enabled.

内容的提问来源于stack exchange，提问作者Peps