An ordinary account is an independent Alibaba Cloud account that is not included in a resource directory by a management account. This topic helps you get started with Cloud Config by using an ordinary account.

Procedure

The following figure shows the steps to get started with Cloud Config by using an ordinary account. Quick start for ordinary accounts
The following table describes the steps to get started with Cloud Config by using an ordinary account.
Category Step Description
Basic operations Step 1: Authorize Cloud Config to access your resources Before you use Cloud Config, you must authorize Cloud Config to access your resources.
Step 2: View the resource list You can view and manage the resources within your account.
Step 3: Create a compliance package You can create a compliance package based on a compliance package template. After you create a compliance package, you can view the compliance evaluation results of associated resources based on the specified rule.
Advanced operations Step 4: Create a rule (Optional) You can create rules by enabling managed rules provided by Cloud Config to audit specified resources.
Step 5: Set the monitoring scope (Optional) By default, Cloud Config monitors all supported types of resources. You can specify the types of resources to be monitored by Cloud Config.
Step 6: Configure resource delivery (Optional) You can specify an Object Storage Service (OSS) bucket to receive the scheduled resource snapshots and resource change logs within your account.
Step 7: Subscribe to resource events (Optional) You can specify a Message Service (MNS) topic to receive the resource non-compliance events and resource change logs within your account.

Step 1: Authorize Cloud Config to access your resources

  1. Log on to the Cloud Config console.
  2. In the Authorize step, click Allow to create the service-linked role that authorizes Cloud Config to access your resources.
    Authorize Cloud Config
    Note Cloud Config needs 2 to 10 minutes to scan your resources and generate a resource list.

Step 2: View the resource list

  1. Log on to the Cloud Config console.
  2. In the left-side navigation pane, choose Resources > Global Resources.
  3. On the Global Resources page, enter a resource ID or set filter conditions to search for the specified resource.
    • You can enter a resource ID to search for the specified resource.
    • You can filter the resources based on the resource type, region, compliance status, and resource status to search for the specified resource with high efficiency.
  4. Click the resource ID in the Resource ID / Resource Name column.
  5. On the Details tab, view the basic information, core configurations, and latest compliance evaluation results of the resource.
    • In the Basic Information section, you can view the ID, name, type, and tags of the resource, the time when the resource was created, and the region and zone in which the resource resides.
    • In the Configuration Details section, you can click View JSON to view the core configurations in the JSON format.
    • In the Latest Evaluation Results section, you can view the latest compliance evaluation results of the resource.

Step 3: Create a compliance package

  1. Log on to the Cloud Config console.
  2. In the left-side navigation pane, click Compliance Package.
  3. On the Compliance Package page, click Enable Compliance Package in the upper-right corner.
  4. In the Basic Information step, specify a name and a risk level for the compliance package. Then, click Next.
  5. In the Select a rule step, select Compliance Package Template, Rules, or Managed rule from the drop-down list. Then, select one or more rules from the rule list. If you select Compliance Package Template, select a compliance package template from the drop-down list that appears. Then, click Next.
  6. In the Rule Settings step, configure the Rule Name, Risk Level, and Description parameters for each rule, and then click Finish.

Step 4: Create a rule (Optional)

  1. Log on to the Cloud Config console.
  2. In the left-side navigation pane, click Rules.
  3. On the Rules page, click Create Rule.
  4. On the Create Rule page, search for a managed rule based on the rule name, tag, evaluation logic, or risk level.
  5. Click Apply Rule.
  6. In the Properties step, set the Rule Name, Risk Level, and Description parameters. Then, click Next.
    The Rule Name, Risk Level, and Trigger Type parameters have default values. You can change the values of the Rule Name and Risk Level parameters.
  7. In the Assess Resource Scope step, keep the default resource type and click Next.
  8. In the Parameters step, click Next.
    If the managed rule has an input parameter, you must set an expected value for the input parameter.
  9. In the Modify step, click Next.

    For managed rules that allow you to modify the remediation settings, you can select the check box next to Modify and set the remediation method, remediation type, and parameters involved. For more information, see Configure automatic remediation or Configure manual remediation.

  10. In the Preview and Save step, check the configurations and click Submit.
  11. Verify that the rule is created.
    • Click View Details. On the page that appears, you can view the rule details on the Rule Details, Result, and Correction Details tabs.
    • Click Return to Rule List. In the Rules list, you can view the status of the created rule in the Status column. In normal cases, the rule is in the Active state.

