UpdateDataRepositoryAssociation - Amazon FSx

UpdateDataRepositoryAssociation

Updates the configuration of an existing data repository association on an Amazon FSx for Lustre file system. Data repository associations are supported only for file systems with the Persistent_2 deployment type.

Request Syntax

{ "AssociationId": "string", "ClientRequestToken": "string", "ImportedFileChunkSize": number, "S3": { "AutoExportPolicy": { "Events": [ "string" ] }, "AutoImportPolicy": { "Events": [ "string" ] } } }

Request Parameters

For information about the parameters that are common to all actions, see Common Parameters.

The request accepts the following data in JSON format.

AssociationId

The ID of the data repository association that you are updating.

Type: String

Length Constraints: Minimum length of 13. Maximum length of 23.

Pattern: ^(dra-[0-9a-f]{8,})$

Required: Yes

ClientRequestToken

(Optional) An idempotency token for resource creation, in a string of up to 64 ASCII characters. This token is automatically filled on your behalf when you use the AWS Command Line Interface (AWS CLI) or an AWS SDK.

Type: String

Length Constraints: Minimum length of 1. Maximum length of 63.

Pattern: [A-za-z0-9_.-]{0,63}$

Required: No

ImportedFileChunkSize

For files imported from a data repository, this value determines the stripe count and maximum amount of data per file (in MiB) stored on a single physical disk. The maximum number of disks that a single file can be striped across is limited by the total number of disks that make up the file system.

The default chunk size is 1,024 MiB (1 GiB) and can go as high as 512,000 MiB (500 GiB). Amazon S3 objects have a maximum size of 5 TB.

Type: Integer

Valid Range: Minimum value of 1. Maximum value of 512000.

Required: No

S3

The configuration for an Amazon S3 data repository linked to an Amazon FSx Lustre file system with a data repository association. The configuration defines which file events (new, changed, or deleted files or directories) are automatically imported from the linked data repository to the file system or automatically exported from the file system to the data repository.

Type: S3DataRepositoryConfiguration object

Required: No

Response Syntax

{ "Association": { "AssociationId": "string", "BatchImportMetaDataOnCreate": boolean, "CreationTime": number, "DataRepositoryPath": "string", "FailureDetails": { "Message": "string" }, "FileSystemId": "string", "FileSystemPath": "string", "ImportedFileChunkSize": number, "Lifecycle": "string", "ResourceARN": "string", "S3": { "AutoExportPolicy": { "Events": [ "string" ] }, "AutoImportPolicy": { "Events": [ "string" ] } }, "Tags": [ { "Key": "string", "Value": "string" } ] } }

Response Elements

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.

Association

The response object returned after the data repository association is updated.

Type: DataRepositoryAssociation object

Errors

For information about the errors that are common to all actions, see Common Errors.

BadRequest

A generic error indicating a failure with a client request.

HTTP Status Code: 400

DataRepositoryAssociationNotFound

No data repository associations were found based upon the supplied parameters.

HTTP Status Code: 400

IncompatibleParameterError

The error returned when a second request is received with the same client request token but different parameters settings. A client request token should always uniquely identify a single request.

HTTP Status Code: 400

InternalServerError

A generic error indicating a server-side failure.

HTTP Status Code: 500

ServiceLimitExceeded

An error indicating that a particular service limit was exceeded. You can increase some service limits by contacting AWS Support.

HTTP Status Code: 400

See Also

For more information about using this API in one of the language-specific AWS SDKs, see the following: