AWS Config
Collect configuration item counts, export failures, notification failures, and insufficient permission metrics from the AWS/Config namespace.
Configuration¶
Install Func¶
We recommend enabling Guance Integrations - Extensions - Hosted Func: all prerequisites are installed automatically. Continue with script installation.
To deploy Func yourself, see Self-hosted Func.
Enable the Script¶
Tip: Prepare suitable AWS access keys in advance (for simplicity, you can grant the global read-only permission
ReadOnlyAccess).
Activate Script in DataFlux Func (Automata)¶
- Log in to the Guance console
- Click the 【Integration】 menu and select 【Cloud Account Management】
- Click 【Add Cloud Account】, select 【AWS】, and fill in the required information on the interface. If you have already configured the cloud account information before, ignore this step
- Click 【Test】, and if the test is successful, click 【Save】. If the test fails, please check if the relevant configuration information is correct and test again
- Click 【Cloud Account Management】, and you can see the added cloud account in the list. Click the corresponding cloud account to enter the details page
- Click the 【Integration】 button on the cloud account details page, find
AWS Configunder theNot Installedlist, click the 【Install】 button, and the installation interface will pop up for installation.
Activate Script Manually¶
- Log in to the Func console, click [Script Market] to open the Guance script market, and search for
integration_aws_config. - Click [Install], then enter the required parameters: AWS AK ID, AK Secret, and account name.
- Click [Deploy Startup Script]. The system automatically creates the
Startupscript set and configures the corresponding startup script. - Once enabled, the corresponding automatic trigger configuration appears under [Management / Automatic Trigger Configuration]. Click [Execute] to run it immediately without waiting for the scheduled time. After a short wait, check the task execution records and logs.
Verification¶
- Confirm that the task is configured under Management / Automatic Trigger Configuration. Check task records and logs for permission or API errors.
- In Guance Metrics, check the
aws_configmeasurement to confirm the monitoring data.
Metrics¶
The measurement is aws_config.
| MetricName | MetricDescribe | Dimensions | Unit |
|---|---|---|---|
ConfigHistoryExportFailed |
Number of failed exports of configuration history to Amazon S3. | Use the dimension sets actually published by CloudWatch | count |
ConfigSnapshotExportFailed |
Number of failed exports of configuration snapshots to Amazon S3. | Use the dimension sets actually published by CloudWatch | count |
ConfigurationRecorderInsufficientPermissionsFailure |
Number of access failures caused by insufficient IAM role permissions for the configuration recorder. | Use the dimension sets actually published by CloudWatch | count |
ChangeNotificationsDeliveryFailed |
Number of failed deliveries of configuration change notifications to the delivery channel Amazon SNS topic. | Use the dimension sets actually published by CloudWatch | count |
ConfigurationItemsRecorded |
Number of configuration items recorded; each item represents a resource configuration at a point in time. | Use the dimension sets actually published by CloudWatch | count |