AWS Aurora MySQL

Use the script package series of 「Guance Cloud Sync」in the script market to synchronize cloud monitoring and cloud asset data to Guance

Configuration¶

Install Func¶

Recommended activation Guance Integration - Extension - Hosted Func: all prerequisites are automatically installed, please continue with script installation

If you deploy Func by yourself, refer to Self-deploy Func

Install Script¶

Note: Please prepare an Amazon AK that meets the requirements in advance (for simplicity, you can directly grant global read-only permission ReadOnlyAccess)

Hosted Edition Activation Script¶

1. Log in to Guance Console
2. Click on the 【Integration】 menu, select 【Cloud Account Management】
3. Click 【Add Cloud Account】, select 【AWS】, fill in the required information on the interface; if cloud account information has been configured before, skip this step
4. Click 【Test】, after a successful test click 【Save】, if the test fails, check whether the relevant configuration information is correct and retest
5. In the 【Cloud Account Management】 list, you can see the added cloud accounts, click on the corresponding cloud account, enter the details page
6. Click the 【Integration】 button on the cloud account details page, under the Not Installed list, find AWS Aurora MySQL, click the 【Install】 button, the installation interface will pop up for installation.

Manual Activation Script¶

1. Log in to the Func Console, click 【Script Market】, enter the official script market, search:guance_aws_aurora_mysql

2. After clicking 【Install】, input the corresponding parameters: AWS AK ID, AK Secret, and account name.

3. Click 【Deploy Startup Script】, the system will automatically create a Startup script set and configure the corresponding startup script automatically.

4. After enabling, you can see the corresponding automatic trigger configuration in "Management / Automatic Trigger Configuration". Click 【Execute】 to immediately execute once without waiting for the scheduled time. Wait a moment, and you can view the execution task records and corresponding logs.

Verification¶

1. Confirm in "Management / Automatic Trigger Configuration" whether the corresponding tasks have the corresponding automatic trigger configurations, and at the same time, check the corresponding task records and logs for any abnormalities.
2. In Guance, "Infrastructure - Resource Catalog", check if there is asset information.
3. In Guance, "Metrics" check if there is corresponding monitoring data.

Metrics¶

Configure Amazon-Cloud Monitoring, more metrics can be collected through configuration Amazon Cloud Monitoring Metrics Details

Amazon RDS Amazon CloudWatch Metrics¶

The AWS/RDS namespace includes the following metrics, which apply to database entities running on Amazon Aurora. Some metrics apply to Aurora MySQL and/or Aurora PostgreSQL. Additionally, some metrics are specific to database clusters, primary database instances, replica database instances, or all database instances.

Amazon Aurora Cluster-Level Metrics¶

Amazon Aurora Instance-Level Metrics¶

Unless otherwise stated, the following instance-specific Amazon CloudWatch metrics apply to all Aurora MySQL and Aurora PostgreSQL instances.

Objects¶

Collected AWS Aurora MySQL object data structure, visible from "Infrastructure - Resource Catalog"

{
  "measurement": "aws_rds",
  "tags": {
    "name"                     : "xxxxx",
    "RegionId"                 : "cn-northwest-1",
    "Engine"                   : "aurora-mysql",
    "DBInstanceClass"          : "db.t3.medium",
    "DBInstanceIdentifier"     : "xxxxxx",
    "AvailabilityZone"         : "ap-southeast-1b",
    "SecondaryAvailabilityZone": "ap-southeast-1c"
  },
  "fields": {
    "InstanceCreateTime"  : "2025/05/26 22:45:02",
    "LatestRestorableTime": "2025/05/26 22:15:26",
    "Endpoint"            : "{JSON serialized connection address}",
    "AllocatedStorage"    : 1,
    "message"             : "{JSON serialized instance data}",
  }
}

Note: Fields in tags and fields may vary with subsequent updates

Tip 1: The value of tags.name is the instance ID, serving as a unique identifier

Tip 2: fields.message and fields.Endpoint are strings serialized in JSON format