AWS DataSync is a managed data transfer service that makes it simpler for you to automate moving data between on-premises storage and Amazon Simple Storage Service (Amazon S3) or Amazon Elastic File System (Amazon EFS).
This API interface reference for AWS DataSync contains documentation for a programming interface that you can use to manage AWS DataSync.
", "operations": { - "CancelTaskExecution": "Cancels execution of a task.
When you cancel a task execution, the transfer of some files are abruptly interrupted. The contents of files that are transferred to the destination might be incomplete or inconsistent with the source files. However, if you start a new task execution on the same task and you allow the task execution to complete, file content on the destination is complete and consistent. This applies to other unexpected failures that interrupt a task execution. In all of these cases, AWS DataSync successfully complete the transfer when you start the next task execution.
", - "CreateAgent": "Activates an AWS DataSync agent that you have deployed on your host. The activation process associates your agent with your account. In the activation process, you specify information such as the AWS Region that you want to activate the agent in. You activate the agent in the AWS Region where your target locations (in Amazon S3 or Amazon EFS) reside. Your tasks are created in this AWS Region.
You can use an agent for more than one location. If a task uses multiple agents, all of them need to have status AVAILABLE for the task to run. If you use multiple agents for a source location, the status of all the agents must be AVAILABLE for the task to run. For more information, see Activating a Sync Agent in the AWS DataSync User Guide.
Agents are automatically updated by AWS on a regular basis, using a mechanism that ensures minimal interruption to your tasks.
", + "CancelTaskExecution": "Cancels execution of a task.
When you cancel a task execution, the transfer of some files are abruptly interrupted. The contents of files that are transferred to the destination might be incomplete or inconsistent with the source files. However, if you start a new task execution on the same task and you allow the task execution to complete, file content on the destination is complete and consistent. This applies to other unexpected failures that interrupt a task execution. In all of these cases, AWS DataSync successfully complete the transfer when you start the next task execution.
", + "CreateAgent": "Activates an AWS DataSync agent that you have deployed on your host. The activation process associates your agent with your account. In the activation process, you specify information such as the AWS Region that you want to activate the agent in. You activate the agent in the AWS Region where your target locations (in Amazon S3 or Amazon EFS) reside. Your tasks are created in this AWS Region.
You can use an agent for more than one location. If a task uses multiple agents, all of them need to have status AVAILABLE for the task to run. If you use multiple agents for a source location, the status of all the agents must be AVAILABLE for the task to run.
For more information, see \"https://docs.aws.amazon.com/datasync/latest/userguide/working-with-agents.html#activating-agent\" (Activating an Agent) in the AWS DataSync User Guide.
Agents are automatically updated by AWS on a regular basis, using a mechanism that ensures minimal interruption to your tasks.
", "CreateLocationEfs": "Creates an endpoint for an Amazon EFS file system.
", "CreateLocationNfs": "Creates an endpoint for a Network File System (NFS) file system.
", - "CreateLocationS3": "Creates an endpoint for an Amazon S3 bucket.
For AWS DataSync to access a destination S3 bucket, it needs an AWS Identity and Access Management (IAM) role that has the required permissions. You can set up the required permissions by creating an IAM policy that grants the required permissions and attaching the policy to the role. An example of such a policy is shown in the examples section. For more information, see Configuring Amazon S3 Location Settings in the AWS DataSync User Guide.
", - "CreateTask": "Creates a task. A task is a set of two locations (source and destination) and a set of default OverrideOptions that you use to control the behavior of a task. If you don't specify default values for Options when you create a task, AWS DataSync populates them with safe service defaults.
When you initially create a task, it enters the INITIALIZING status and then the CREATING status. In CREATING status, AWS DataSync attempts to mount the source Network File System (NFS) location. The task transitions to the AVAILABLE status without waiting for the destination location to mount. Instead, AWS DataSync mounts a destination before every task execution and then unmounts it after every task execution.
If an agent that is associated with a source (NFS) location goes offline, the task transitions to the UNAVAILABLE status. If the status of the task remains in the CREATING status for more than a few minutes, it means that your agent might be having trouble mounting the source NFS file system. Check the task's ErrorCode and ErrorDetail. Mount issues are often caused by either a misconfigured firewall or a mistyped NFS server host name.
Deletes an agent. To specify which agent to delete, use the Amazon Resource Name (ARN) of the agent in your request. The operation disassociates the agent from your AWS account. However, it doesn't delete the agent virtual machine (VM) from your on-premises environment.
After you delete an agent, you can't reactivate it and you longer pay software charges for it.
Creates an endpoint for an Amazon S3 bucket.
For AWS DataSync to access a destination S3 bucket, it needs an AWS Identity and Access Management (IAM) role that has the required permissions. You can set up the required permissions by creating an IAM policy that grants the required permissions and attaching the policy to the role. An example of such a policy is shown in the examples section.
For more information, see \"https://docs.aws.amazon.com/datasync/latest/userguide/working-with-locations.html#create-s3-location\" (Configuring Amazon S3 Location Settings) in the AWS DataSync User Guide.
", + "CreateTask": "Creates a task. A task is a set of two locations (source and destination) and a set of Options that you use to control the behavior of a task. If you don't specify Options when you create a task, AWS DataSync populates them with service defaults.
When you create a task, it first enters the CREATING state. During CREATING AWS DataSync attempts to mount the on-premises Network File System (NFS) location. The task transitions to the AVAILABLE state without waiting for the AWS location to become mounted. If required, AWS DataSync mounts the AWS location before each task execution.
If an agent that is associated with a source (NFS) location goes offline, the task transitions to the UNAVAILABLE status. If the status of the task remains in the CREATING status for more than a few minutes, it means that your agent might be having trouble mounting the source NFS file system. Check the task's ErrorCode and ErrorDetail. Mount issues are often caused by either a misconfigured firewall or a mistyped NFS server host name.
", + "DeleteAgent": "Deletes an agent. To specify which agent to delete, use the Amazon Resource Name (ARN) of the agent in your request. The operation disassociates the agent from your AWS account. However, it doesn't delete the agent virtual machine (VM) from your on-premises environment.
", "DeleteLocation": "Deletes the configuration of a location used by AWS DataSync.
", "DeleteTask": "Deletes a task.
", "DescribeAgent": "Returns metadata such as the name, the network interfaces, and the status (that is, whether the agent is running or not) for an agent. To specify which agent to describe, use the Amazon Resource Name (ARN) of the agent in your request.
", @@ -22,7 +22,7 @@ "ListTagsForResource": "Returns all the tags associated with a specified resources.
", "ListTaskExecutions": "Returns a list of executed tasks.
", "ListTasks": "Returns a list of all the tasks.
", - "StartTaskExecution": "Starts a specific invocation of a task. A TaskExecution value represents an individual run of a task. Each task can have at most one TaskExecution at a time.
TaskExecution has the following transition phases: INITIALIZING | PREPARING | TRANSFERRING | VERIFYING | SUCCESS/FAILURE.
For detailed information, see Task Execution in Components and Terminology in the AWS DataSync User Guide.
", + "StartTaskExecution": "Starts a specific invocation of a task. A TaskExecution value represents an individual run of a task. Each task can have at most one TaskExecution at a time.
TaskExecution has the following transition phases: INITIALIZING | PREPARING | TRANSFERRING | VERIFYING | SUCCESS/FAILURE.
For detailed information, see Task Execution in \"https://docs.aws.amazon.com/datasync/latest/userguide/how-datasync-works.html#terminology\" (Components and Terminology) in the AWS DataSync User Guide.
", "TagResource": "Applies a key-value pair to an AWS resource.
", "UntagResource": "Removes a tag from an AWS resource.
", "UpdateAgent": "Updates the name of an agent.
", @@ -32,7 +32,7 @@ "ActivationKey": { "base": null, "refs": { - "CreateAgentRequest$ActivationKey": "Your agent activation key. You can get the activation key either by sending an HTTP GET request with redirects that enable you to get the agent IP address (port 80). Alternatively, you can get it from the AWS DataSync console.
The redirect URL returned in the response provides you the activation key for your agent in the query string parameter activationKey. It might also include other activation-related parameters; however, these are merely defaults. The arguments you pass to this API call determine the actual configuration of your agent. For more information, see Activating a Sync Agent in the AWS DataSync User Guide.
Your agent activation key. You can get the activation key either by sending an HTTP GET request with redirects that enable you to get the agent IP address (port 80). Alternatively, you can get it from the AWS DataSync console.
The redirect URL returned in the response provides you the activation key for your agent in the query string parameter activationKey. It might also include other activation-related parameters; however, these are merely defaults. The arguments you pass to this API call determine the actual configuration of your agent.
For more information, see \"https://docs.aws.amazon.com/datasync/latest/userguide/working-with-agents.html#activating-agent\" (Activating a Agent) in the AWS DataSync User Guide.
" } }, "AgentArn": { @@ -243,9 +243,9 @@ } }, "Ec2Config": { - "base": "The subnet and the security group that the target Amazon EFS file system uses. The subnet must have at least one mount target for that file system. The security group that you provide needs to be able to communicate with the security group on the mount target in the subnet specified.
The exact relationship between security group M (of the mount target) and security group S (which you provide for DataSync to use at this stage) is as follows:
Security group M (which you associate with the mount target) must allow inbound access for the Transmission Control Protocol (TCP) on the NFS port (2049) from security group S. You can enable inbound connections either by IP address (CIDR range) or security group.
Security group S (provided to DataSync to access EFS) should have a rule that enables outbound connections to the NFS port on one of the file system’s mount targets. You can enable outbound connections either by IP address (CIDR range) or security group. For information about security groups and mount targets, see Security Groups for Amazon EC2 Instances and Mount Targets in the Amazon EFS User Guide.
The subnet and the security group that DataSync uses to access target EFS file system. The subnet must have at least one mount target for that file system. The security group that you provide needs to be able to communicate with the security group on the mount target in the subnet specified.
", "refs": { - "CreateLocationEfsRequest$Ec2Config": "The subnet and security group that the Amazon EFS file system uses.
", + "CreateLocationEfsRequest$Ec2Config": "The subnet and security group that the Amazon EFS file system uses. The security group that you provide needs to be able to communicate with the security group on the mount target in the subnet specified.
The exact relationship between security group M (of the mount target) and security group S (which you provide for DataSync to use at this stage) is as follows:
Security group M (which you associate with the mount target) must allow inbound access for the Transmission Control Protocol (TCP) on the NFS port (2049) from security group S. You can enable inbound connections either by IP address (CIDR range) or security group.
Security group S (provided to DataSync to access EFS) should have a rule that enables outbound connections to the NFS port on one of the file system’s mount targets. You can enable outbound connections either by IP address (CIDR range) or security group.
For information about security groups and mount targets, see \"https://docs.aws.amazon.com/efs/latest/ug/security-considerations.html#network-access\" (Security Groups for Amazon EC2 Instances and Mount Targets) in the Amazon EFS User Guide.
The ARN of the subnet that the Amazon EC2 resource belongs in.
" + "Ec2Config$SubnetArn": "The ARN of the subnet and the security group that DataSync uses to access the target EFS file system.
" } }, "EfsFilesystemArn": { @@ -273,6 +273,35 @@ "CreateLocationEfsRequest$EfsFilesystemArn": "The Amazon Resource Name (ARN) for the Amazon EFS file system.
" } }, + "FilterList": { + "base": null, + "refs": { + "CreateTaskRequest$Excludes": "A filter that determines which files to exclude from a task based on the specified pattern. Transfers all files in the task’s subdirectory, except files that match the filter that is set.
", + "DescribeTaskExecutionResponse$Excludes": "Specifies that the task execution excludes files from the transfer based on the specified pattern in the filter. Transfers all files in the task’s subdirectory, except files that match the filter that is set.
", + "DescribeTaskExecutionResponse$Includes": "Specifies that the task execution excludes files in the transfer based on the specified pattern in the filter. When multiple include filters are set, they are interpreted as an OR.
", + "DescribeTaskResponse$Excludes": "Specifies that the task excludes files in the transfer based on the specified pattern in the filter. Transfers all files in the task’s subdirectory, except files that match the filter that is set.
", + "StartTaskExecutionRequest$Includes": "A filter that determines which files to include in the transfer during a task execution based on the specified pattern in the filter. When multiple include filters are set, they are interpreted as an OR.
", + "UpdateTaskRequest$Excludes": "A filter that determines which files to exclude from a task based on the specified pattern in the filter. Transfers all files in the task’s subdirectory, except files that match the filter that is set.
" + } + }, + "FilterRule": { + "base": "A pattern that determines which files to include in the transfer or which files to exclude.
", + "refs": { + "FilterList$member": null + } + }, + "FilterType": { + "base": null, + "refs": { + "FilterRule$FilterType": "Specifies the type of filter rule pattern to apply. DataSync only supports the SIMPLE_PATTERN rule type.
" + } + }, + "FilterValue": { + "base": null, + "refs": { + "FilterRule$Value": "A pattern that defines the filter. The filter might include or exclude files is a transfer.
" + } + }, "Gid": { "base": null, "refs": { @@ -285,6 +314,11 @@ "S3Config$BucketAccessRoleArn": "The Amazon S3 bucket to access. This bucket is used as a parameter in the CreateLocationS3 operation.
" } }, + "InternalException": { + "base": "This exception is thrown when an error occurs in the AWS DataSync service.
", + "refs": { + } + }, "InvalidRequestException": { "base": "This exception is thrown when the client submits a malformed request.
", "refs": { @@ -384,8 +418,9 @@ "LogGroupArn": { "base": null, "refs": { - "CreateTaskRequest$CloudWatchLogGroupArn": "The Amazon Resource Name (ARN) of the Amazon CloudWatch log group that is used to monitor and log events in the task. For more information on these groups, see Working with Log Groups and Log Streams in the Amazon CloudWatch User Guide.
For more information about how to useCloudWatchLogs with DataSync, see Monitoring Your Task.
", - "DescribeTaskResponse$CloudWatchLogGroupArn": "The Amazon Resource Name (ARN) of the Amazon CloudWatch log group that was used to monitor and log events in the task. For more information on these groups, see Working with Log Groups and Log Streams in the Amazon CloudWatch User Guide.
" + "CreateTaskRequest$CloudWatchLogGroupArn": "The Amazon Resource Name (ARN) of the Amazon CloudWatch log group that is used to monitor and log events in the task.
For more information on these groups, see \"https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/Working-with-log-groups-and-streams.html\" (Working with Log Groups and Log Streams) in the Amazon CloudWatch User Guide.
For more information about how to useCloudWatchLogs with DataSync, see \"https://docs.aws.amazon.com/datasync/latest/userguide/monitor-datasync.html\" (Monitoring Your Task)
", + "DescribeTaskResponse$CloudWatchLogGroupArn": "The Amazon Resource Name (ARN) of the Amazon CloudWatch log group that was used to monitor and log events in the task.
For more information on these groups, see \"https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/Working-with-log-groups-and-streams.html\" (Working with Log Groups and Log Streams) in the Amazon CloudWatch UserGuide.
", + "UpdateTaskRequest$CloudWatchLogGroupArn": "The Amazon Resource Name (ARN) of the resource name of the CloudWatch LogGroup.
" } }, "MaxResults": { @@ -419,6 +454,25 @@ "ListTasksResponse$NextToken": "An opaque string that indicates the position at which to begin returning the next list of tasks.
" } }, + "NfsMountOptions": { + "base": "Represents the mount options that are available for DataSync to access an NFS location.
", + "refs": { + "CreateLocationNfsRequest$MountOptions": "The NFS mount options that DataSync can use to mount your NFS share.
", + "DescribeLocationNfsResponse$MountOptions": "The NFS mount options that DataSync used to mount your NFS share.
" + } + }, + "NfsVersion": { + "base": null, + "refs": { + "NfsMountOptions$Version": "The specific NFS version that you want DataSync to use to mount your NFS share. If you don't specify a version, DataSync defaults to AUTOMATIC. That is, DataSync automatically selects a version based on negotiation with the NFS server.
The subdirectory in the NFS file system that is used to read data from the NFS source location or write data to the NFS destination. The NFS path should be a path that's exported by the NFS server, or a subdirectory of that path. The path should be such that it can be mounted by other NFS clients in your network.
To see all the paths exported by your NFS server. run \"showmount -e nfs-server-name\" from an NFS client that has access to your server. You can specify any directory that appears in the results, and any subdirectory of that directory. Ensure that the NFS export is accessible without Kerberos authentication.
To transfer all the data in the folder you specified, DataSync needs to have permissions to read all the data. To ensure this, either configure the NFS export with no_root_squash, or ensure that the permissions for all of the files that you want DataSync allow read access for all users. Doing either enables the agent to read the files. For the agent to access directories, you must additionally enable all execute access.
For information about NFS export configuration, see \"http://web.mit.edu/rhel-doc/5/RHEL-5-manual/Deployment_Guide-en-US/s1-nfs-server-config-exports.html\" (18.7. The /etc/exports Configuration File).
" + } + }, "OnPremConfig": { "base": "A list of Amazon Resource Names (ARNs) of agents to use for a Network File System (NFS) location.
", "refs": { @@ -469,7 +523,7 @@ } }, "S3Config": { - "base": "The Amazon Resource Name (ARN) of the AWS Identity and Access Management (IAM) role that is used to access an Amazon S3 bucket. For detailed information about using such a role, see Components and Terminology in the AWS DataSync User Guide.
", + "base": "The Amazon Resource Name (ARN) of the AWS Identity and Access Management (IAM) role that is used to access an Amazon S3 bucket.
For detailed information about using such a role, see \"https://docs.aws.amazon.com/datasync/latest/userguide/working-with-locations.html#create-s3-location\" (Creating a Location for Amazon S3) in the AWS DataSync User Guide.
", "refs": { "CreateLocationS3Request$S3Config": null, "DescribeLocationS3Response$S3Config": null @@ -495,7 +549,6 @@ "base": null, "refs": { "CreateLocationEfsRequest$Subdirectory": "A subdirectory in the location’s path. This subdirectory in the EFS file system is used to read data from the EFS source location or write data to the EFS destination. By default, AWS DataSync uses the root directory.
", - "CreateLocationNfsRequest$Subdirectory": "The subdirectory in the NFS file system that is used to read data from the NFS source location or write data to the NFS destination. The NFS path should be a path that's exported by the NFS server, or a subdirectory of that path. The path should be such that it can be mounted by other NFS clients in your network.
To see all the paths exported by your NFS server. run \"showmount -e nfs-server-name\" from an NFS client that has access to your server. You can specify any directory that appears in the results, and any subdirectory of that directory. Ensure that the NFS export is accessible without Kerberos authentication.
To transfer all the data in the folder you specified, DataSync needs to have permissions to read all the data. To ensure this, either configure the NFS export with no_root_squash, or ensure that the permissions for all of the files that you want sync allow read access for all users. Doing either enables the agent to read the files. For the agent to access directories, you must additionally enable all execute access. For information about NFS export configuration, see 18.7. The /etc/exports Configuration File in the Centos documentation.
A subdirectory in the Amazon S3 bucket. This subdirectory in Amazon S3 is used to read data from the S3 source location or write data to the S3 destination.
" } }, @@ -515,7 +568,7 @@ "TagList": { "base": null, "refs": { - "CreateAgentRequest$Tags": "The key-value pair that represents the tag you want to associate with the agent. The value can be an empty string. This value helps you manage, filter, and search for your agents.
Valid characters for key and value are letters, spaces, and numbers representable in UTF-8 format, and the following special characters: + - = . _ : / @.
The key-value pair that represents the tag that you want to associate with the agent. The value can be an empty string. This value helps you manage, filter, and search for your agents.
Valid characters for key and value are letters, spaces, and numbers representable in UTF-8 format, and the following special characters: + - = . _ : / @.
The key-value pair that represents a tag that you want to add to the resource. The value can be an empty string. This value helps you manage, filter, and search for your resources. We recommend that you create a name tag for your location.
", "CreateLocationNfsRequest$Tags": "The key-value pair that represents the tag that you want to add to the location. The value can be an empty string. We recommend using tags to name your resources.
", "CreateLocationS3Request$Tags": "The key-value pair that represents the tag that you want to add to the location. The value can be an empty string. We recommend using tags to name your resources.
", @@ -580,7 +633,7 @@ "refs": { "CancelTaskExecutionRequest$TaskExecutionArn": "The Amazon Resource Name (ARN) of the task execution to cancel.
", "DescribeTaskExecutionRequest$TaskExecutionArn": "The Amazon Resource Name (ARN) of the task that is being executed.
", - "DescribeTaskExecutionResponse$TaskExecutionArn": "The Amazon Resource Name (ARN) of the task execution that was described. TaskExecutionArn is hierarchical and includes TaskArn for the task that was executed.
For example, a TaskExecution value with the ARN arn:aws:sync:us-east-1:209870788375:task/task-0208075f79cedf4a2/execution/exec-08ef1e88ec491019b executed the task with the ARN arn:aws:sync:us-east-1:209870788375:task/task-0208075f79cedf4a2.
The Amazon Resource Name (ARN) of the task execution that was described. TaskExecutionArn is hierarchical and includes TaskArn for the task that was executed.
For example, a TaskExecution value with the ARN arn:aws:datasync:us-east-1:111222333444:task/task-0208075f79cedf4a2/execution/exec-08ef1e88ec491019b executed the task with the ARN arn:aws:datasync:us-east-1:111222333444:task/task-0208075f79cedf4a2.
The Amazon Resource Name (ARN) of the task execution that is syncing files.
", "StartTaskExecutionResponse$TaskExecutionArn": "The Amazon Resource Name (ARN) of the specific task execution that was started.
", "TaskExecutionListEntry$TaskExecutionArn": "The Amazon Resource Name (ARN) of the task that was executed.
" @@ -607,7 +660,7 @@ "TaskExecutionStatus": { "base": null, "refs": { - "DescribeTaskExecutionResponse$Status": "The status of the task. For detailed information about sync statuses, see Understanding Sync Task Statuses.
", + "DescribeTaskExecutionResponse$Status": "The status of the task execution.
For detailed information about task execution statuses, see \"https://docs.aws.amazon.com/datasync/latest/userguide/working-with-tasks.html#understand-task-creation-statuses\" (Understanding Task Statuses).
", "TaskExecutionListEntry$Status": "The status of a task execution.
" } }, @@ -626,14 +679,14 @@ "TaskStatus": { "base": null, "refs": { - "DescribeTaskResponse$Status": "The status of the task that was described. For detailed information about sync statuses, see Understanding Sync Task Statuses.
", + "DescribeTaskResponse$Status": "The status of the task that was described.
For detailed information about task execution statuses, see \"https://docs.aws.amazon.com/datasync/latest/userguide/working-with-tasks.html#understand-task-creation-statuses\" (Understanding Task Statuses).
", "TaskListEntry$Status": "The status of the task.
" } }, "Time": { "base": null, "refs": { - "DescribeAgentResponse$LastConnectionTime": "The time that the agent was last connected.
", + "DescribeAgentResponse$LastConnectionTime": "The time that the agent last connected to DataSyc.
", "DescribeAgentResponse$CreationTime": "The time that the agent was activated (that is, created in your account).
", "DescribeLocationEfsResponse$CreationTime": "The time that the EFS location was created.
", "DescribeLocationNfsResponse$CreationTime": "The time that the NFS location was created.
", @@ -699,6 +752,8 @@ "refs": { "DescribeTaskResponse$ErrorCode": "Errors that AWS DataSync encountered during execution of the task. You can use this error code to help troubleshoot issues.
", "DescribeTaskResponse$ErrorDetail": "Detailed description of an error that was encountered during the task execution. You can use this information to help troubleshoot issues.
", + "InternalException$message": null, + "InternalException$errorCode": null, "InvalidRequestException$message": null, "InvalidRequestException$errorCode": null, "TaskExecutionResultDetail$ErrorCode": "Errors that AWS DataSync encountered during execution of the task. You can use this error code to help troubleshoot issues.
", diff --git a/aws-sdk-core/apis/iotanalytics/2017-11-27/api-2.json b/aws-sdk-core/apis/iotanalytics/2017-11-27/api-2.json index b748111b3de..f9693a182ff 100644 --- a/aws-sdk-core/apis/iotanalytics/2017-11-27/api-2.json +++ b/aws-sdk-core/apis/iotanalytics/2017-11-27/api-2.json @@ -631,6 +631,18 @@ "batchPutMessageErrorEntries":{"shape":"BatchPutMessageErrorEntries"} } }, + "BucketKeyExpression":{ + "type":"string", + "max":255, + "min":1, + "pattern":"^[a-zA-Z0-9!_.*'()/{}:-]*$" + }, + "BucketName":{ + "type":"string", + "max":255, + "min":3, + "pattern":"^[a-zA-Z0-9.\\-_]*$" + }, "CancelPipelineReprocessingRequest":{ "type":"structure", "required":[ @@ -886,7 +898,8 @@ "DatasetContentDeliveryDestination":{ "type":"structure", "members":{ - "iotEventsDestinationConfiguration":{"shape":"IotEventsDestinationConfiguration"} + "iotEventsDestinationConfiguration":{"shape":"IotEventsDestinationConfiguration"}, + "s3DestinationConfiguration":{"shape":"S3DestinationConfiguration"} } }, "DatasetContentDeliveryRule":{ @@ -1299,6 +1312,29 @@ "status":{"shape":"DatasetContentStatus"} } }, + "GlueConfiguration":{ + "type":"structure", + "required":[ + "tableName", + "databaseName" + ], + "members":{ + "tableName":{"shape":"GlueTableName"}, + "databaseName":{"shape":"GlueDatabaseName"} + } + }, + "GlueDatabaseName":{ + "type":"string", + "max":150, + "min":1, + "pattern":"[\\u0020-\\uD7FF\\uE000-\\uFFFD\\uD800\\uDC00-\\uDBFF\\uDFFF\\t]*" + }, + "GlueTableName":{ + "type":"string", + "max":150, + "min":1, + "pattern":"[\\u0020-\\uD7FF\\uE000-\\uFFFD\\uD800\\uDC00-\\uDBFF\\uDFFF\\t]*" + }, "Image":{ "type":"string", "max":255 @@ -1777,6 +1813,20 @@ "logResult":{"shape":"LogResult"} } }, + "S3DestinationConfiguration":{ + "type":"structure", + "required":[ + "bucket", + "key", + "roleArn" + ], + "members":{ + "bucket":{"shape":"BucketName"}, + "key":{"shape":"BucketKeyExpression"}, + "glueConfiguration":{"shape":"GlueConfiguration"}, + "roleArn":{"shape":"RoleArn"} + } + }, "SampleChannelDataRequest":{ "type":"structure", "required":["channelName"], diff --git a/aws-sdk-core/apis/iotanalytics/2017-11-27/docs-2.json b/aws-sdk-core/apis/iotanalytics/2017-11-27/docs-2.json index c08817f0c7b..6203d57386c 100644 --- a/aws-sdk-core/apis/iotanalytics/2017-11-27/docs-2.json +++ b/aws-sdk-core/apis/iotanalytics/2017-11-27/docs-2.json @@ -122,6 +122,18 @@ "refs": { } }, + "BucketKeyExpression": { + "base": null, + "refs": { + "S3DestinationConfiguration$key": "The key of the data set contents object. Each object in an Amazon S3 bucket has a key that is its unique identifier within the bucket (each object in a bucket has exactly one key).
" + } + }, + "BucketName": { + "base": null, + "refs": { + "S3DestinationConfiguration$bucket": "The name of the Amazon S3 bucket to which data set contents are delivered.
" + } + }, "CancelPipelineReprocessingRequest": { "base": null, "refs": { @@ -279,7 +291,7 @@ } }, "DatasetActionSummary": { - "base": "", + "base": "Information about the action which automatically creates the data set's contents.
", "refs": { "DatasetActionSummaries$member": null } @@ -640,6 +652,24 @@ "refs": { } }, + "GlueConfiguration": { + "base": "Configuration information for coordination with the AWS Glue ETL (extract, transform and load) service.
", + "refs": { + "S3DestinationConfiguration$glueConfiguration": "Configuration information for coordination with the AWS Glue ETL (extract, transform and load) service.
" + } + }, + "GlueDatabaseName": { + "base": null, + "refs": { + "GlueConfiguration$databaseName": "The name of the database in your AWS Glue Data Catalog in which the table is located. (An AWS Glue Data Catalog database contains Glue Data tables.)
" + } + }, + "GlueTableName": { + "base": null, + "refs": { + "GlueConfiguration$tableName": "The name of the table in your AWS Glue Data Catalog which is used to perform the ETL (extract, transform and load) operations. (An AWS Glue Data Catalog table contains partitioned data and descriptions of data sources and targets.)
" + } + }, "Image": { "base": null, "refs": { @@ -1048,7 +1078,8 @@ "DeviceRegistryEnrichActivity$roleArn": "The ARN of the role that allows access to the device's registry information.
", "DeviceShadowEnrichActivity$roleArn": "The ARN of the role that allows access to the device's shadow.
", "IotEventsDestinationConfiguration$roleArn": "The ARN of the role which grants AWS IoT Analytics permission to deliver data set contents to an AWS IoT Events input.
", - "LoggingOptions$roleArn": "The ARN of the role that grants permission to AWS IoT Analytics to perform logging.
" + "LoggingOptions$roleArn": "The ARN of the role that grants permission to AWS IoT Analytics to perform logging.
", + "S3DestinationConfiguration$roleArn": "The ARN of the role which grants AWS IoT Analytics permission to interact with your Amazon S3 and AWS Glue resources.
" } }, "RunPipelineActivityRequest": { @@ -1061,6 +1092,12 @@ "refs": { } }, + "S3DestinationConfiguration": { + "base": "Configuration information for delivery of data set contents to Amazon S3.
", + "refs": { + "DatasetContentDeliveryDestination$s3DestinationConfiguration": "Configuration information for delivery of data set contents to Amazon S3.
" + } + }, "SampleChannelDataRequest": { "base": null, "refs": { @@ -1287,7 +1324,7 @@ } }, "VersioningConfiguration": { - "base": null, + "base": "Information about the versioning of data set contents.
", "refs": { "CreateDatasetRequest$versioningConfiguration": "[Optional] How many versions of data set contents are kept. If not specified or set to null, only the latest version plus the latest succeeded version (if they are different) are kept for the time period specified by the \"retentionPeriod\" parameter. (For more information, see https://docs.aws.amazon.com/iotanalytics/latest/userguide/getting-started.html#aws-iot-analytics-dataset-versions)
", "Dataset$versioningConfiguration": "[Optional] How many versions of data set contents are kept. If not specified or set to null, only the latest version plus the latest succeeded version (if they are different) are kept for the time period specified by the \"retentionPeriod\" parameter. (For more information, see https://docs.aws.amazon.com/iotanalytics/latest/userguide/getting-started.html#aws-iot-analytics-dataset-versions)
", diff --git a/aws-sdk-core/apis/lambda/2015-03-31/api-2.json b/aws-sdk-core/apis/lambda/2015-03-31/api-2.json index e462d81d688..ed4cbc04ebc 100644 --- a/aws-sdk-core/apis/lambda/2015-03-31/api-2.json +++ b/aws-sdk-core/apis/lambda/2015-03-31/api-2.json @@ -2053,6 +2053,7 @@ "nodejs4.3", "nodejs6.10", "nodejs8.10", + "nodejs10.x", "java8", "python2.7", "python3.6", diff --git a/aws-sdk-core/apis/lambda/2015-03-31/waiters-2.json b/aws-sdk-core/apis/lambda/2015-03-31/waiters-2.json new file mode 100644 index 00000000000..07d1ab253a5 --- /dev/null +++ b/aws-sdk-core/apis/lambda/2015-03-31/waiters-2.json @@ -0,0 +1,22 @@ +{ + "version": 2, + "waiters": { + "FunctionExists": { + "delay": 1, + "operation": "GetFunction", + "maxAttempts": 20, + "acceptors": [ + { + "state": "success", + "matcher": "status", + "expected": 200 + }, + { + "state": "retry", + "matcher": "error", + "expected": "ResourceNotFoundException" + } + ] + } + } +} diff --git a/aws-sdk-core/lib/aws-sdk-core/lambda.rb b/aws-sdk-core/lib/aws-sdk-core/lambda.rb index 79ea466a85e..d999e2ca8e4 100644 --- a/aws-sdk-core/lib/aws-sdk-core/lambda.rb +++ b/aws-sdk-core/lib/aws-sdk-core/lambda.rb @@ -3,4 +3,5 @@ docs: "#{Aws::API_DIR}/lambda/2015-03-31/docs-2.json", examples: "#{Aws::API_DIR}/lambda/2015-03-31/examples-1.json", paginators: "#{Aws::API_DIR}/lambda/2015-03-31/paginators-1.json", + waiters: "#{Aws::API_DIR}/lambda/2015-03-31/waiters-2.json", })