#[non_exhaustive]
pub enum DeleteRemediationConfigurationErrorKind {
InsufficientPermissionsException(InsufficientPermissionsException),
InvalidParameterValueException(InvalidParameterValueException),
NoSuchRemediationConfigurationException(NoSuchRemediationConfigurationException),
RemediationInProgressException(RemediationInProgressException),
Unhandled(Unhandled),
}Expand description
Types of errors that can occur for the DeleteRemediationConfiguration operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
InsufficientPermissionsException(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 permissions:
-
To call IAM
GetRoleaction or create a service-linked role. -
To read Amazon S3 bucket or call SSM:GetDocument.
-
InvalidParameterValueException(InvalidParameterValueException)
One or more of the specified parameters are invalid. Verify that your parameters are valid and try again.
NoSuchRemediationConfigurationException(NoSuchRemediationConfigurationException)
You specified an Config rule without a remediation configuration.
RemediationInProgressException(RemediationInProgressException)
Remediation action is in progress. You can either cancel execution in Amazon Web Services Systems Manager or wait and try again later.
Unhandled(Unhandled)
An unexpected error occurred (e.g., invalid JSON returned by the service or an unknown error code).
When logging an error from the SDK, it is recommended that you either wrap the error in
DisplayErrorContext, use another
error reporter library that visits the error’s cause/source chain, or call
Error::source for more details about the underlying cause.