| _key | core | string | |
| account_id | core | string | |
| association_id | core | string | The system-generated, unique ID of the data repository association. |
| batch_import_meta_data_on_create | core | bool | A boolean flag indicating whether an import data repository task to import metadata should run after the data repository association is created. The task runs if this flag is set to <code>true</code>. <note> <code>BatchImportMetaDataOnCreate</code> is not supported for data repositories linked to an Amazon File Cache resource. </note> |
| creation_time | core | timestamp | |
| data_repository_path | core | string | The path to the data repository that will be linked to the cache or file system. <ul> <li> For Amazon File Cache, the path can be an NFS data repository that will be linked to the cache. The path can be in one of two formats: <ul> <li> If you are not using the <code>DataRepositorySubdirectories</code> parameter, the path is to an NFS Export directory (or one of its subdirectories) in the format <code>nsf://nfs-domain-name/exportpath</code>. You can therefore link a single NFS Export to a single data repository association. </li> <li> If you are using the <code>DataRepositorySubdirectories</code> parameter, the path is the domain name of the NFS file system in the format <code>nfs://filer-domain-name</code>, which indicates the root of the subdirectories specified with the <code>DataRepositorySubdirectories</code> parameter. </li> </ul> </li> <li> For Amazon File Cache, the path can be an S3 bucket or prefix in the format <code>s3://bucket-name/prefix/</code> (where <code>prefix</code> is optional). </li> <li> For Amazon FSx for Lustre, the path can be an S3 bucket or prefix in the format <code>s3://bucket-name/prefix/</code> (where <code>prefix</code> is optional). </li> </ul> |
| data_repository_subdirectories | core | array<string> | For Amazon File Cache, a list of NFS Exports that will be linked with an NFS data repository association. All the subdirectories must be on a single NFS file system. The Export paths are in the format <code>/exportpath1</code>. To use this parameter, you must configure <code>DataRepositoryPath</code> as the domain name of the NFS file system. The NFS file system domain name in effect is the root of the subdirectories. Note that <code>DataRepositorySubdirectories</code> is not supported for S3 data repositories. |
| failure_details | core | json | |
| file_cache_id | core | string | The globally unique ID of the Amazon File Cache resource. |
| file_cache_path | core | string | A path on the Amazon File Cache that points to a high-level directory (such as <code>/ns1/</code>) or subdirectory (such as <code>/ns1/subdir/</code>) that will be mapped 1-1 with <code>DataRepositoryPath</code>. The leading forward slash in the path is required. Two data repository associations cannot have overlapping cache paths. For example, if a data repository is associated with cache path <code>/ns1/</code>, then you cannot link another data repository with cache path <code>/ns1/ns2</code>. This path specifies the directory in your cache where files will be exported from. This cache directory can be linked to only one data repository (S3 or NFS) and no other data repository can be linked to the directory. <note> The cache path can only be set to root (/) on an NFS DRA when <code>DataRepositorySubdirectories</code> is specified. If you specify root (/) as the cache path, you can create only one DRA on the cache. The cache path cannot be set to root (/) for an S3 DRA. </note> |
| file_system_id | core | string | |
| file_system_path | core | string | A path on the Amazon FSx for Lustre file system that points to a high-level directory (such as <code>/ns1/</code>) or subdirectory (such as <code>/ns1/subdir/</code>) that will be mapped 1-1 with <code>DataRepositoryPath</code>. The leading forward slash in the name is required. Two data repository associations cannot have overlapping file system paths. For example, if a data repository is associated with file system path <code>/ns1/</code>, then you cannot link another data repository with file system path <code>/ns1/ns2</code>. This path specifies where in your file system files will be exported from or imported to. This file system directory can be linked to only one Amazon S3 bucket, and no other S3 bucket can be linked to the directory. <note> If you specify only a forward slash (<code>/</code>) as the file system path, you can link only one data repository to the file system. You can only specify "/" as the file system path for the first data repository associated with a file system. </note> |
| imported_file_chunk_size | core | int64 | 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 or cache. 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. |
| lifecycle | core | string | Describes the state of a data repository association. The lifecycle can have the following values: <ul> <li> <code>CREATING</code> - The data repository association between the file system or cache and the data repository is being created. The data repository is unavailable. </li> <li> <code>AVAILABLE</code> - The data repository association is available for use. </li> <li> <code>MISCONFIGURED</code> - The data repository association is misconfigured. Until the configuration is corrected, automatic import and automatic export will not work (only for Amazon FSx for Lustre). </li> <li> <code>UPDATING</code> - The data repository association is undergoing a customer initiated update that might affect its availability. </li> <li> <code>DELETING</code> - The data repository association is undergoing a customer initiated deletion. </li> <li> <code>FAILED</code> - The data repository association is in a terminal state that cannot be recovered. </li> </ul> |
| nfs | core | json | The configuration for an NFS data repository linked to an Amazon File Cache resource with a data repository association. |
| resource_arn | core | string | |
| s3 | core | json | The configuration for an Amazon S3 data repository linked to an Amazon FSx for Lustre file system with a data repository association. |
| tags | core | hstore | |
