What is AWS Config?
AWS Config is a fully managed service that provides you with an AWS resource inventory, configuration history, and configuration change notifications to enable security and governance. With AWS Config you can discover existing AWS resources, export a complete inventory of your AWS resources with all configuration details, and determine how a resource was configured at any point in time. These capabilities enable compliance auditing, security analysis, resource change tracking, and troubleshooting.
What are the benefits of AWS Config?
AWS Config makes it easy to track your resource’s configuration without the need for up-front investments and avoiding the complexity of installing and updating agents for data collection or maintaining large databases. Once you enable AWS Config, you can view continuously updated details of all configuration attributes associated with AWS resources. You are notified via Amazon Simple Notification Service (SNS) of every configuration change.
How can AWS Config help with audits?
AWS Config gives you access to resource configuration history. You can relate configuration changes with AWS CloudTrail events that possibly contributed to the change in configuration. This information provides you full visibility, right from details, such as “Who made the change?”, “From what IP address?” to the effect of this change on AWS resources and related resources. You can use this information to generate reports to aid auditing and assessing compliance over a period of time.
Who should turn on AWS Config?
Customers who want to track changes to resources configuration, answer questions about resource configurations, demonstrate compliance, troubleshoot or perform security analysis should turn on AWS Config.
How does AWS Config work with AWS CloudTrail?
AWS CloudTrail records user API activity on your account and allows you to access information about this activity. You get full details about API actions, such as identity of the caller, the time of the API call, the request parameters, and the response elements returned by the AWS service. AWS Config records point-in-time configuration details for your AWS resources as Configuration Items (CIs). You can use a CI to answer “What did my AWS resource look like?” at a point in time. You can use AWS CloudTrail to answer “Who made an API call to modify this resource?” For example, you can use the AWS Management Console for AWS Config to detect security group “Production-DB” was incorrectly configured in the past. Using the integrated AWS CloudTrail information, you can pinpoint which user misconfigured “Production-DB” security group.
How do I get started with this service?
The quickest way to get started with AWS Config is to use the AWS Management Console. You can turn on AWS Config in two clicks. For additional details, see the Getting Started documentation.
How do I access my resources’ configuration?
You can lookup current and historical resource configuration using the AWS Management Console, AWS Command Line Interface or SDKs.
For additional details, please refer to AWS Config documentation.
Do I turn on AWS Config regionally or globally?
You turn on AWS Config on a per-region basis for your account.
Can AWS Config aggregate data across different AWS accounts?
Yes, you can set up AWS Config to deliver configuration updates from different accounts to one S3 bucket, once the appropriate IAM policies are applied to the S3 bucket. You can also publish notifications to the one SNS Topic, within the same region, once appropriate IAM policies are applied to the SNS Topic.
Is API activity on AWS Config itself logged by AWS CloudTrail?
Yes. All AWS Config API activity, including use of AWS Config APIs to read configuration data, is logged by AWS CloudTrail.
What time and timezones are displayed in the timeline view of a resource? What about daylight savings?
AWS Config displays the time at which configurations were recorded for a resource on a timeline. All times are captured in Coordinated Universal Time (UTC). When the timeline is visualized on the management console, the services uses the current time zone (adjusted for daylight savings, if relevant) to display all the other recorded times in the timeline view.
What AWS resources types are covered by AWS Config?
At this time, AWS Config monitors configurations for the following resource types.
Amazon EC2
• EC2 Instance
• EC2 Network Interface
• EC2 Security Group
• EC2 Elastic IP (VPC only)
Amazon VPC
• Customer Gateway
• Internet Gateway
• Network ACL
• RouteTable
• Subnets
• VPCs
• VPN Gateway
• VPN Connection
Amazon EBS
• EBS Volumes (all types)
AWS CloudTrail
• Trail
What regions is AWS Config available in?
For details on the regions where AWS Config is available, please visit this page:
http://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/
What is a configuration item?
A Configuration Item (CI) is the configuration of a resource at a given point-in-time. A CI consists of 5 sections:
- Basic information about the resource that is common across different resource types (e.g., Amazon Resource Names, tags),
- Configuration data specific to the resource (e.g., EC2 instance type),
- Map of relationships with other resources (e.g., EC2::Volume vol-3434df43 is “attached to instance” EC2 Instance i-3432ee3a),
- AWS CloudTrail event IDs that are related to this state,
- Metadata that helps you identify information about the CI, such as the version of this CI, and when this CI was captured.
What are AWS Config relationships and how are they used?
AWS Config takes the relationships among resources into account when recording changes. For example, if a new Amazon EC2 Security Group is associated with an Amazon EC2 Instance, AWS Config records the updated configurations of both the primary resource, the Amazon EC2 Security Group, and related resources, such as the Amazon EC2 Instance, if these resources actually changed.
Does AWS Config record every state a resource has been in?
AWS Config detects change to resource's configuration and records the configuration state that resulted from that change. In cases where several configuration changes are made to a resource in quick succession (e.g. within a span of few minutes), Config will only record the latest configuration of that resource that represents cumulative impact of the set of changes. In these situations, Config will only list the latest change in the relatedEvents field of the Configuration Item.This allows users and programs to continue to change infrastructure configurations without having to wait for Config to record intermediate transient states.
Does AWS Config record configuration changes that did not result from API activity on that resource?
Yes, AWS Config will regularly scan configuration of resources for changes that haven't yet been recorded and record these changes. CIs recorded from these scans will not have a relatedEvent field in the payload, and only the latest state that is different from state already recorded is picked up.
How will I be charged for this service?
With AWS Config, you are charged based on the number Configuration Items (CIs) recorded for supported resources in your AWS account. There is no up-front commitment and you can stop recording CIs at any time. Charges per CI are rolled up into your monthly bill. See pricing details.
Configuration snapshots and Configuration history files are delivered to you in an S3 bucket that you choose, and configuration change notifications are delivered via Amazon Simple Notification Service (SNS).Standard rates for Amazon S3 and Amazon SNS apply
Can you provide breakdown of charges using an example?
The service charges you incur depend on the number of CIs recoded by your resources. This depends on the number of resources in your account, and the configuration changes you make to these resources. For an account with several hundred resources, and standard configuration change activity, AWS Config would capture fewer than 3,000 CIs per month, or less than $9 per month.
Typical S3 charges based on 3,000 CIs per month are less than $1. The 3,000 SNS notifications for each CI are within the free tier of 1 million requests per month, incurring a $0.0 fee.
What AWS partner solutions are available for AWS Config?
Ecosystem partners such as Splunk, ServiceNow, Evident.IO, CloudCheckr, Redseal Networks and RedHat CloudForms provide offerings that are fully integrated with data from AWS Config. Managed Service Providers, such as 2nd Watch and CloudNexa have also announced integrations with AWS Config. These solutions include capabilities such as change management and security analysis and allow you to visualize, monitor and manage AWS resource configurations.
For more information, see AWS Config partner solutions.