create-workflow¶

Description¶

Allows you to create a workflow with specified steps and step details the workflow invokes after file transfer completes. After creating a workflow, you can associate the workflow created with any transfer servers by specifying the workflow-details field in CreateServer and UpdateServer operations.

Synopsis¶

  create-workflow
[--description <value>]
--steps <value>
[--on-exception-steps <value>]
[--tags <value>]
[--cli-input-json | --cli-input-yaml]
[--generate-cli-skeleton <value>]
[--debug]
[--endpoint-url <value>]
[--no-verify-ssl]
[--no-paginate]
[--output <value>]
[--query <value>]
[--profile <value>]
[--region <value>]
[--version <value>]
[--color <value>]
[--no-sign-request]
[--ca-bundle <value>]
[--cli-read-timeout <value>]
[--cli-connect-timeout <value>]
[--cli-binary-format <value>]
[--no-cli-pager]
[--cli-auto-prompt]
[--no-cli-auto-prompt]

Options¶

--description (string)

A textual description for the workflow.

--steps (list)

Specifies the details for the steps that are in the specified workflow.

The TYPE specifies which of the following actions is being taken for this step.

COPY : Copy the file to another location.

CUSTOM : Perform a custom step with an Lambda function target.

DELETE : Delete the file.

TAG : Add a tag to the file.

Note

Currently, copying and tagging are supported only on S3.

For file location, you specify either the S3 bucket and key, or the EFS file system ID and path.

(structure)

The basic building block of a workflow.

Type -> (string)

Currently, the following step types are supported.

COPY : Copy the file to another location.

CUSTOM : Perform a custom step with an Lambda function target.

DELETE : Delete the file.

TAG : Add a tag to the file.

CopyStepDetails -> (structure)

Details for a step that performs a file copy.

Consists of the following values:

A description

An S3 location for the destination of the file copy.

A flag that indicates whether or not to overwrite an existing file of the same name. The default is FALSE .

Name -> (string)

The name of the step, used as an identifier.

DestinationFileLocation -> (structure)

Specifies the location for the file being copied. Only applicable for Copy type workflow steps. Use ${Transfer:username} in this field to parametrize the destination prefix by username.

S3FileLocation -> (structure)

Specifies the details for the S3 file being copied.

Bucket -> (string)

Specifies the S3 bucket for the customer input file.

Key -> (string)

The name assigned to the file when it was created in Amazon S3. You use the object key to retrieve the object.

EfsFileLocation -> (structure)

Reserved for future use.

FileSystemId -> (string)

The identifier of the file system, assigned by Amazon EFS.

Path -> (string)

The pathname for the folder being used by a workflow.

OverwriteExisting -> (string)

A flag that indicates whether or not to overwrite an existing file of the same name. The default is FALSE .

SourceFileLocation -> (string)

Specifies which file to use as input to the workflow step: either the output from the previous step, or the originally uploaded file for the workflow.

Enter ${previous.file} to use the previous file as the input. In this case, this workflow step uses the output file from the previous workflow step as input. This is the default value.

Enter ${original.file} to use the originally-uploaded file location as input for this step.

CustomStepDetails -> (structure)

Details for a step that invokes a lambda function.

Consists of the lambda function name, target, and timeout (in seconds).

Name -> (string)

The name of the step, used as an identifier.

Target -> (string)

The ARN for the lambda function that is being called.

TimeoutSeconds -> (integer)

Timeout, in seconds, for the step.

SourceFileLocation -> (string)

Specifies which file to use as input to the workflow step: either the output from the previous step, or the originally uploaded file for the workflow.

Enter ${previous.file} to use the previous file as the input. In this case, this workflow step uses the output file from the previous workflow step as input. This is the default value.

Enter ${original.file} to use the originally-uploaded file location as input for this step.

DeleteStepDetails -> (structure)

Details for a step that deletes the file.

Name -> (string)

The name of the step, used as an identifier.

SourceFileLocation -> (string)

Specifies which file to use as input to the workflow step: either the output from the previous step, or the originally uploaded file for the workflow.

Enter ${previous.file} to use the previous file as the input. In this case, this workflow step uses the output file from the previous workflow step as input. This is the default value.

Enter ${original.file} to use the originally-uploaded file location as input for this step.

