Working with AWS Directory Service for Microsoft Active Directory - AWS Transfer Family

Working with AWS Directory Service for Microsoft Active Directory

You can use AWS Transfer Family to authenticate your file transfer end users using AWS Directory Service for Microsoft Active Directory. It enables seamless migration of file transfer workflows that rely on Active Directory authentication without changing end users’ credentials or needing a custom authorizer.

With AWS Managed Microsoft AD, you can securely provide AWS Directory Service users and groups access over SFTP, FTPS, and FTP for data stored in Amazon Simple Storage Service (Amazon S3) or Amazon Elastic File System (Amazon EFS). If you use Active Directory to store your users’ credentials, you now have an easier way to enable file transfers for these users.

You can provide access to Active Directory groups in AWS Managed Microsoft AD in your on-premises environment or in the AWS Cloud using Active Directory connectors. You can give users that are already configured in your Microsoft Windows environment, either in the AWS Cloud or in their on-premises network, access to an AWS Transfer Family server that uses AWS Managed Microsoft AD for identity.

Note

Transfer Family does not support Simple AD.

To use AWS Managed Microsoft AD, you must perform the following steps:

  1. Create one or more AWS Managed Microsoft AD directories using the AWS Directory Service console.

  2. Use the Transfer Family console to create a server that uses AWS Managed Microsoft AD as its identity provider.

  3. Create access from one or more of your AWS Directory Service groups.

  4. Although not required, we recommend that you test and verify user access.

Before you start

Before you can use AWS Managed Microsoft AD, you must provide a unique identifier for each group in your Microsoft AD directory. You can use the security identifier (SID) for each group to do this. The users of the group that you associate have access to your Amazon S3 or Amazon EFS resources over the enabled protocols using AWS Transfer Family.

Use the following Windows PowerShell command to retrieve the SID for a group, replacing YourGroupName with the name of the group.

Get-ADGroup -Filter {samAccountName -like "YourGroupName*"} -Properties * | Select SamAccountName,ObjectSid

Choosing AWS Managed Microsoft AD as your identity provider

This section describes how to use AWS Directory Service for Microsoft Active Directory with a server.

To use AWS Managed Microsoft AD with Transfer Family

  1. Sign in to the AWS Management Console and open the AWS Directory Service console at https://console.aws.amazon.com/directoryservicev2/.

    Use the AWS Directory Service console to configure one or more managed directories. For more information, see AWS Managed Microsoft AD in the AWS Directory Service Admin Guide.

    
                        Console screenshot of the Directory Service console showing a list
                            of directories.
  2. Open the AWS Transfer Family console at https://console.aws.amazon.com/transfer/, and choose Create server.

  3. On the Choose protocols page, choose one or more protocols from the list.

    Note

    If you select FTPS, you must provide the AWS Certificate Manager certificate.

  4. For Choose an identity provider, choose AWS Directory Service.

    
                        Console screenshot showing Choose identity provider section with
                            Directory Service selected.
  5. The Directory list contains all the managed directories that you have configured. Choose a directory from the list, and choose Next.

    Note

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

  6. To finish creating the server, use one of the following procedures:

    In those procedures, continue with the step that follows choosing an identity provider.

Important

You can't delete a Microsoft AD directory in AWS Directory Service if you used it in a Transfer Family server. You must delete the server first, and then you can delete the directory.

Granting access to groups

After you create the server, you must choose which groups in the directory should have access to upload and download files over the enabled protocols using AWS Transfer Family. You do this by creating an access.

Note

Users must belong directly to the group to which you are granting access. For example, assume that Bob is a user and he belongs to groupA, and groupA itself is included in groupB.

  • If you grant access to groupA, Bob is granted access.

  • If you grant access to groupB (and not to groupA), Bob does not have access.

To grant access to a group

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

  2. Navigate to your server details page.

  3. In the Accesses section, choose Create access.

  4. Enter the SID for the AWS Managed Microsoft AD directory that you want to have access to this server.

    Note

    For information about how to find the SID for your group, see Before you start.

  5. For Access, choose an AWS Identity and Access Management (IAM) role for the group.

  6. In the Policy section, choose a policy. The default setting is None.

  7. For Home directory, choose an S3 bucket that corresponds to the group's home directory.

    Note

    You can limit the portions of the bucket that users see by creating a session policy. For example, to limit users to their own folder under the /filetest directory, enter the following text in the box.

    /filetest/${transfer:UserName}

    To learn more about creating a session policy, see Creating a session policy for an Amazon S3 bucket.

  8. Choose Add to create the association.

  9. Choose your server.

  10. Choose Create access.

    1. Enter the SID for the group.

      Note

      For information about how to find the SID, see Before you start.

  11. Choose Create access.

In the Accesses section, the accesses for the server are listed.


                Console screenshot showing the Accesses section with the server accesses
                    listed.

Testing users

You can test whether a user has access to the AWS Managed Microsoft AD directory for your server.

Note

A user must be in exactly one group (an external ID) that is listed in the Access section of the Endpoint configuration page. If the user is in no groups, or is in more than a single group, that user is not granted access.

To test whether a specific user has access

  1. On the server details page, choose Actions, and then choose Test.

  2. For Identity provider testing, enter the user name and password for a user that is in one of the groups that has access.

  3. Choose Test.

You see a successful identity provider test, showing that the selected user has been granted access to the server.


                Console screenshot of the successful identity provider testing
                    response.

If the user belongs to more than one group that has access, you receive the following response.

"Response":"", "StatusCode":200, "Message":"More than one associated access found for user's groups."

Deleting server access for a group

To delete server access for a group

  1. On the server details page, choose Actions, and then choose Delete Access.

  2. In the dialog box, confirm that you want to remove access for this group.

When you return to the server details page, you see that the access for this group is no longer listed.

Connecting to the server using SSH (Secure Shell)

After you configure your server and users, you can connect to the server using SSH and use the fully qualified user name for a user that has access.

sftp user@active-directory-domain@vpc-endpoint

For example: transferuserexample@mycompany.com@vpce-0123456abcdef-789xyz.vpc-svc-987654zyxabc.us-east-1.vpce.amazonaws.com

This format targets the search of the federation, limiting the search of a potentially large Active Directory.

Note

You can specify the simple user name. However, in this case, the Active Directory code has to search all the directories in the federation. This might limit the search, and authentication might fail even if the user should have access.

After authenticating, the user is located in the home directory that you specified when you configured the user.