aws-sdk-transfer 1.51.0 → 1.54.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 1c7ebfe35b8189393b2cb7d7e2dc0075a9fc346bfecf2c8ada3775293ac64b0b
-  data.tar.gz: 5846819507d83c00b63ae4fb1c93d09ec088e6aa015768ca78d8b53c019970b8
+  metadata.gz: 65c22200ccc095cf2afc03c93c5381a621da9ae132ebf660e29725359151815e
+  data.tar.gz: 0e393876399f2472754a661d0235b48c53eaee4db832faabb26210a99dd14983
 SHA512:
-  metadata.gz: ac4893b7513f79c391eb4d1aa813f6a31334ab38203ddfc0f47d299b88d02b65038fbec2456154a47d3f72e40ecf57410d5c82be1d4e26d787c4a44ea6f13c9d
-  data.tar.gz: 2810caafe6baba9e75cbaccdd9116c1f6078b3a9508fe7e4d36ca9128f6d7b9e87bbec9d049ebc02e4daec9e355df8ab8cb277ce1587c5f4723848fcf95f4144
+  metadata.gz: 885c30e162f5be6b9f0a75cd78bc2071e07c13e31f23e21861188e7016920ca3b22724b015a9bd812498d871903f4424a084752951150ede299d4608163397ef
+  data.tar.gz: 908228841afdb842d56e00c206ac1d9f37b6af85c13b2170f7f8926f2d32dbe122187a2b51be587ed97a37ce1e8c1093d1f657c5ed84f68364bf9af5c694a521

data/CHANGELOG.md

@@ -1,6 +1,21 @@
 Unreleased Changes
 ------------------
 
+1.54.0 (2022-05-12)
+------------------
+
+* Feature - AWS Transfer Family now accepts ECDSA keys for server host keys
+
+1.53.0 (2022-04-19)
+------------------
+
+* Feature - This release contains corrected HomeDirectoryMappings examples for several API functions: CreateAccess, UpdateAccess, CreateUser, and UpdateUser,.
+
+1.52.0 (2022-03-23)
+------------------
+
+* Feature - Documentation updates for AWS Transfer Family to describe how to remove an associated workflow from a server.
+
 1.51.0 (2022-03-10)
 ------------------
 

data/VERSION

@@ -1 +1 @@
-1.51.0
+1.54.0

data/lib/aws-sdk-transfer/client.rb

@@ -406,7 +406,7 @@ module Aws::Transfer
     #
     #   The following is an `Entry` and `Target` pair example for `chroot`.
     #
-    #   `[ \{ "Entry:": "/", "Target": "/bucket_name/home/mydirectory" \} ]`
+    #   `[ \{ "Entry": "/", "Target": "/bucket_name/home/mydirectory" \} ]`
     #
     # @option params [String] :policy
     #   A session policy for your user so that you can use the same IAM role
@@ -608,8 +608,25 @@ module Aws::Transfer
     #    </note>
     #
     # @option params [String] :host_key
-    #   The RSA private key as generated by the `ssh-keygen -N "" -m PEM -f
-    #   my-new-server-key` command.
+    #   The RSA or ECDSA private key to use for your server.
+    #
+    #   Use the following command to generate an RSA 2048 bit key with no
+    #   passphrase:
+    #
+    #   `ssh-keygen -t rsa -b 2048 -N "" -m PEM -f my-new-server-key`.
+    #
+    #   Use a minimum value of 2048 for the `-b` option: you can create a
+    #   stronger key using 3072 or 4096.
+    #
+    #   Use the following command to generate an ECDSA 256 bit key with no
+    #   passphrase:
+    #
+    #   `ssh-keygen -t ecdsa -b 256 -N "" -m PEM -f my-new-server-key`.
+    #
+    #   Valid values for the `-b` option for ECDSA are 256, 384, and 521.
+    #
+    #   For both of these commands, you can replace *my-new-server-key* with a
+    #   string of your choice.
     #
     #   If you aren't planning to migrate existing users from an existing
     #   SFTP-enabled server to a new server, don't update the host key.
@@ -836,7 +853,7 @@ module Aws::Transfer
     #
     #   The following is an `Entry` and `Target` pair example for `chroot`.
     #
-    #   `[ \{ "Entry:": "/", "Target": "/bucket_name/home/mydirectory" \} ]`
+    #   `[ \{ "Entry": "/", "Target": "/bucket_name/home/mydirectory" \} ]`
     #
     # @option params [String] :policy
     #   A session policy for your user so that you can use the same IAM role
