AWS Aurora PostgreSQL

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¶

It is recommended to activate the Guance integration - extension - managed Func: all prerequisites are automatically installed. Please continue with the script installation.

If you deploy Func on your own, refer to Self-deployed 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)

Managed Version Activation Script¶

1. Log in to Guance console
2. Click the 【Integration】 menu, select 【Cloud Account Management】
3. Click 【Add Cloud Account】, choose 【AWS】, fill in the required information on the interface. If you have already configured cloud account information before, skip this step.
4. Click 【Test】, if the test is successful, 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 the corresponding cloud account to enter the details page.
6. Click the 【Integration】 button on the cloud account details page. Under the Not Installed list, find AWS Aurora PostgreSQL, click the 【Install】 button, and install it via the pop-up installation interface.

Manual Activation Script¶

1. Log in to the Func console, click 【Script Market】, go to the official script market, search for guance_aws_aurora_postgresql
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 automatically configure the corresponding startup scripts.
4. After activation, you can see the corresponding automatic trigger configuration in the 「Management / Automatic Trigger Configuration」. Click 【Execute】 to run immediately without waiting for the scheduled time. After a while, 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. You can also check the corresponding task records and logs to see if there are any abnormalities.
2. In Guance, under 「Infrastructure - Resource Catalog」, check if there is any asset information.
3. In Guance, under 「Metrics」, check if there is any corresponding monitoring data.

Metrics¶

Configure Amazon-CloudWatch by configuring more metrics Amazon CloudWatch 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 specified, the following instance-specific Amazon CloudWatch metrics apply to all Aurora MySQL and Aurora PostgreSQL instances.

Objects¶

The collected AWS Aurora PostgreSQL object data structure can be seen in the 「Infrastructure - Resource Catalog」

{
  "measurement": "aws_rds",
  "tags": {
    "name"                     : "xxxxx",
    "RegionId"                 : "cn-northwest-1",
    "Engine"                   : "aurora-postgresql",
    "DBInstanceClass"          : "db.t3.medium",
    "DBInstanceIdentifier"     : "xxxxxx",
    "AvailabilityZone"         : "cn-northwest-1c",
    "SecondaryAvailabilityZone": "ap-southeast-1c"
  },
  "fields": {
    "InstanceCreateTime"  : "2025-05-19T19:54:07.871Z",
    "LatestRestorableTime": "2025-05-19T19:54:07.871Z",
    "Endpoint"            : "{connection address JSON data}",
    "AllocatedStorage"    : 100,
    "message"             : "{instance JSON data}",
  }
}

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

Tip 1: The value of tags.name is the instance ID, used for unique identification

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