import { Command as $Command } from "@smithy/smithy-client"; import type { MetadataBearer as __MetadataBearer } from "@smithy/types"; import type { ConfigServiceClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../ConfigServiceClient"; import type { DeleteOrganizationConformancePackRequest } from "../models/models_0"; /** * @public */ export type { __MetadataBearer }; export { $Command }; /** * @public * * The input for {@link DeleteOrganizationConformancePackCommand}. */ export interface DeleteOrganizationConformancePackCommandInput extends DeleteOrganizationConformancePackRequest { } /** * @public * * The output of {@link DeleteOrganizationConformancePackCommand}. */ export interface DeleteOrganizationConformancePackCommandOutput extends __MetadataBearer { } declare const DeleteOrganizationConformancePackCommand_base: { new (input: DeleteOrganizationConformancePackCommandInput): import("@smithy/smithy-client").CommandImpl; new (input: DeleteOrganizationConformancePackCommandInput): import("@smithy/smithy-client").CommandImpl; getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions; }; /** *

Deletes the specified organization conformance pack and all of the Config rules and remediation actions from * all member accounts in that organization.

*

Only a management account or a delegated administrator account can delete an organization conformance pack. * When calling this API with a delegated administrator, you must ensure Organizations * ListDelegatedAdministrator permissions are added.

*

Config sets the state of a conformance pack to DELETE_IN_PROGRESS until the deletion is complete. * You cannot update a conformance pack while it is in this state.

* *

* Recommendation: Consider excluding the AWS::Config::ResourceCompliance resource type from recording before deleting rules *

*

Deleting rules creates configuration items (CIs) for AWS::Config::ResourceCompliance * that can affect your costs for the configuration recorder. If you are deleting rules which evaluate a large number of resource types, * this can lead to a spike in the number of CIs recorded.

*

To avoid the associated costs, you can opt to disable recording * for the AWS::Config::ResourceCompliance resource type before deleting rules, and re-enable recording after the rules have been deleted.

*

However, since deleting rules is an asynchronous process, it might take an hour or more to complete. During the time * when recording is disabled for AWS::Config::ResourceCompliance, rule evaluations will not be recorded in the associated resource’s history.

*
* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript * import { ConfigServiceClient, DeleteOrganizationConformancePackCommand } from "@aws-sdk/client-config-service"; // ES Modules import * // const { ConfigServiceClient, DeleteOrganizationConformancePackCommand } = require("@aws-sdk/client-config-service"); // CommonJS import * // import type { ConfigServiceClientConfig } from "@aws-sdk/client-config-service"; * const config = {}; // type is ConfigServiceClientConfig * const client = new ConfigServiceClient(config); * const input = { // DeleteOrganizationConformancePackRequest * OrganizationConformancePackName: "STRING_VALUE", // required * }; * const command = new DeleteOrganizationConformancePackCommand(input); * const response = await client.send(command); * // {}; * * ``` * * @param DeleteOrganizationConformancePackCommandInput - {@link DeleteOrganizationConformancePackCommandInput} * @returns {@link DeleteOrganizationConformancePackCommandOutput} * @see {@link DeleteOrganizationConformancePackCommandInput} for command's `input` shape. * @see {@link DeleteOrganizationConformancePackCommandOutput} for command's `response` shape. * @see {@link ConfigServiceClientResolvedConfig | config} for ConfigServiceClient's `config` shape. * * @throws {@link NoSuchOrganizationConformancePackException} (client fault) *

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.

* * @throws {@link OrganizationAccessDeniedException} (client fault) *

For PutConfigurationAggregator API, you can see this exception for the following reasons:

* *

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

* * @throws {@link ResourceInUseException} (client fault) *

You see this exception in the following cases:

* * * @throws {@link ConfigServiceServiceException} *

Base exception class for all service exceptions from ConfigService service.

* * * @public */ export declare class DeleteOrganizationConformancePackCommand extends DeleteOrganizationConformancePackCommand_base { /** @internal type navigation helper, not in runtime. */ protected static __types: { api: { input: DeleteOrganizationConformancePackRequest; output: {}; }; sdk: { input: DeleteOrganizationConformancePackCommandInput; output: DeleteOrganizationConformancePackCommandOutput; }; }; }