@@ -970,13 +987,13 @@ module Aws::Transfer
     #   The `TYPE` specifies which of the following actions is being taken for
     #   this step.
     #
-    #   * *Copy*\: copy the file to another location
+    #   * *COPY*\: copy the file to another location
     #
-    #   * *Custom*\: custom step with a lambda target
+    #   * *CUSTOM*\: custom step with a lambda target
     #
-    #   * *Delete*\: delete the file
+    #   * *DELETE*\: delete the file
     #
-    #   * *Tag*\: add a tag to the file
+    #   * *TAG*\: add a tag to the file
     #
     #   <note markdown="1"> Currently, copying and tagging are supported only on S3.
     #
@@ -2359,7 +2376,7 @@ module Aws::Transfer
     #
     #   The following is an `Entry` and `Target` pair example for `chroot`.
     #
-    #   `[ \{ "Entry:": "/", "Target": "/bucket_name/home/mydirectory" \} ]`
+    #   `[ \{ "Entry": "/", "Target": "/bucket_name/home/mydirectory" \} ]`
     #
     # @option params [String] :policy
     #   A session policy for your user so that you can use the same IAM role
@@ -2562,15 +2579,32 @@ module Aws::Transfer
     #    </note>
     #
     # @option params [String] :host_key
-    #   The RSA private key as generated by `ssh-keygen -N "" -m PEM -f
-    #   my-new-server-key`.
+    #   The RSA or ECDSA private key to use for your server.
+    #
+    #   Use the following command to generate an RSA 2048 bit key with no
+    #   passphrase:
+    #
+    #   `ssh-keygen -t rsa -b 2048 -N "" -m PEM -f my-new-server-key`.
+    #
+    #   Use a minimum value of 2048 for the `-b` option: you can create a
+    #   stronger key using 3072 or 4096.
+    #
+    #   Use the following command to generate an ECDSA 256 bit key with no
+    #   passphrase:
+    #
+    #   `ssh-keygen -t ecdsa -b 256 -N "" -m PEM -f my-new-server-key`.
+    #
+    #   Valid values for the `-b` option for ECDSA are 256, 384, and 521.
+    #
+    #   For both of these commands, you can replace *my-new-server-key* with a
+    #   string of your choice.
     #
     #   If you aren't planning to migrate existing users from an existing
-    #   server to a new server, don't update the host key. Accidentally
-    #   changing a server's host key can be disruptive.
+    #   SFTP-enabled server to a new server, don't update the host key.
+    #   Accidentally changing a server's host key can be disruptive.
     #
     #   For more information, see [Change the host key for your SFTP-enabled
-    #   server][1] in the *Amazon Web ServicesTransfer Family User Guide*.
+    #   server][1] in the *Amazon Web Services Transfer Family User Guide*.
     #
     #
     #
@@ -2647,6 +2681,12 @@ module Aws::Transfer
     #   Specifies the workflow ID for the workflow to assign and the execution
     #   role used for executing the workflow.
     #
+    #   To remove an associated workflow from a server, you can provide an
+    #   empty `OnUpload` object, as in the following example.
+    #
+    #   `aws transfer update-server --server-id s-01234567890abcdef
+    #   --workflow-details '\{"OnUpload":[]\}'`
+    #
     # @return [Types::UpdateServerResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
     #
     #   * {Types::UpdateServerResponse#server_id #server_id} => String
@@ -2747,7 +2787,7 @@ module Aws::Transfer
     #
     #   The following is an `Entry` and `Target` pair example for `chroot`.
     #
-    #   `[ \{ "Entry:": "/", "Target": "/bucket_name/home/mydirectory" \} ]`
+    #   `[ \{ "Entry": "/", "Target": "/bucket_name/home/mydirectory" \} ]`
     #
     # @option params [String] :policy
     #   A session policy for your user so that you can use the same IAM role
@@ -2860,7 +2900,7 @@ module Aws::Transfer
         params: params,
         config: config)
       context[:gem_name] = 'aws-sdk-transfer'
-      context[:gem_version] = '1.51.0'
+      context[:gem_version] = '1.54.0'
       Seahorse::Client::Request.new(handlers, context)
     end
 

data/lib/aws-sdk-transfer/types.rb

@@ -161,7 +161,7 @@ module Aws::Transfer
     #
     #   The following is an `Entry` and `Target` pair example for `chroot`.
     #
