put_resource_config
async
¶
put_resource_config(
resource_type: ResourceTypeString,
schema_version_id: SchemaVersionId,
resource_id: ResourceId,
configuration: Configuration,
*,
config_overrides: Optional[AsyncConfigServiceClientConfig] = None,
resource_name: Optional[ResourceName] = None,
tags: Optional[Tags] = None,
) -> None
Records the configuration state for the resource provided in the request. The configuration state of a resource is represented in Config as Configuration Items. Once this API records the configuration item, you can retrieve the list of configuration items for the custom resource type using existing Config APIs.
The custom resource type must be registered with CloudFormation. This API accepts the configuration item registered with CloudFormation.
When you call this API, Config only stores configuration state of the resource provided in the request. This API does not change or remediate the configuration of the resource.
Write-only schema properites are not recorded as part of the published configuration item.
Parameters:
-
resource_type(ResourceTypeString) –The type of the resource. The custom resource type must be registered with CloudFormation.
You cannot use the organization names “amzn”, “amazon”, “alexa”, “custom” with custom resource types. It is the first part of the ResourceType up to the first ::.
-
schema_version_id(SchemaVersionId) –Version of the schema registered for the ResourceType in CloudFormation.
-
resource_id(ResourceId) –Unique identifier of the resource.
-
resource_name(Optional[ResourceName], default:None) –Name of the resource.
-
configuration(Configuration) –The configuration object of the resource in valid JSON format. It must match the schema registered with CloudFormation.
The configuration JSON must not exceed 64 KB.
-
tags(Optional[Tags], default:None) –Tags associated with the resource.
This field is not to be confused with the Amazon Web Services-wide tag feature for Amazon Web Services resources. Tags for
PutResourceConfigare tags that you supply for the configuration items of your custom resources.
Raises:
-
InsufficientPermissionsException–Indicates one of the following errors:
-
For PutConfigRule, the rule cannot be created because the IAM role assigned to Config lacks permissions to perform the config:Put* action.
-
For PutConfigRule, the 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
GetRoleaction or create a service-linked role. -
For PutConformancePack and PutOrganizationConformancePack, a conformance pack cannot be created because you do not have the following permissions:
-
You do not have permission to call IAM
GetRoleaction or create a service-linked role. -
You do not have permission to read Amazon S3 bucket or call SSM:GetDocument.
-
-
For PutServiceLinkedConfigurationRecorder, a service-linked configuration recorder cannot be created because you do not have the following permissions: IAM
CreateServiceLinkedRole. -
For PutConnector, a connector cannot be created because you do not have the following permissions: IAM
CreateServiceLinkedRole.
-
-
MaxActiveResourcesExceededException–You have reached the limit of active custom resource types in your account. There is a limit of 100,000. Delete unused resources using DeleteResourceConfig
. -
NoRunningConfigurationRecorderException–There is no configuration recorder running.
-
ValidationException–The requested operation is not valid. You will see this exception if there are missing required fields or if the input value fails the validation.
For PutStoredQuery, one of the following errors:
-
There are missing required fields.
-
The input value fails the validation.
-
You are trying to create more than 300 queries.
For DescribeConfigurationRecorders and DescribeConfigurationRecorderStatus, one of the following errors:
-
You have specified more than one configuration recorder.
-
You have provided a service principal for service-linked configuration recorder that is not valid.
For AssociateResourceTypes and DisassociateResourceTypes, one of the following errors:
-
Your configuraiton recorder has a recording strategy that does not allow the association or disassociation of resource types.
-
One or more of the specified resource types are already associated or disassociated with the configuration recorder.
-
For service-linked configuration recorders, the configuration recorder does not record one or more of the specified resource types.
For DeleteServiceLinkedConfigurationRecorder, one of the following errors:
-
You have provided both
ArnandServicePrincipal. Only one ofArnorServicePrincipalcan be specified. -
You have provided a service principal for service-linked configuration recorder that is not valid.
-
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_config_service/_services/async_config_service.py
6609 6610 6611 6612 6613 6614 6615 6616 6617 6618 6619 6620 6621 6622 6623 6624 6625 6626 6627 6628 6629 6630 6631 6632 6633 6634 6635 6636 6637 6638 6639 6640 6641 6642 6643 6644 6645 6646 6647 6648 6649 6650 6651 6652 6653 6654 6655 6656 6657 6658 6659 6660 6661 6662 6663 6664 6665 6666 6667 6668 6669 6670 6671 6672 6673 | |