integration-docs
Loading

Config

Stack 9.1.0 Serverless Observability Serverless Security

Version 4.2.0 (View all)
Subscription level
What's this?
Basic
Ingestion method(s) API, AWS CloudWatch, AWS S3

AWS Config provides a detailed view of the configuration of AWS resources in your AWS account. This includes how the resources are related to one another and how they were configured in the past so that you can see how the configurations and relationships change over time.

Use this integration to collect and parse data from your AWS Config APIs. Visualize that data in Kibana, create alerts to notify you if something goes wrong, and reference data when troubleshooting an issue.

Important

Extra AWS charges on API requests will be generated by this integration. Check API Requests for more details.

The AWS Config integration collects one type of data: logs.

Logs help you keep a record of the findings in AWS Config, allowing you to track and audit compliance status of your resources.

The AWS Config integration works by first retrieving all config rules using the DescribeConfigRules API. Then, for each specific config rule, the integration fetches its evaluation results using the GetComplianceDetailsByConfigRule API. These evaluation results enrich their respective config rules, ultimately producing a finding log.

See more details in the Logs reference.

Agentless integrations allow you to collect data without having to manage Elastic Agent in your cloud. They make manual agent deployment unnecessary, so you can focus on your data instead of the agent that collects it. For more information, refer to Agentless integrations and the Agentless integrations FAQ. Agentless deployments are only supported in Elastic Serverless and Elastic Cloud environments. This functionality is in beta and is subject to change. Beta features are not subject to the support SLA of official GA features.

  • Elastic Agent must be installed
  • You can install only one Elastic Agent per host.
  • Elastic Agent is required to stream data from the REST API and ship the data to Elastic, where the events will then be processed via the integration's ingest pipelines.

Before using any AWS integration you will need:

  • AWS Credentials to connect with your AWS account.
  • AWS Permissions to make sure the user you're using to connect has permission to share the relevant data.

For more details about these requirements, please take a look at the AWS integration documentation.

Use this integration if you only need to collect data from the AWS Config service.

  1. Login to https://console.aws.amazon.com/.
  2. Go to https://console.aws.amazon.com/iam/ to access the IAM console.
  3. On the navigation menu, choose Users.
  4. Choose your IAM user name.
  5. Select Create access key from the Security Credentials tab.
  6. To see the new access key, choose Show.
  1. In Kibana navigate to Management > Integrations.
  2. In "Search for integrations" top bar, search for AWS Config.
  3. Select the "AWS Config" integration from the search results.
  4. Select "Add AWS Config" to add the integration.
  5. Add all the required integration configuration parameters, including the aws_region to enable data collection.
  6. Select "Save and continue" to save the integration.

Note

  1. For the current integration package, it is compulsory to add Secret Access Key and Access Key ID.
  2. The AWS Config integration performs a full ingestion of all findings during each interval.

Version 4.0.0 of the AWS Config integration adds support for Elastic Cloud Security workflow. The enhancement enables the users of the AWS Config integration to ingest misconfiguration findings from the AWS Config platform into Elastic and get insights directly from the Misconfiguration Findings page. Version 4.0.0 adds Elastic Latest Transform which copies the latest findings from source indices matching the pattern logs-aws.config-* into new destination indices matching the pattern security_solution-awsconfig.misconfiguration_latest-*. The Elastic Findings pages will display findings based on the destination indices.

For existing users of the AWS Config integration, before upgrading to version 4.0.0 please ensure the following requirements are met:

  1. Users need Elastic Security solution which has requirements documented here.
  2. To use transforms, users must have:
    • at least one transform node,
    • management features visible in the Kibana space, and
    • security privileges that:
      • grant use of transforms, and
      • grant access to source and destination indices For more details on Transform Setup, refer to the link here
  3. Because the latest copy of findings is now indexed in two places, that is, in both source and destination indices, users must anticipate storage requirements accordingly.

This is the config dataset.

An example event for config looks as following:

ECS Field Reference

Please refer to the following document for detailed information on ECS fields.

This integration includes one or more Kibana dashboards that visualizes the data collected by the integration. The screenshots below illustrate how the ingested data is displayed.