-    #   `[ \{ "Entry:": "/", "Target": "/bucket_name/home/mydirectory" \} ]`
+    #   `[ \{ "Entry": "/", "Target": "/bucket_name/home/mydirectory" \} ]`
     #   @return [Array<Types::HomeDirectoryMapEntry>]
     #
     # @!attribute [rw] policy
@@ -409,8 +409,25 @@ module Aws::Transfer
     #   @return [String]
     #
     # @!attribute [rw] host_key
-    #   The RSA private key as generated by the `ssh-keygen -N "" -m PEM -f
-    #   my-new-server-key` command.
+    #   The RSA or ECDSA private key to use for your server.
+    #
+    #   Use the following command to generate an RSA 2048 bit key with no
+    #   passphrase:
+    #
+    #   `ssh-keygen -t rsa -b 2048 -N "" -m PEM -f my-new-server-key`.
+    #
+    #   Use a minimum value of 2048 for the `-b` option: you can create a
+    #   stronger key using 3072 or 4096.
+    #
+    #   Use the following command to generate an ECDSA 256 bit key with no
+    #   passphrase:
+    #
+    #   `ssh-keygen -t ecdsa -b 256 -N "" -m PEM -f my-new-server-key`.
+    #
+    #   Valid values for the `-b` option for ECDSA are 256, 384, and 521.
+    #
+    #   For both of these commands, you can replace *my-new-server-key* with
+    #   a string of your choice.
     #
     #   If you aren't planning to migrate existing users from an existing
     #   SFTP-enabled server to a new server, don't update the host key.
@@ -646,7 +663,7 @@ module Aws::Transfer
     #
     #   The following is an `Entry` and `Target` pair example for `chroot`.
     #
-    #   `[ \{ "Entry:": "/", "Target": "/bucket_name/home/mydirectory" \} ]`
+    #   `[ \{ "Entry": "/", "Target": "/bucket_name/home/mydirectory" \} ]`
     #   @return [Array<Types::HomeDirectoryMapEntry>]
     #
     # @!attribute [rw] policy
@@ -864,13 +881,13 @@ module Aws::Transfer
     #   The `TYPE` specifies which of the following actions is being taken
     #   for this step.
     #
-    #   * *Copy*\: copy the file to another location
+    #   * *COPY*\: copy the file to another location
     #
-    #   * *Custom*\: custom step with a lambda target
+    #   * *CUSTOM*\: custom step with a lambda target
     #
-    #   * *Delete*\: delete the file
+    #   * *DELETE*\: delete the file
     #
-    #   * *Tag*\: add a tag to the file
+    #   * *TAG*\: add a tag to the file
     #
     #   <note markdown="1"> Currently, copying and tagging are supported only on S3.
     #
@@ -2133,13 +2150,13 @@ module Aws::Transfer
     # @!attribute [rw] step_type
     #   One of the available step types.
     #
-    #   * *Copy*\: copy the file to another location
+    #   * *COPY*\: copy the file to another location
     #
-    #   * *Custom*\: custom step with a lambda target
+    #   * *CUSTOM*\: custom step with a lambda target
     #
-    #   * *Delete*\: delete the file
+    #   * *DELETE*\: delete the file
     #
-    #   * *Tag*\: add a tag to the file
+    #   * *TAG*\: add a tag to the file
     #   @return [String]
     #
     # @!attribute [rw] outputs
@@ -2187,7 +2204,7 @@ module Aws::Transfer
     #
     # The following is an `Entry` and `Target` pair example for `chroot`.
     #
-    # `[ \{ "Entry:": "/", "Target": "/bucket_name/home/mydirectory" \} ]`
+    # `[ \{ "Entry": "/", "Target": "/bucket_name/home/mydirectory" \} ]`
     #
     # @note When making an API call, you may pass HomeDirectoryMapEntry
     #   data as a hash:
@@ -3818,7 +3835,7 @@ module Aws::Transfer
     #
     #   The following is an `Entry` and `Target` pair example for `chroot`.
     #
-    #   `[ \{ "Entry:": "/", "Target": "/bucket_name/home/mydirectory" \} ]`
+    #   `[ \{ "Entry": "/", "Target": "/bucket_name/home/mydirectory" \} ]`
     #   @return [Array<Types::HomeDirectoryMapEntry>]
     #
     # @!attribute [rw] policy
@@ -4060,15 +4077,32 @@ module Aws::Transfer
     #   @return [String]
     #
     # @!attribute [rw] host_key