TagStepDetails -> (structure)

Details for a step that creates one or more tags.

You specify one or more tags: each tag contains a key/value pair.

Name -> (string)

The name of the step, used as an identifier.

Tags -> (list)

Array that contains from 1 to 10 key/value pairs.

(structure)

Specifies the key-value pair that are assigned to a file during the execution of a Tagging step.

Key -> (string)

The name assigned to the tag that you create.

Value -> (string)

The value that corresponds to the key.

SourceFileLocation -> (string)

Specifies which file to use as input to the workflow step: either the output from the previous step, or the originally uploaded file for the workflow.

Enter ${previous.file} to use the previous file as the input. In this case, this workflow step uses the output file from the previous workflow step as input. This is the default value.

Enter ${original.file} to use the originally-uploaded file location as input for this step.

DecryptStepDetails -> (structure)

Name -> (string)

Type -> (string)

SourceFileLocation -> (string)

OverwriteExisting -> (string)

DestinationFileLocation -> (structure)

Specifies the location for the file being copied. Only applicable for the Copy type of workflow steps.

S3FileLocation -> (structure)

Specifies the details for the S3 file being copied.

Bucket -> (string)

Specifies the S3 bucket for the customer input file.

Key -> (string)

The name assigned to the file when it was created in Amazon S3. You use the object key to retrieve the object.

EfsFileLocation -> (structure)

Reserved for future use.

FileSystemId -> (string)

The identifier of the file system, assigned by Amazon EFS.

Path -> (string)

The pathname for the folder being used by a workflow.

JSON Syntax:

[
  {
    "Type": "COPY"|"CUSTOM"|"TAG"|"DELETE"|"DECRYPT",
    "CopyStepDetails": {
      "Name": "string",
      "DestinationFileLocation": {
        "S3FileLocation": {
          "Bucket": "string",
          "Key": "string"
        },
        "EfsFileLocation": {
          "FileSystemId": "string",
          "Path": "string"
        }
      },
      "OverwriteExisting": "TRUE"|"FALSE",
      "SourceFileLocation": "string"
    },
    "CustomStepDetails": {
      "Name": "string",
      "Target": "string",
      "TimeoutSeconds": integer,
      "SourceFileLocation": "string"
    },
    "DeleteStepDetails": {
      "Name": "string",
      "SourceFileLocation": "string"
    },
    "TagStepDetails": {
      "Name": "string",
      "Tags": [
        {
          "Key": "string",
          "Value": "string"
        }
        ...
      ],
      "SourceFileLocation": "string"
    },
    "DecryptStepDetails": {
      "Name": "string",
      "Type": "PGP",
      "SourceFileLocation": "string",
      "OverwriteExisting": "TRUE"|"FALSE",
      "DestinationFileLocation": {
        "S3FileLocation": {
          "Bucket": "string",
          "Key": "string"
        },
        "EfsFileLocation": {
          "FileSystemId": "string",
          "Path": "string"
        }
      }
    }
  }
  ...
]

--on-exception-steps (list)

Specifies the steps (actions) to take if errors are encountered during execution of the workflow.

Note

For custom steps, the lambda function needs to send FAILURE to the call back API to kick off the exception steps. Additionally, if the lambda does not send SUCCESS before it times out, the exception steps are executed.

(structure)

The basic building block of a workflow.

Type -> (string)

Currently, the following step types are supported.

COPY : Copy the file to another location.

CUSTOM : Perform a custom step with an Lambda function target.

DELETE : Delete the file.

TAG : Add a tag to the file.

CopyStepDetails -> (structure)

Details for a step that performs a file copy.

Consists of the following values:

A description

An S3 location for the destination of the file copy.

A flag that indicates whether or not to overwrite an existing file of the same name. The default is FALSE .

Name -> (string)

The name of the step, used as an identifier.

DestinationFileLocation -> (structure)

Specifies the location for the file being copied. Only applicable for Copy type workflow steps. Use ${Transfer:username} in this field to parametrize the destination prefix by username.

S3FileLocation -> (structure)

Specifies the details for the S3 file being copied.

Bucket -> (string)

Specifies the S3 bucket for the customer input file.

Key -> (string)

The name assigned to the file when it was created in Amazon S3. You use the object key to retrieve the object.

EfsFileLocation -> (structure)

