Class: Aws::ConfigService::Types::ConfigurationRecorder

Inherits:
Struct
  • Object
show all
Includes:
Structure
Defined in:
lib/aws-sdk-configservice/types.rb

Overview

Records configuration changes to your specified resource types. For more information about the configuration recorder, see [ **Managing the Configuration Recorder** ][1] in the *Config Developer Guide*.

[1]: docs.aws.amazon.com/config/latest/developerguide/stop-start-recorder.html

Constant Summary collapse

SENSITIVE =
[]

Instance Attribute Summary collapse

Instance Attribute Details

#nameString

The name of the configuration recorder. Config automatically assigns the name of “default” when creating the configuration recorder.

<note markdown=“1”> You cannot change the name of the configuration recorder after it has been created. To change the configuration recorder name, you must delete it and create a new configuration recorder with a new name.

</note>

Returns:

  • (String)


1545
1546
1547
1548
1549
1550
1551
1552
# File 'lib/aws-sdk-configservice/types.rb', line 1545

class ConfigurationRecorder < Struct.new(
  :name,
  :role_arn,
  :recording_group,
  :recording_mode)
  SENSITIVE = []
  include Aws::Structure
end

#recording_groupTypes::RecordingGroup

Specifies which resource types Config records for configuration changes.

<note markdown=“1”> High Number of Config Evaluations

You may notice increased activity in your account during your

initial month recording with Config when compared to subsequent months. During the initial bootstrapping process, Config runs evaluations on all the resources in your account that you have selected for Config to record.

If you are running ephemeral workloads, you may see increased

activity from Config as it records configuration changes associated with creating and deleting these temporary resources. An *ephemeral workload* is a temporary use of computing resources that are loaded and run when needed. Examples include Amazon Elastic Compute Cloud (Amazon EC2) Spot Instances, Amazon EMR jobs, and Auto Scaling. If you want to avoid the increased activity from running ephemeral workloads, you can run these types of workloads in a separate account with Config turned off to avoid increased configuration recording and rule evaluations.

</note>


1545
1546
1547
1548
1549
1550
1551
1552
# File 'lib/aws-sdk-configservice/types.rb', line 1545

class ConfigurationRecorder < Struct.new(
  :name,
  :role_arn,
  :recording_group,
  :recording_mode)
  SENSITIVE = []
  include Aws::Structure
end

#recording_modeTypes::RecordingMode

Specifies the default recording frequency that Config uses to record configuration changes. Config supports *Continuous recording* and *Daily recording*.

  • Continuous recording allows you to record configuration changes continuously whenever a change occurs.

  • Daily recording allows you to receive a configuration item (CI) representing the most recent state of your resources over the last 24-hour period, only if it’s different from the previous CI recorded.

<note markdown=“1”> Firewall Manager depends on continuous recording to monitor your resources. If you are using Firewall Manager, it is recommended that you set the recording frequency to Continuous.

</note>

You can also override the recording frequency for specific resource types.



1545
1546
1547
1548
1549
1550
1551
1552
# File 'lib/aws-sdk-configservice/types.rb', line 1545

class ConfigurationRecorder < Struct.new(
  :name,
  :role_arn,
  :recording_group,
  :recording_mode)
  SENSITIVE = []
  include Aws::Structure
end

#role_arnString

Amazon Resource Name (ARN) of the IAM role assumed by Config and used by the configuration recorder.

<note markdown=“1”> While the API model does not require this field, the server will reject a request without a defined ‘roleARN` for the configuration recorder.

</note>

<note markdown=“1”> **Pre-existing Config role**

If you have used an Amazon Web Services service that uses Config,

such as Security Hub or Control Tower, and an Config role has already been created, make sure that the IAM role that you use when setting up Config keeps the same minimum permissions as the already created Config role. You must do this so that the other Amazon Web Services service continues to run as expected.

For example, if Control Tower has an IAM role that allows Config to

read Amazon Simple Storage Service (Amazon S3) objects, make sure that the same permissions are granted within the IAM role you use when setting up Config. Otherwise, it may interfere with how Control Tower operates. For more information about IAM roles for Config, see

**Identity and Access Management for Config** ][1

in the *Config

Developer Guide*.

</note>

[1]: docs.aws.amazon.com/config/latest/developerguide/security-iam.html

Returns:

  • (String)


1545
1546
1547
1548
1549
1550
1551
1552
# File 'lib/aws-sdk-configservice/types.rb', line 1545

class ConfigurationRecorder < Struct.new(
  :name,
  :role_arn,
  :recording_group,
  :recording_mode)
  SENSITIVE = []
  include Aws::Structure
end