-    #   The RSA private key as generated by `ssh-keygen -N "" -m PEM -f
-    #   my-new-server-key`.
+    #   The RSA or ECDSA private key to use for your server.
+    #
+    #   Use the following command to generate an RSA 2048 bit key with no
+    #   passphrase:
+    #
+    #   `ssh-keygen -t rsa -b 2048 -N "" -m PEM -f my-new-server-key`.
+    #
+    #   Use a minimum value of 2048 for the `-b` option: you can create a
+    #   stronger key using 3072 or 4096.
+    #
+    #   Use the following command to generate an ECDSA 256 bit key with no
+    #   passphrase:
+    #
+    #   `ssh-keygen -t ecdsa -b 256 -N "" -m PEM -f my-new-server-key`.
+    #
+    #   Valid values for the `-b` option for ECDSA are 256, 384, and 521.
+    #
+    #   For both of these commands, you can replace *my-new-server-key* with
+    #   a string of your choice.
     #
     #   If you aren't planning to migrate existing users from an existing
-    #   server to a new server, don't update the host key. Accidentally
-    #   changing a server's host key can be disruptive.
+    #   SFTP-enabled server to a new server, don't update the host key.
+    #   Accidentally changing a server's host key can be disruptive.
     #
     #   For more information, see [Change the host key for your SFTP-enabled
-    #   server][1] in the *Amazon Web ServicesTransfer Family User Guide*.
+    #   server][1] in the *Amazon Web Services Transfer Family User Guide*.
     #
     #
     #
@@ -4153,6 +4187,12 @@ module Aws::Transfer
     # @!attribute [rw] workflow_details
     #   Specifies the workflow ID for the workflow to assign and the
     #   execution role used for executing the workflow.
+    #
+    #   To remove an associated workflow from a server, you can provide an
+    #   empty `OnUpload` object, as in the following example.
+    #
+    #   `aws transfer update-server --server-id s-01234567890abcdef
+    #   --workflow-details '\{"OnUpload":[]\}'`
     #   @return [Types::WorkflowDetails]
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/transfer-2018-11-05/UpdateServerRequest AWS API Documentation
@@ -4251,7 +4291,7 @@ module Aws::Transfer
     #
     #   The following is an `Entry` and `Target` pair example for `chroot`.
     #
-    #   `[ \{ "Entry:": "/", "Target": "/bucket_name/home/mydirectory" \} ]`
+    #   `[ \{ "Entry": "/", "Target": "/bucket_name/home/mydirectory" \} ]`
     #   @return [Array<Types::HomeDirectoryMapEntry>]
     #
     # @!attribute [rw] policy
@@ -4430,6 +4470,12 @@ module Aws::Transfer
     # @!attribute [rw] on_upload
     #   A trigger that starts a workflow: the workflow begins to execute
     #   after a file is uploaded.
+    #
+    #   To remove an associated workflow from a server, you can provide an
+    #   empty `OnUpload` object, as in the following example.
+    #
+    #   `aws transfer update-server --server-id s-01234567890abcdef
+    #   --workflow-details '\{"OnUpload":[]\}'`
     #   @return [Array<Types::WorkflowDetail>]
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/transfer-2018-11-05/WorkflowDetails AWS API Documentation
@@ -4487,13 +4533,13 @@ module Aws::Transfer
     # @!attribute [rw] type
     #   Currently, the following step types are supported.
     #
-    #   * *Copy*\: copy the file to another location
+    #   * *COPY*\: copy the file to another location
     #
-    #   * *Custom*\: custom step with a lambda target
+    #   * *CUSTOM*\: custom step with a lambda target
     #
-    #   * *Delete*\: delete the file
+    #   * *DELETE*\: delete the file
     #
-    #   * *Tag*\: add a tag to the file
+    #   * *TAG*\: add a tag to the file
     #   @return [String]
     #
     # @!attribute [rw] copy_step_details

data/lib/aws-sdk-transfer.rb

@@ -49,6 +49,6 @@ require_relative 'aws-sdk-transfer/customizations'
 # @!group service
 module Aws::Transfer
 
-  GEM_VERSION = '1.51.0'
+  GEM_VERSION = '1.54.0'
 
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: aws-sdk-transfer
 version: !ruby/object:Gem::Version
-  version: 1.51.0
+  version: 1.54.0
 platform: ruby
 authors:
 - Amazon Web Services
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2022-03-10 00:00:00.000000000 Z
+date: 2022-05-12 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: aws-sdk-core