Step 5: Set the monitoring scope (Optional)

  1. Log on to the Cloud Config console.
  2. In the left-side navigation pane, choose Settings > Service Settings.
  3. On the Service Settings page, click Monitoring Scope. On the tab that appears, click Modify.
  4. Specify resources that you want to monitor.
    • If you select All Supported Resource Types, a new service that is integrated with Cloud Config is automatically monitored.
    • If you select Custom Resource Types, you can specify resources that you want to monitor.
  5. Click OK.
  6. In the Email Verification dialog box, click Get Verification Code.
    Alibaba Cloud sends a verification code to the email address that is bound to your account.
  7. Enter the verification code in the Verification Code field and click OK.

Step 6: Configure resource delivery (Optional)

  1. Log on to the Cloud Config console.
  2. In the left-side navigation pane, choose Settings > Delivery Channels.
  3. On the Delivery Settings page, click Deliver Logs to OSS.
  4. On the Deliver Logs to OSS tab, turn on OSS Settings.
  5. Configure the parameters to deliver resource data.
    The following table describes the parameters.
    Parameter Description
    Select Acceptable Content The type of the resource data that you want to deliver to the OSS bucket. Valid values:
    • Scheduled Snapshots: scheduled resource snapshots. Cloud Config delivers resource snapshots to the OSS bucket at 00:00:00 and 12:00:00 every day.
    • Historical Configuration Changes: resource change logs. Cloud Config delivers resource change logs to the OSS bucket when the configurations of resources are changed.
    Bucket Source The source of the OSS bucket.
    • If you select Create a bucket in the account, specify a bucket name.
    • If you select Select an existing bucket from the account, select an existing bucket from the Bucket drop-down list.
    Region The region where the OSS bucket resides.
    Bucket The name of the OSS bucket. The bucket name must be unique.
    Server-side Encryption Specifies whether to encrypt log files and the method that is used to encrypt the log files. This parameter is required only if you select Create a bucket in the account in the Bucket Source section.
    Valid values:
    • No
    • AES256
    • KMS
  6. Click OK.

Step 7: Subscribe to resource events (Optional)

  1. Log on to the Cloud Config console.
  2. In the left-side navigation pane, choose Settings > Delivery Channels.
  3. On the Delivery Settings page, click Deliver Data to Message Service
  4. On the Deliver Data to Message Service tab, turn on MNS Settings.
  5. Configure the parameters to deliver resource data.

    The following table describes the parameters.

    Parameter Description
    Select Acceptable Content
    The type of the resource data that you want to deliver to the MNS topic. Valid values:
    • Historical Configuration Changes: resource change logs. Cloud Config delivers resource change logs to the MNS topic when the configurations of resources change.
    • Non-compliance Events: resource non-compliance events. If a resource is evaluated as incompliant, Cloud Config delivers the resource non-compliance event to the MNS topic.
    MNS Topic Source The source of the MNS topic.
    • If you select Create a topic in the account, specify a topic name.
    • If you select Select an existing topic from the account, select an existing topic from the Topic Name drop-down list.
    Topic name The name of the MNS topic. The topic name must be unique in the account in the specified region.
    MNS Region The region where the MNS topic resides.
    Maximum Message Size (Byte) The maximum length of the message body that can be received by the topic. Unit: bytes. Valid values: 1024 to 65536. Default value: 65536.
    Note We recommend that you set this parameter to a value greater than or equal to 8192. Otherwise, the message delivery may fail due to the length limit.
    Enable Logging Specifies whether to store the operation logs of the MNS topic in the associated Log Service Logstore. Operation logs are generated when messages are received, forwarded, and deleted.
    Minimum Risk Level of the Events to Subscribe The lowest risk level of the events to which you want to subscribe. Valid values:
    • All Risk Levels
    • High Risk
    • Medium Risk
    • Low Risk

    For example, if you select Medium Risk, Cloud Config delivers non-compliance events at the Medium Risk and High Risk levels. Non-compliance events at the Low Risk level are ignored.

    Events of Specified Resource Type The types of the resources whose events to which you want to subscribe. Valid values:
    • All Supported Resource Types: subscribes to the events of all supported types of resources. If a new service is integrated with Cloud Config, the resource type of the service is automatically added to the monitoring scope.
    • Custom Resource Types: subscribes to the events of the specified types of resources.
    Recipient Address for Large Files
    The Object Storage Service (OSS) bucket that is used to receive the large messages that Cloud Config delivers to the MNS topic.
    • If you configure this parameter, a message that Cloud Config delivers to the MNS topic is automatically transferred to the specified OSS bucket when the message size exceeds 64 KB.
    • If you leave this parameter empty, the excess part of a message that Cloud Config delivers to the MNS topic is automatically discarded when the message size exceeds 64 KB.
    Note The Region and Account parameters are automatically configured based on the settings in the Content and Recipient Address section. You need to only select a bucket.
  6. Click OK.