import { Command as $Command } from "@aws-sdk/smithy-client"; import { Handler, HttpHandlerOptions as __HttpHandlerOptions, MetadataBearer as __MetadataBearer, MiddlewareStack } from "@aws-sdk/types"; import { PutBucketAnalyticsConfigurationRequest } from "../models/models_0"; import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; export interface PutBucketAnalyticsConfigurationCommandInput extends PutBucketAnalyticsConfigurationRequest { } export interface PutBucketAnalyticsConfigurationCommandOutput extends __MetadataBearer { } /** *

Sets an analytics configuration for the bucket (specified by the analytics configuration * ID). You can have up to 1,000 analytics configurations per bucket.

* *

You can choose to have storage class analysis export analysis reports sent to a * comma-separated values (CSV) flat file. See the DataExport request element. * Reports are updated daily and are based on the object filters that you configure. When * selecting data export, you specify a destination bucket and an optional destination prefix * where the file is written. You can export the data to a destination bucket in a different * account. However, the destination bucket must be in the same Region as the bucket that you * are making the PUT analytics configuration to. For more information, see Amazon S3 Analytics – Storage Class * Analysis.

* * *

You must create a bucket policy on the destination bucket where the exported file is * written to grant permissions to Amazon S3 to write objects to the bucket. For an example * policy, see Granting Permissions for Amazon S3 Inventory and Storage Class Analysis.

* * *

To use this operation, you must have permissions to perform the * s3:PutAnalyticsConfiguration action. The bucket owner has this permission * by default. The bucket owner can grant this permission to others. For more information * about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 * Resources.

* * *

* Special Errors *

*
- *
  * HTTP Error: HTTP 400 Bad Request *
  *
- *
  * Code: InvalidArgument *
  *
- *
  * Cause: Invalid argument. *
  *
*
*
- *
  * HTTP Error: HTTP 400 Bad Request *
  *
- *
  * Code: TooManyConfigurations *
  *
- *
  * Cause: You are attempting to create a new configuration but have * already reached the 1,000-configuration limit. *
  *
*
*
- *
  * HTTP Error: HTTP 403 Forbidden *
  *
- *
  * Code: AccessDenied *
  *
- *
  * Cause: You are not the owner of the specified bucket, or you do * not have the s3:PutAnalyticsConfiguration bucket permission to set the * configuration on the bucket. *
  *
*

* * * * * * *

* Related Resources *

*
* GetBucketAnalyticsConfiguration *
*
*
* DeleteBucketAnalyticsConfiguration *
*
*
* ListBucketAnalyticsConfigurations *
*

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript * import { S3Client, PutBucketAnalyticsConfigurationCommand } from "@aws-sdk/client-s3"; // ES Modules import * // const { S3Client, PutBucketAnalyticsConfigurationCommand } = require("@aws-sdk/client-s3"); // CommonJS import * const client = new S3Client(config); * const command = new PutBucketAnalyticsConfigurationCommand(input); * const response = await client.send(command); * ``` * * @see {@link PutBucketAnalyticsConfigurationCommandInput} for command's `input` shape. * @see {@link PutBucketAnalyticsConfigurationCommandOutput} for command's `response` shape. * @see {@link S3ClientResolvedConfig | config} for S3Client's `config` shape. * */ export declare class PutBucketAnalyticsConfigurationCommand extends $Command { readonly input: PutBucketAnalyticsConfigurationCommandInput; constructor(input: PutBucketAnalyticsConfigurationCommandInput); /** * @internal */ resolveMiddleware(clientStack: MiddlewareStack, configuration: S3ClientResolvedConfig, options?: __HttpHandlerOptions): Handler; private serialize; private deserialize; }