Skip to main content
This walkthrough shows how to enable AWS Config to build a basic, region-specific resource inventory. It covers navigating the console, selecting a recording method, configuring delivery to Amazon S3, optionally using managed rules, reviewing settings, and verifying that AWS Config is recording and populating the resource inventory. Before you start, choose the AWS Region where you want the inventory and open the AWS Management Console. AWS Config is region-scoped; each region maintains its own recorder, delivery channel, and inventory.

Quick summary

Steps

  1. Navigate to AWS Config
  • Open the AWS Console and type Config in the search bar. Select the Config service.
  • If this is your first time, the console shows a “Get started” flow. Otherwise you’ll land on the AWS Config dashboard.
  1. Start setup and choose recording method
  • Click Get started and follow the three-step setup: Settings → Rules → Review.
  • Under Recording method choose All resource types with customizable overrides. This instructs AWS Config to record all supported resources in the region while still allowing you to exclude specific types or change recording frequency per resource.
A screenshot of the AWS Management Console on the "Set up AWS Config" page showing the "Recording method" section with the "All resource types with customizable overrides" option selected. The browser toolbar and account/region details are visible at the top, with setup steps listed on the left.
  1. Recording frequency and overrides
  • For a near real-time inventory, choose Continuous recording. This captures configuration changes as they occur rather than as a daily snapshot.
  • Overrides are optional—use them to exclude resource types or change frequency for specific resources. For this demo you can leave overrides at their defaults.
  1. Data governance: service-linked role
  • AWS Config must read resource configurations and deliver snapshots. When prompted, create the AWS Config service-linked role so Config has the permissions it needs.
  1. Delivery channel: configure S3 for snapshots and history
  • Configure the delivery channel so AWS Config can write configuration snapshots and configuration history to an S3 bucket.
  • You can create a new bucket during setup or choose an existing one. The console will validate an existing S3 bucket in your account.
A screenshot of the AWS Console showing the "Set up AWS Config" Delivery channel page, with options to create or choose an Amazon S3 bucket and a selected S3 bucket name field. The page also shows an S3 prefix path and related configuration controls.
  • Best practice: create the bucket in the same Region (and account) to avoid cross-region transfer costs and simplify permissions. Use a descriptive name such as config-<region>-<account-id> when creating a new bucket. Verify bucket permissions allow AWS Config to write objects.
  1. Rules (optional)
  • AWS Config offers many managed rules to evaluate resources against policies (for example, checking certificate or load balancer settings). Rules mark resources as compliant or non-compliant.
  • For a basic resource inventory you do not need rules; you can add managed or custom rules later to automate compliance checks.
  1. Review and confirm
  • On the Review step, use the Edit buttons to adjust Settings, Rules, or Delivery channel. When ready, confirm to create the configuration recorder and delivery channel.
A browser screenshot of the AWS Console showing the "Set up AWS Config" Review page with a left-side stepper highlighting Step 3: Review. The main panel shows "Review" and "Step 1: Settings" with a "Recording method" summary and an Edit button.
  1. Verify recording and view the resource inventory
  • After setup you’ll be redirected to the AWS Config dashboard. Go to Settings and confirm the recorder status shows Recording is on. AWS Config must be recording in order to capture new configuration changes.
If recording is not enabled, AWS Config will not collect any new configuration information. Always verify that the recorder status is active before relying on the inventory.
A screenshot of the AWS Config Settings page. It shows a customer-managed recorder marked "Recording is on" with Edit and Stop recording buttons and recording method details below.
  • Open Resources → Resource inventory to view collected resources and metadata. Initial discovery may take time depending on the number of resources in the account and region.
AWS Config is region-scoped. The inventory shown in the console is specific to the selected region. If you enable Config in multiple regions, each region will maintain its own inventory and delivery artifacts.
  • Example: below is a Resources view (from a different region) illustrating how discovered resources are listed once AWS Config completes discovery.
A screenshot of the AWS Config "Resources" console listing resource identifiers and types (e.g., ACM Certificate, several AppConfig deployment strategies, Athena WorkGroup, Cassandra Keyspace). The top-right shows an account banner labeled "CloudWithDjango-Org."

Troubleshooting checklist

  • Recorder status: Confirm Recording is on in Settings.
  • Delivery: Ensure the S3 bucket exists and AWS Config has write permissions.
  • Region: Verify the console region matches the region you enabled AWS Config in.
  • Role: Confirm the service-linked role was created (or manually create it if needed).

Conclusion

  • Enabling AWS Config with continuous recording and an S3 delivery channel creates a dependable, region-specific resource inventory and configuration history.
  • Allow time for initial discovery; once enabled, AWS Config captures changes continuously. Add AWS-managed or custom rules later to enforce compliance and monitor drift.

Watch Video

Practice Lab