AWS S3¶

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

Configuration¶

Install Func¶

It is recommended to activate Guance Integration - Extension - Managed Func: all prerequisites will be automatically installed. Please proceed with the script installation.

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

Script Installation¶

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

Managed Version Script Activation¶

1. Log in to the Guance console.
2. Click on the 【Manage】 menu and select 【Cloud Account Management】.
3. Click 【Add Cloud Account】, choose 【AWS】, and 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 the corresponding cloud account and go to the details page.
6. On the cloud account details page, click the 【Integration】 button. Under the Not Installed list, find AWS S3, click the 【Install】 button, and follow the prompts to install it.

Manual Script Activation¶

1. Log in to the Func console, click 【Script Market】, enter the official script market, and search for guance_aws_s3.
2. After clicking 【Install】, input the corresponding parameters: AWS AK ID, AK Secret, and account name.
3. Click 【Deploy Startup Script】, and the system will automatically create a Startup script set and configure the corresponding startup scripts.
4. After enabling, you can see the corresponding automatic trigger configuration in "Management / Automatic Trigger Configuration". Click 【Execute】 to run it immediately without waiting for the regular time interval. Wait a moment, and you can view the execution task records and corresponding logs.

Verification¶

1. In "Management / Automatic Trigger Configuration", confirm whether the corresponding tasks have the corresponding automatic trigger configurations, and at the same time, you can check the corresponding task records and logs for any abnormalities.
2. In Guance, under "Infrastructure / Custom", check if there are asset information entries.
3. In Guance, under "Metrics", check if there are corresponding monitoring data entries.

Metrics¶

After configuring Amazon-CloudWatch, the default metric sets are as follows. You can collect more metrics through configuration. Details about Amazon CloudWatch Metrics

Daily Storage Metrics for Amazon S3 Buckets in CloudWatch¶

The AWS/S3 namespace includes the following daily storage metrics for buckets.

Request Metrics for Amazon S3 in CloudWatch¶

The AWS/S3 namespace includes the following request metrics. These metrics include non-billable requests (such as GET requests from COPY and Replication).

S3 Replication Metrics in CloudWatch¶

You can use S3 replication metrics to monitor the progress of replication by tracking pending bytes, pending operations, and replication lag. For more details, see Monitoring Progress Using Replication Metrics.

Note:

You can enable alerts for replication metrics in Amazon CloudWatch. When setting up alarms for replication metrics, set the Missing data treatment field to Treat missing data as ignore (maintain the alarm state).

S3 Storage Lens Metrics in CloudWatch¶

You can publish S3 Storage Lens usage and activity metrics to Amazon CloudWatch to create a unified view of operations on CloudWatch dashboards. S3 Storage Lens metrics are published to the AWS/S3/Storage-Lens namespace in CloudWatch. CloudWatch publishing options are available for S3 Storage Lens dashboards upgraded to advanced metrics and recommendations.

For a list of S3 Storage Lens metrics published to CloudWatch, see Amazon S3 Storage Lens Metrics Glossary. For a complete list of dimensions, see Dimensions.

S3 Object Lambda Request Metrics in CloudWatch¶

S3 Object Lambda includes the following request metrics.

Amazon S3 on Outposts Metrics in CloudWatch¶

For a list of metrics used for S3 on Outposts in CloudWatch, see CloudWatch metrics.

Amazon S3 Dimensions in CloudWatch¶

The following dimensions are used to filter Amazon S3 metrics.

S3 Storage Lens Dimensions in CloudWatch¶

For a list of dimensions used to filter S3 Storage Lens metrics in CloudWatch, see Dimensions.

S3 Object Lambda Request Dimensions in CloudWatch¶

The following dimensions are used to filter data from object Lambda access points.

Objects¶

The collected AWS S3 object data structure can be viewed under "Infrastructure - Custom".

{
  "measurement": "aws_s3",
  "tags": {
    "name"              : "dataxxxx",
    "RegionId"          : "cn-northwest-1",
    "LocationConstraint": "cn-northwest-1",
    "Name"              : "dataxxxx"
  },
  "fields": {
    "CreationDate": "2022-03-09T06:13:31Z",
    "Grants"      : "{JSON data}",
    "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 name, used for unique identification.

Tip 2: fields.message is a JSON serialized string.

Tip 3: fields.Grants represents the bucket access control list.