Class ConfigServiceException

You have specified a template that is not valid or supported.

Your Amazon S3 bucket policy does not permit AWS Config to write to it.

Indicates one of the following errors:

• For PutConfigRule, the rule cannot be created because the IAM role assigned to AWS Config lacks permissions to perform the config:Put* action.

• For PutConfigRule, the AWS Lambda function cannot be invoked. Check the function ARN, and check the function's permissions.

• For PutOrganizationConfigRule, organization config rule cannot be created because you do not have permissions to call IAM GetRole action or create a service linked role.

• For PutConformancePack and PutOrganizationConformancePack, a conformance pack cannot be created because you do not have permissions:

  • To call IAM GetRole action or create a service linked role.

  • To read Amazon S3 bucket.

You have provided a configuration recorder name that is not valid.

The specified delivery channel name is not valid.

The syntax of the query is incorrect.

The specified limit is outside the allowable range.

The specified next token is invalid. Specify the nextToken string that was returned in the previous response to get the next page of results.

One or more of the specified parameters are invalid. Verify that your parameters are valid and try again.

AWS Config throws an exception if the recording group does not contain a valid list of resource types. Invalid values might also be incorrectly formatted.

The specified ResultToken is invalid.

You have provided a null or empty role ARN.

The specified Amazon S3 key prefix is not valid.

The specified Amazon SNS topic does not exist.

The specified time range is not valid. The earlier time is not chronologically before the later time.

You cannot delete the delivery channel you specified because the configuration recorder is running.

For StartConfigRulesEvaluation API, this exception is thrown if an evaluation is in progress or if you call the StartConfigRulesEvaluation API more than once per minute.

For PutConfigurationAggregator API, this exception is thrown if the number of accounts and aggregators exceeds the limit.

You have reached the limit (100,000) of active custom resource types in your account. Delete unused resources using DeleteResourceConfig.

Failed to add the AWS Config rule because the account already contains the maximum number of 150 rules. Consider deleting any deactivated rules before you add new rules.

You have reached the limit of the number of recorders you can create.

You have reached the limit (6) of the number of conformance packs in an account (6 conformance pack with 25 AWS Config rules per pack).

You have reached the limit of the number of delivery channels you can create.

You have reached the limit of the number of organization config rules you can create.

You have reached the limit (6) of the number of organization conformance packs in an account (6 conformance pack with 25 AWS Config rules per pack per account).

Failed to add the retention configuration because a retention configuration with that name already exists.

There are no configuration recorders available to provide the role needed to describe your resources. Create a configuration recorder.

There is no delivery channel available to record configurations.

Organization is no longer available.

There is no configuration recorder running.

The specified Amazon S3 bucket does not exist.

One or more AWS Config rules in the request are invalid. Verify that the rule names are correct and try again.

AWS Config rule that you passed in the filter does not exist.

You have specified a configuration aggregator that does not exist.

You have specified a configuration recorder that does not exist.

You specified one or more conformance packs that do not exist.

You have specified a delivery channel that does not exist.

You specified one or more organization config rules that do not exist.

AWS Config organization conformance pack that you passed in the filter does not exist.

For DeleteOrganizationConformancePack, you tried to delete an organization conformance pack that does not exist.

You specified an AWS Config rule without a remediation configuration.

You tried to delete a remediation exception that does not exist.

You have specified a retention configuration that does not exist.

For PutConfigAggregator API, no permission to call EnableAWSServiceAccess API.

For all OrganizationConfigRule and OrganizationConformancePack APIs, AWS Config throws an exception if APIs are called from member accounts. All APIs must be called from organization master account.

AWS Config resource cannot be created because your organization does not have all features enabled.

You have specified a template that is not valid or supported.

The configuration item size is outside the allowable range.

Remediation action is in progress. You can either cancel execution in AWS Systems Manager or wait and try again later.

Two users are trying to modify the same query at the same time. Wait for a moment and try again.

You see this exception in the following cases:

• For DeleteConfigRule, AWS Config is deleting this rule. Try your request again later.

• For DeleteConfigRule, the rule is deleting your evaluation results. Try your request again later.

• For DeleteConfigRule, a remediation action is associated with the rule and AWS Config cannot delete this rule. Delete the remediation action associated with the rule before deleting the rule and try your request again later.

• For PutConfigOrganizationRule, organization config rule deletion is in progress. Try your request again later.

• For DeleteOrganizationConfigRule, organization config rule creation is in progress. Try your request again later.

• For PutConformancePack and PutOrganizationConformancePack, a conformance pack creation, update, and deletion is in progress. Try your request again later.

• For DeleteConformancePack, a conformance pack creation, update, and deletion is in progress. Try your request again later.

You have specified a resource that is either unknown or has not been discovered.

You have specified a resource that does not exist.

You have reached the limit of the number of tags you can use. You have more than 50 tags.

The requested action is not valid.