AWS Config launches support for third-party resources

AWS Config announces the launch of a new feature that enables you to perform configuration audit and compliance verification for third-party resources. You can now publish the configuration of third-party resources, such as GitHub repositories, Microsoft Active Directory resources, or any on-premises server into AWS Config using our new API.

After this configuration data is published into AWS Config, you can view and monitor the resource inventory and configuration history using the AWS Config console and APIs, just like you do today for AWS resources. You can also create AWS Config rules or conformance packs to evaluate these third-party resources against best practices, internal policies, and regulatory policies. This enables you to use AWS Config as your primary tool to perform configuration audit and compliance verification of both AWS and third-party resources.

Get started by registering the schema of your third-party resource in AWS CloudFormation Registry. Then, call the PutResourceConfig API in AWS Config to create a custom configuration item per the schema that you just registered. A custom configuration item is the configuration of a custom or third-party resource at a given point-in-time.

Pricing is based on the number of custom configuration items recorded. For more details, visit the AWS Config Pricing page. To learn more about AWS Config, visit the AWS Config webpage.

Support for third-party resources is available in the following AWS Regions: Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo) , Canada (Central), EU (Frankfurt), EU (Ireland), EU (London), EU (Paris), EU (Stockholm), South America (Sao Paulo), US East (N. Virginia), US East (Ohio), US West (N. California) and US West (Oregon).