Reserved for future use.

FileSystemId -> (string)

The identifier of the file system, assigned by Amazon EFS.

Path -> (string)

The pathname for the folder being used by a workflow.

OverwriteExisting -> (string)

A flag that indicates whether or not to overwrite an existing file of the same name. The default is FALSE .

SourceFileLocation -> (string)

Specifies which file to use as input to the workflow step: either the output from the previous step, or the originally uploaded file for the workflow.

Enter ${previous.file} to use the previous file as the input. In this case, this workflow step uses the output file from the previous workflow step as input. This is the default value.

Enter ${original.file} to use the originally-uploaded file location as input for this step.

CustomStepDetails -> (structure)

Details for a step that invokes a lambda function.

Consists of the lambda function name, target, and timeout (in seconds).

Name -> (string)

The name of the step, used as an identifier.

Target -> (string)

The ARN for the lambda function that is being called.

TimeoutSeconds -> (integer)

Timeout, in seconds, for the step.

SourceFileLocation -> (string)

Specifies which file to use as input to the workflow step: either the output from the previous step, or the originally uploaded file for the workflow.

Enter ${previous.file} to use the previous file as the input. In this case, this workflow step uses the output file from the previous workflow step as input. This is the default value.

Enter ${original.file} to use the originally-uploaded file location as input for this step.

DeleteStepDetails -> (structure)

Details for a step that deletes the file.

Name -> (string)

The name of the step, used as an identifier.

SourceFileLocation -> (string)

Specifies which file to use as input to the workflow step: either the output from the previous step, or the originally uploaded file for the workflow.

Enter ${previous.file} to use the previous file as the input. In this case, this workflow step uses the output file from the previous workflow step as input. This is the default value.

Enter ${original.file} to use the originally-uploaded file location as input for this step.

TagStepDetails -> (structure)

Details for a step that creates one or more tags.

You specify one or more tags: each tag contains a key/value pair.

Name -> (string)

The name of the step, used as an identifier.

Tags -> (list)

Array that contains from 1 to 10 key/value pairs.

(structure)

Specifies the key-value pair that are assigned to a file during the execution of a Tagging step.

Key -> (string)

The name assigned to the tag that you create.

Value -> (string)

The value that corresponds to the key.

SourceFileLocation -> (string)

Specifies which file to use as input to the workflow step: either the output from the previous step, or the originally uploaded file for the workflow.

Enter ${previous.file} to use the previous file as the input. In this case, this workflow step uses the output file from the previous workflow step as input. This is the default value.

Enter ${original.file} to use the originally-uploaded file location as input for this step.

DecryptStepDetails -> (structure)

Name -> (string)

Type -> (string)

SourceFileLocation -> (string)

OverwriteExisting -> (string)

DestinationFileLocation -> (structure)

Specifies the location for the file being copied. Only applicable for the Copy type of workflow steps.

S3FileLocation -> (structure)

Specifies the details for the S3 file being copied.

Bucket -> (string)

Specifies the S3 bucket for the customer input file.

Key -> (string)

The name assigned to the file when it was created in Amazon S3. You use the object key to retrieve the object.

EfsFileLocation -> (structure)

Reserved for future use.

FileSystemId -> (string)

The identifier of the file system, assigned by Amazon EFS.

Path -> (string)

The pathname for the folder being used by a workflow.

JSON Syntax:

[
  {
    "Type": "COPY"|"CUSTOM"|"TAG"|"DELETE"|"DECRYPT",
    "CopyStepDetails": {
      "Name": "string",
      "DestinationFileLocation": {
        "S3FileLocation": {
          "Bucket": "string",
          "Key": "string"
        },
        "EfsFileLocation": {
          "FileSystemId": "string",
          "Path": "string"
        }
      },
      "OverwriteExisting": "TRUE"|"FALSE",
      "SourceFileLocation": "string"
    },
    "CustomStepDetails": {
      "Name": "string",
      "Target": "string",
      "TimeoutSeconds": integer,
      "SourceFileLocation": "string"
    },
    "DeleteStepDetails": {
      "Name": "string",
      "SourceFileLocation": "string"
    },
    "TagStepDetails": {
      "Name": "string",
      "Tags": [
        {
          "Key": "string",
          "Value": "string"
        }
        ...
      ],
      "SourceFileLocation": "string"
    },
    "DecryptStepDetails": {
      "Name": "string",
      "Type": "PGP",
      "SourceFileLocation": "string",
      "OverwriteExisting": "TRUE"|"FALSE",
      "DestinationFileLocation": {
        "S3FileLocation": {
          "Bucket": "string",
          "Key": "string"
        },
        "EfsFileLocation": {
          "FileSystemId": "string",
          "Path": "string"
        }
      }
    }
  }
  ...
]

