|
461 | 461 | "DnsIpList": {
|
462 | 462 | "base": null,
|
463 | 463 | "refs": {
|
464 |
| - "CreateLocationSmbRequest$DnsIpAddresses": "<p>Specifies the IPv4 addresses for the DNS servers that your SMB file server belongs to. This parameter applies only if <code>AuthenticationType</code> is set to <code>KERBEROS</code>.</p> <p>If you have multiple domains in your environment, configuring this parameter makes sure that DataSync connects to the right SMB file server.</p>", |
465 |
| - "DescribeLocationSmbResponse$DnsIpAddresses": "<p>The IPv4 addresses for the DNS servers that your SMB file server belongs to. This element applies only if <code>AuthenticationType</code> is set to <code>KERBEROS</code>.</p>", |
466 |
| - "UpdateLocationSmbRequest$DnsIpAddresses": "<p>Specifies the IPv4 addresses for the DNS servers that your SMB file server belongs to. This parameter applies only if <code>AuthenticationType</code> is set to <code>KERBEROS</code>.</p> <p>If you have multiple domains in your environment, configuring this parameter makes sure that DataSync connects to the right SMB file server. </p>" |
| 464 | + "CreateLocationSmbRequest$DnsIpAddresses": "<p>Specifies the IPv4 or IPv6 addresses for the DNS servers that your SMB file server belongs to. This parameter applies only if <code>AuthenticationType</code> is set to <code>KERBEROS</code>.</p> <p>If you have multiple domains in your environment, configuring this parameter makes sure that DataSync connects to the right SMB file server.</p>", |
| 465 | + "DescribeLocationSmbResponse$DnsIpAddresses": "<p>The IPv4 or IPv6 addresses for the DNS servers that your SMB file server belongs to. This element applies only if <code>AuthenticationType</code> is set to <code>KERBEROS</code>.</p>", |
| 466 | + "UpdateLocationSmbRequest$DnsIpAddresses": "<p>Specifies the IP addresses (IPv4 or IPv6) for the DNS servers that your SMB file server belongs to. This parameter applies only if <code>AuthenticationType</code> is set to <code>KERBEROS</code>.</p> <p>If you have multiple domains in your environment, configuring this parameter makes sure that DataSync connects to the right SMB file server. </p>" |
467 | 467 | }
|
468 | 468 | },
|
469 | 469 | "Duration": {
|
|
815 | 815 | "base": null,
|
816 | 816 | "refs": {
|
817 | 817 | "CreateLocationHdfsRequest$KerberosPrincipal": "<p>The Kerberos principal with access to the files and folders on the HDFS cluster. </p> <note> <p>If <code>KERBEROS</code> is specified for <code>AuthenticationType</code>, this parameter is required.</p> </note>",
|
818 |
| - "CreateLocationSmbRequest$KerberosPrincipal": "<p>Specifies a Kerberos prinicpal, which is an identity in your Kerberos realm that has permission to access the files, folders, and file metadata in your SMB file server.</p> <p>A Kerberos principal might look like <code>HOST/[email protected]</code>.</p> <p>Principal names are case sensitive. Your DataSync task execution will fail if the principal that you specify for this parameter doesn’t exactly match the principal that you use to create the keytab file.</p>", |
| 818 | + "CreateLocationSmbRequest$KerberosPrincipal": "<p>Specifies a Kerberos principal, which is an identity in your Kerberos realm that has permission to access the files, folders, and file metadata in your SMB file server.</p> <p>A Kerberos principal might look like <code>HOST/[email protected]</code>.</p> <p>Principal names are case sensitive. Your DataSync task execution will fail if the principal that you specify for this parameter doesn’t exactly match the principal that you use to create the keytab file.</p>", |
819 | 819 | "DescribeLocationHdfsResponse$KerberosPrincipal": "<p>The Kerberos principal with access to the files and folders on the HDFS cluster. This parameter is used if the <code>AuthenticationType</code> is defined as <code>KERBEROS</code>.</p>",
|
820 | 820 | "DescribeLocationSmbResponse$KerberosPrincipal": "<p>The Kerberos principal that has permission to access the files, folders, and file metadata in your SMB file server.</p>",
|
821 | 821 | "UpdateLocationHdfsRequest$KerberosPrincipal": "<p>The Kerberos principal with access to the files and folders on the HDFS cluster. </p>",
|
|
975 | 975 | "DescribeLocationObjectStorageResponse$LocationUri": "<p>The URI of the object storage system location.</p>",
|
976 | 976 | "DescribeLocationS3Response$LocationUri": "<p>The URL of the Amazon S3 location that was described.</p>",
|
977 | 977 | "DescribeLocationSmbResponse$LocationUri": "<p>The URI of the SMB location.</p>",
|
978 |
| - "LocationListEntry$LocationUri": "<p>Represents a list of URIs of a location. <code>LocationUri</code> returns an array that contains a list of locations when the <a href=\"https://docs.aws.amazon.com/datasync/latest/userguide/API_ListLocations.html\">ListLocations</a> operation is called.</p> <p>Format: <code>TYPE://GLOBAL_ID/SUBDIR</code>.</p> <p>TYPE designates the type of location (for example, <code>nfs</code> or <code>s3</code>).</p> <p>GLOBAL_ID is the globally unique identifier of the resource that backs the location. An example for EFS is <code>us-east-2.fs-abcd1234</code>. An example for Amazon S3 is the bucket name, such as <code>myBucket</code>. An example for NFS is a valid IPv4 address or a hostname that is compliant with Domain Name Service (DNS).</p> <p>SUBDIR is a valid file system path, delimited by forward slashes as is the *nix convention. For NFS and Amazon EFS, it's the export path to mount the location. For Amazon S3, it's the prefix path that you mount to and treat as the root of the location.</p> <p/>" |
| 978 | + "LocationListEntry$LocationUri": "<p>Represents a list of URIs of a location. <code>LocationUri</code> returns an array that contains a list of locations when the <a href=\"https://docs.aws.amazon.com/datasync/latest/userguide/API_ListLocations.html\">ListLocations</a> operation is called.</p> <p>Format: <code>TYPE://GLOBAL_ID/SUBDIR</code>.</p> <p>TYPE designates the type of location (for example, <code>nfs</code> or <code>s3</code>).</p> <p>GLOBAL_ID is the globally unique identifier of the resource that backs the location. An example for EFS is <code>us-east-2.fs-abcd1234</code>. An example for Amazon S3 is the bucket name, such as <code>myBucket</code>. An example for NFS is a valid IPv4 or IPv6 address or a hostname that is compliant with DNS.</p> <p>SUBDIR is a valid file system path, delimited by forward slashes as is the *nix convention. For NFS and Amazon EFS, it's the export path to mount the location. For Amazon S3, it's the prefix path that you mount to and treat as the root of the location.</p> <p/>" |
979 | 979 | }
|
980 | 980 | },
|
981 | 981 | "LogGroupArn": {
|
|
1106 | 1106 | "ObjectStorageSecretKey": {
|
1107 | 1107 | "base": null,
|
1108 | 1108 | "refs": {
|
1109 |
| - "CreateLocationObjectStorageRequest$SecretKey": "<p>Specifies the secret key (for example, a password) if credentials are required to authenticate with the object storage server.</p>", |
1110 |
| - "UpdateLocationObjectStorageRequest$SecretKey": "<p>Specifies the secret key (for example, a password) if credentials are required to authenticate with the object storage server.</p>" |
| 1109 | + "CreateLocationObjectStorageRequest$SecretKey": "<p>Specifies the secret key (for example, a password) if credentials are required to authenticate with the object storage server.</p> <note> <p>If you provide a secret using <code>SecretKey</code>, but do not provide secret configuration details using <code>CmkSecretConfig</code> or <code>CustomSecretConfig</code>, then DataSync stores the token using your Amazon Web Services account's Secrets Manager secret.</p> </note>", |
| 1110 | + "UpdateLocationObjectStorageRequest$SecretKey": "<p>Specifies the secret key (for example, a password) if credentials are required to authenticate with the object storage server.</p> <note> <p>If you provide a secret using <code>SecretKey</code>, but do not provide secret configuration details using <code>CmkSecretConfig</code> or <code>CustomSecretConfig</code>, then DataSync stores the token using your Amazon Web Services account's Secrets Manager secret.</p> </note>" |
1111 | 1111 | }
|
1112 | 1112 | },
|
1113 | 1113 | "ObjectStorageServerPort": {
|
|
1121 | 1121 | "ObjectStorageServerProtocol": {
|
1122 | 1122 | "base": null,
|
1123 | 1123 | "refs": {
|
1124 |
| - "CreateLocationObjectStorageRequest$ServerProtocol": "<p>Specifies the protocol that your object storage server uses to communicate.</p>", |
| 1124 | + "CreateLocationObjectStorageRequest$ServerProtocol": "<p>Specifies the protocol that your object storage server uses to communicate. If not specified, the default value is <code>HTTPS</code>.</p>", |
1125 | 1125 | "DescribeLocationObjectStorageResponse$ServerProtocol": "<p>The protocol that your object storage system uses to communicate.</p>",
|
1126 | 1126 | "UpdateLocationObjectStorageRequest$ServerProtocol": "<p>Specifies the protocol that your object storage server uses to communicate.</p>"
|
1127 | 1127 | }
|
|
1366 | 1366 | "ServerHostname": {
|
1367 | 1367 | "base": null,
|
1368 | 1368 | "refs": {
|
1369 |
| - "CreateLocationNfsRequest$ServerHostname": "<p>Specifies the DNS name or IP version 4 address of the NFS file server that your DataSync agent connects to.</p>", |
1370 |
| - "CreateLocationObjectStorageRequest$ServerHostname": "<p>Specifies the domain name or IP version 4 (IPv4) address of the object storage server that your DataSync agent connects to.</p>", |
1371 |
| - "CreateLocationSmbRequest$ServerHostname": "<p>Specifies the domain name or IP address of the SMB file server that your DataSync agent connects to.</p> <p>Remember the following when configuring this parameter:</p> <ul> <li> <p>You can't specify an IP version 6 (IPv6) address.</p> </li> <li> <p>If you're using Kerberos authentication, you must specify a domain name.</p> </li> </ul>", |
1372 |
| - "UpdateLocationNfsRequest$ServerHostname": "<p>Specifies the DNS name or IP version 4 (IPv4) address of the NFS file server that your DataSync agent connects to.</p>", |
1373 |
| - "UpdateLocationObjectStorageRequest$ServerHostname": "<p>Specifies the domain name or IP version 4 (IPv4) address of the object storage server that your DataSync agent connects to.</p>", |
1374 |
| - "UpdateLocationSmbRequest$ServerHostname": "<p>Specifies the domain name or IP address of the SMB file server that your DataSync agent connects to.</p> <p>Remember the following when configuring this parameter:</p> <ul> <li> <p>You can't specify an IP version 6 (IPv6) address.</p> </li> <li> <p>If you're using Kerberos authentication, you must specify a domain name.</p> </li> </ul>" |
| 1369 | + "CreateLocationNfsRequest$ServerHostname": "<p>Specifies the DNS name or IP address (IPv4 or IPv6) of the NFS file server that your DataSync agent connects to.</p>", |
| 1370 | + "CreateLocationObjectStorageRequest$ServerHostname": "<p>Specifies the domain name or IP address (IPv4 or IPv6) of the object storage server that your DataSync agent connects to.</p>", |
| 1371 | + "CreateLocationSmbRequest$ServerHostname": "<p>Specifies the domain name or IP address (IPv4 or IPv6) of the SMB file server that your DataSync agent connects to.</p> <note> <p>If you're using Kerberos authentication, you must specify a domain name.</p> </note>", |
| 1372 | + "UpdateLocationNfsRequest$ServerHostname": "<p>Specifies the DNS name or IP address (IPv4 or IPv6) of the NFS file server that your DataSync agent connects to.</p>", |
| 1373 | + "UpdateLocationObjectStorageRequest$ServerHostname": "<p>Specifies the domain name or IP address (IPv4 or IPv6) of the object storage server that your DataSync agent connects to.</p>", |
| 1374 | + "UpdateLocationSmbRequest$ServerHostname": "<p>Specifies the domain name or IP address (IPv4 or IPv6) of the SMB file server that your DataSync agent connects to.</p> <note> <p>If you're using Kerberos authentication, you must specify a domain name.</p> </note>" |
1375 | 1375 | }
|
1376 | 1376 | },
|
1377 | 1377 | "ServerIpAddress": {
|
|
0 commit comments