Create an AS2 server using the Transfer Family console - AWS Transfer Family

Create an AS2 server using the Transfer Family console

This procedure explains how to create an AS2-enabled server by using the Transfer Family console. If you want to use the AWS CLI instead, see Step 2: Create a Transfer Family server that uses the AS2 protocol.

Note

You can attach a file-processing workflow to a Transfer Family server that uses the AS2 protocol: however, AS2 messages don't execute workflows attached to the server.

To create an AS2-enabled server

  1. Open the AWS Transfer Family console at https://console.aws.amazon.com/transfer/.

  2. In the left navigation pane, choose Servers, and then choose Create server.

  3. On the Choose protocols page, select AS2 (Applicability Statement 2), and then choose Next.

  4. On the Choose an identity provider page, choose Next.

    Note

    For AS2, you cannot choose an identity provider because basic authentication is not supported for the AS2 protocol. Instead, you control access through virtual private cloud (VPC) security groups.

  5. On the Choose an endpoint page, do the following:

    Console screenshot showing the Choose an endpoint page with VPC hosted selected.

    1. For Endpoint type, choose VPC hosted 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 for the AS2 protocol. To make your VPC endpoint accessible over the internet, choose Internet Facing under Access, and then supply your Elastic IP addresses.

    2. For Access, choose one of the following options:

      • Internal – Choose this option to provide access from within your VPC and VPC-connected environments, such as an on-premises data center over AWS Direct Connect or VPN.

      • Internet Facing – Choose this option to provide access over the internet and from within your VPC and VPC-connected environments, such as an on-premises data center over AWS Direct Connect or VPN.

        If you choose Internet Facing, supply your Elastic IP addresses when prompted.

    3. For VPC, either choose an existing VPC or choose Create VPC to create a new VPC.

    4. For FIPS Enabled, keep the FIPS Enabled endpoint check box cleared.

      Note

      FIPS-enabled endpoints are not supported for the AS2 protocol.

    5. Choose Next.

  6. On the Choose a domain page, choose Amazon S3 to store and access your files as objects by using the selected protocol.

    Choose Next.

  7. On the Configure additional details page, choose the settings that you need.

    Note

    If you are configuring any other protocols along with AS2, all of the additional detail settings apply. However, for the AS2 protocol, the only settings that apply are those in the CloudWatch logging and Tags sections.

    Even though setting up a CloudWatch logging role is optional, we highly recommend setting it up so that you can see the status of your messages and troubleshoot configuration issues.

  8. On the Review and create page, review your choices to make sure they are correct.

    • If you want to edit any of your settings, choose Edit next to the step that you want to change.

      Note

      If you edit a step, we recommend that you review each step after the step that 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 several minutes before the status for your new server changes to Online. At that point, your server can perform file operations for your users.