Create an FTPS-enabled server - AWS Transfer Family

Create an FTPS-enabled server

File Transfer Protocol over SSL (FTPS) is an extension to FTP. It uses Transport Layer Security (TLS) and Secure Sockets Layer (SSL) cryptographic protocols to encrypt traffic. FTPS allows encryption of both the control and data channel connections either concurrently or independently.

To create an FTPS-enabled server

  1. Open the AWS Transfer Family console at https://console.aws.amazon.com/transfer/ and select Servers from the navigation pane, then choose Create server.

  2. In Choose protocols, select FTPS.

    For Server certificate, choose a certificate stored in AWS Certificate Manager (ACM) which will be used to identify your server when clients connect to it over FTPS and then choose Next.

    To request a new public certificate, see Request a public certificate in the AWS Certificate Manager User Guide.

    To import an existing certificate into ACM, see Importing certificates into ACM in the AWS Certificate Manager User Guide.

    To request a private certificate to use FTPS through private IP addresses, see Requesting a Private Certificate in the AWS Certificate Manager User Guide.

    Certificates with the following cryptographic algorithms and key sizes are supported:

    • 2048-bit RSA (RSA_2048)

    • 4096-bit RSA (RSA_4096)

    • Elliptic Prime Curve 256 bit (EC_prime256v1)

    • Elliptic Prime Curve 384 bit (EC_secp384r1)

    • Elliptic Prime Curve 521 bit (EC_secp521r1)

    Note

    The certificate must be a valid SSL/TLS X.509 version 3 certificate with FQDN or IP address specified and information about the issuer.

    
                        Console screenshot showing Choose protocols dialog box with FTPS
                            selected.
  3. In Choose an identity provider, choose the identity provider that you want to use to manage user access. You have the following options:

    • AWS Directory Service for Microsoft Active Directory: you provide an AWS Directory Service directory to access the endpoint. By doing so, you can use credentials stored in your Active Directory to authenticate your users. To learn more about working with AWS Managed Microsoft AD identity providers, see Working with AWS Directory Service for Microsoft Active Directory.

      Note

      Cross-Account and Shared directories are not supported for AWS Managed Microsoft AD.

      
                            Console screenshot showing Choose identity provider dialog box with
                                Managed AD selected.
    • Custom: choose either of the following options:

      
                            Console screenshot showing Choose identity provider dialog box with
                                Custom selected.
  4. In Choose an endpoint, do the following:

    Note

    FTPS servers for Transfer Family operate over Port 21 (Control Channel) and Port Range 8192-8200 (Data Channel).

    1. For Endpoint type, choose the VPC hosted endpoint type to host your server's endpoint. For information about setting up your VPC hosted endpoint, see Create a server in a virtual private cloud.

      Note

      Publicly accessible endpoints are not supported.

    2. (Optional) For FIPS Enabled, select the FIPS Enabled endpoint check box to ensure that the endpoint complies with Federal Information Processing Standards (FIPS).

      Note

      FIPS-enabled endpoints are only available in North American AWS Regions. For available Regions, see AWS Transfer Family endpoints and quotas in the AWS General Reference. For more information about the available FIPS endpoints, see Federal Information Processing Standard (FIPS) 140-2 .

    3. Choose Next.

    
                        Console screenshot showing Choose endpoint dialog box with VPC
                            hosted selected.
  5. On the Choose domain page, choose the AWS storage service that you want to use to store and access your data over the selected protocol:

    • Choose Amazon S3 to store and access your files as objects over the selected protocol.

    • Choose Amazon EFS to store and access your files in your Amazon EFS file system over the selected protocol.

    Choose Next.

  6. In Configure additional details, do the following:

    1. For CloudWatch logging, choose one of the following to enable Amazon CloudWatch logging of your user activity:

      • Create a new role to allow Transfer Family to automatically create the IAM role, as long as you have the right permissions to create a new role. The IAM role that is created is called AWSTransferLoggingAccess.

      • Choose an existing role to choose an existing IAM role from your account. Under Logging role, choose the role. This IAM role should include a trust policy with Service set to transfer.amazonaws.com.

        For more information about CloudWatch logging, see Log activity with CloudWatch.

      Note
      • You can't view end-user activity in CloudWatch if you don't specify a logging role.

      • If you don't want to set up a CloudWatch logging role, choose Choose an existing role, but don't select a logging role.

      
                                Console screenshot showing CloudWatch logging section with
                                    create new role selected.
    2. For Cryptographic algorithm options, choose a security policy that contains the cryptographic algorithms enabled for use by your server.

      Note

      By default:

      • If FIPS Enabled endpoint is not selected, the TransferSecurityPolicy-2020-06 security policy is attached to your server.

      • If FIPS Enabled endpoint is selected, the TransferSecurityPolicy-FIPS-2020-06 security policy is attached to your server.

      For more information about security policies, see Working with security policies.

      
                                Console screenshot showing cryptographic algorithm options
                                    section with a security policy selected.
    3. (Optional) For Server Host Key, keep it blank.

      Note

      This section is only for migrating users from an existing SFTP-enabled server.

      
                                Console screenshot showing server host key section.
    4. (Optional) For Tags, for Key and Value, enter one or more tags as key-value pairs, and then choose Add tag.

    5. Choose Next.

      
                                Console screenshot showing tags section.
    6. (Optional) For Post-upload file-processing WorkflowId, enter a workflow ID and a corresponding role that Transfer should assume when executing the workflow.

      
                                Console screenshot showing the tags section.
  7. In Review and create, review your choices.

    • If you want to edit any of them, choose Edit next to the step.

      Note

      You will need to review each step after the step you chose to edit.

    • If you have no changes, choose Create server to create your server. You are taken to the Servers page, shown following, where your new server is listed.

It can take a couple of minutes before the status for your new server changes to Online. At that point, your server can perform file operations for your users.


                Console screenshot showing servers section with server ID and status of
                    starting.

Next steps – For the next step, continue on to Working with custom identity providers to set up users.