--tags (list)

Key-value pairs that can be used to group and search for workflows. Tags are metadata attached to workflows for any purpose.

(structure)

Creates a key-value pair for a specific resource. Tags are metadata that you can use to search for and group a resource for various purposes. You can apply tags to servers, users, and roles. A tag key can take more than one value. For example, to group servers for accounting purposes, you might create a tag called Group and assign the values Research and Accounting to that group.

Key -> (string)

The name assigned to the tag that you create.

Value -> (string)

Contains one or more values that you assigned to the key name you create.

Shorthand Syntax:

Key=string,Value=string ...

JSON Syntax:

[
  {
    "Key": "string",
    "Value": "string"
  }
  ...
]

--cli-input-json | --cli-input-yaml (string) Reads arguments from the JSON string provided. The JSON string follows the format provided by --generate-cli-skeleton. If other arguments are provided on the command line, those values will override the JSON-provided values. It is not possible to pass arbitrary binary values using a JSON-provided value as the string will be taken literally. This may not be specified along with --cli-input-yaml.

--generate-cli-skeleton (string) Prints a JSON skeleton to standard output without sending an API request. If provided with no value or the value input, prints a sample input JSON that can be used as an argument for --cli-input-json. Similarly, if provided yaml-input it will print a sample input YAML that can be used with --cli-input-yaml. If provided with the value output, it validates the command inputs and returns a sample output JSON for that command. The generated JSON skeleton is not stable between versions of the AWS CLI and there are no backwards compatibility guarantees in the JSON skeleton generated.

Global Options¶

--debug (boolean)

Turn on debug logging.

--endpoint-url (string)

Override command’s default URL with the given URL.

--no-verify-ssl (boolean)

By default, the AWS CLI uses SSL when communicating with AWS services. For each SSL connection, the AWS CLI will verify SSL certificates. This option overrides the default behavior of verifying SSL certificates.

--no-paginate (boolean)

Disable automatic pagination.

--output (string)

The formatting style for command output.

json
text
table
yaml
yaml-stream

--query (string)

A JMESPath query to use in filtering the response data.

--profile (string)

Use a specific profile from your credential file.

--region (string)

The region to use. Overrides config/env settings.

--version (string)

Display the version of this tool.

--color (string)

Turn on/off color output.

on
off
auto

--no-sign-request (boolean)

Do not sign requests. Credentials will not be loaded if this argument is provided.

--ca-bundle (string)

The CA certificate bundle to use when verifying SSL certificates. Overrides config/env settings.

--cli-read-timeout (int)

The maximum socket read time in seconds. If the value is set to 0, the socket read will be blocking and not timeout. The default value is 60 seconds.

--cli-connect-timeout (int)

The maximum socket connect time in seconds. If the value is set to 0, the socket connect will be blocking and not timeout. The default value is 60 seconds.

--cli-binary-format (string)

The formatting style to be used for binary blobs. The default format is base64. The base64 format expects binary blobs to be provided as a base64 encoded string. The raw-in-base64-out format preserves compatibility with AWS CLI V1 behavior and binary values must be passed literally. When providing contents from a file that map to a binary blob fileb:// will always be treated as binary and use the file contents directly regardless of the cli-binary-format setting. When using file:// the file contents will need to properly formatted for the configured cli-binary-format.

base64
raw-in-base64-out

--no-cli-pager (boolean)

Disable cli pager for output.

--cli-auto-prompt (boolean)

Automatically prompt for CLI input parameters.

--no-cli-auto-prompt (boolean)

Disable automatically prompt for CLI input parameters.

Output¶

WorkflowId -> (string)

A unique identifier for the workflow.

Table of Contents

Feedback

User Guide

create-workflow¶

Description¶

Synopsis¶

Options¶

Global Options¶

Output¶