Questions tagged with AWS Transfer Family
Content language: English
Sort by most recent
AWS Transfer Family is pleased to announce the following enhancements to the managed workflows capability. 1. You can now configure your workflow steps to process either the originally uploaded file or the output file from the previous workflow step. You can also make multiple copies of a file and archive the original source file for records retention. 2. You can now utilize username as a variable in workflows copy steps, enabling you to dynamically route files to user-specific folders in Amazon S3. 3. You can now use AWS CloudFormation to configure and deploy managed workflows in a standardized and repeatable way across multiple regions and accounts. 4. Also, you now have access to AWS CloudWatch metrics such as total number of executions, successful executions and failed executions for your Workflows. To learn more, please visit our managed Workflows documentation  or the blog post  for additional details.  https://docs.aws.amazon.com/transfer/latest/userguide/transfer-workflows.html  https://aws.amazon.com/blogs/architecture/building-a-cloud-native-file-transfer-platform-using-aws-transfer-family-workflows/
AWS Transfer Family servers can now display customized messages, such as organizational policies or terms and conditions to your end users, helping you achieve your legal and compliance requirements. You can also present a customized Message of The Day (MOTD), such as a greeting message, to enhance user experience. To learn more about using login banners with AWS Transfer Family, please find details in our documentation - https://docs.aws.amazon.com/transfer/latest/userguide/create-server-sftp.html
I have an AWS Transfer server running using an AWS Hosted Active Directory for authentication. I have a two way transitive domain trust in place with an on-premise Active Directory domain. Is it possible to use security groups form the trusted domain to grant access? I have tried to add Group SID's from the trusted domain but this results the following error: Failed to add access (1 validation error detected: Value ' <SID> at 'externalId' failed to satisfy constraint: Member must satisfy regular expression pattern: ^S-1-[\d-]+$) Setting up Access with a SID from the AWS Directory Service is working as expected.
The Endpoint is too long for the field that gets filled in for the SFTP software on customer end . Given AWS Endpoint is 59 characters long and the field only supports 55 characters. Do you know if there is a way for us to get a shorter one?
Hello All, I have deleted my sftp server in transfer family that contain all my users. Worst i don't have any inventory for the users. How do i recover.
I have an AWS Transfer requirement where I need to provide key based authentication as you get from the Service Managed identity provider, and AWS Directory Service authentication. Is this possible from a single server?
What IAM policies can be used to replicate the two demos in [AWS Transfer Family Managed Workflows Demo | Amazon Web Services](https://www.youtube.com/watch?v=t-iNqCRospw)?
My team has an app running on both Android and iOS that needs to upload media files (video ad images) to an s3 bucket. The solution was implemented using S3 Transferutility and it was working fine, but we discovered this week that we are having some issues on Android. Now, when we try to upload a media file on Android OS the transfers state keeps waiting indefinitely. iOS is working fine. AWS SDK Core: 2.18.0 Does any one of you have any suggestion on what could it be?
I am working on a CF template to deploy a AWS Transfer server. I am using EndPointType=VPC and I need to be able to specify the IP's of the network interfaces for two subnets. From the https://docs.aws.amazon.com/transfer/latest/userguide/API_EndpointDetails.html I can see that I need to use the AddressAllocationIds statement. This only appears to be possible via the UpdateServer API. I guess I need to call the UpdateServer API after the AWS::Transfer::Server block in the template? Is there an example of this available anywhere?
Starting today, AWS Transfer Family is available in the Asia Pacific (Osaka) Region. AWS Transfer Family provides fully managed file transfers for Amazon Simple Storage Service (Amazon S3) and Amazon Elastic File System (EFS). With this launch, AWS Transfer Family is now available in 21 commercial AWS regions, AWS GovCloud (US) Regions, Amazon China (Beijing) Region, operated by Sinnet, and the Amazon China (Ningxia) Region, operated by NWCD. AWS Transfer Family supports file transfers over Secure File Transfer Protocol (SFTP), File Transfer Protocol (FTP) and FTP over SSL (FTPS), simplifying and accelerating migration of file transfer workflows to AWS. For more information, visit the AWS Transfer Family product page and see the AWS Region Table for complete regional availability information.
When we try to send a file from Unix box to S3 bucket via AWS transfer family resolve hostname of Endpoint is not found correctly and there is error generate for SFTP logs "changing state from STATE_NOT CONNECTED to STATE_CLOSED" and connection timeout. For the last 6 months, File transfer was successful without any issues. Below are errors in cloudwatch logs of the AWS transfer family: ERRORS KEX_FAILURE MESSAGE= "no matching key exchange method found" Kex=diffie-hellman-group1-sha1
I created a SFTP server in AWS Transfer family connected to an S3 bucket with the service managing the users. Created 3 users and it was all working fine. I created a fourth user (with the same IAM role attached as the working users) and it did not work and received an SSH AUTH FAILURE when trying to connect. So I added the public key to the user again (assuming I had screwed up). The two keys both show the same fingerprint in the AWS transfer console so I didn't screw up. But still does not work. However, when I checked the fingerprint of the key locally using 'ssh-keygen -l -f <keyname>' I get a totally different fingerprint to the one shown against the keys for that user. So I removed the key from one of the working users and added the exact same public key back in. That user no longer works but the public key has not changed. What am I doing wrong here?