How do I transfer files between a local computer and a WorkSpace?
I want to transfer a file between my local desktop and Amazon WorkSpaces, but I don’t know how. Or, when I transfer files, I experience high latency.
Resolution
For Amazon DCV WorkSpaces, you can use the file transfer feature to transfer files between a local client and WorkSpaces. To configure file transfer, you must be a WorkSpaces administrator. You must also use a Windows client, Linux client, or web access, and the WorkSpaces client must be version 5.23.0 or later.
You can't use the file transfer feature for PCoIP WorkSpaces. To transfer a text file, copy the text, and then paste the text into a new text file in WorkSpaces. For other file types, take one of the following actions.
Use Amazon S3
Upload the files to an Amazon Simple Storage Service (Amazon S3) bucket from your local machine. Then, download the files into your WorkSpace.
Or, use the AWS Command Line Interface (AWS CLI) to allow the WorkSpace to access the S3 bucket with your files.
Note: If you receive errors when you run AWS CLI commands, then see Troubleshooting errors for the AWS CLI. Also, make sure that you're using the most recent AWS CLI version.
Complete the following steps:
- To grant your WorkSpace permission to access the S3 bucket, run the configure command:
Note: You can use AWS Identity and Access Management (IAM) to manage the access keys for your IAM users.$ aws configure
- To list your S3 buckets, run the ls command:
Note: To create an IAM policy that allows read and write access to the bucket, see Allowing read and write access to an Amazon S3 bucket.$ aws s3 ls
- In the command's output, verify that your S3 bucket is on the list.
- To download the files from the S3 bucket to your WorkSpace, run the cp command:
Note: Replace testbucket with your bucket name, username with your username, and file.txt with your file.aws s3 cp s3://testbucket/file.txt D:\Users\username\Desktop
Use FSx for Windows File Server
Complete the following steps:
- Create an Amazon FSx for Windows File Server file system.
- To integrate your file system with WorkSpaces, join the file system with AWS Directory Service for Microsoft Active Directory or a self-managed Microsoft Active Directory.
- Configure your file system to be accessible from your local machine and your WorkSpace. On your local machine, set up network connectivity with the virtual private cloud (VPC) where the FSx for Windows File Server is located. To set up access to the VPC from an on-premises environment, use AWS Direct Connect or AWS VPN.
- Configure the network security groups and firewall rules. They must allow inbound SMB traffic on TCP port 445 from the local machine and WorkSpaces environments to the Amazon FSx file system's security group.
- From the local Windows computer, map the Amazon FSx file share as a network drive. Use the DNS name or preferred IP address of the Amazon FSx file system.
- From the WorkSpace, map the Amazon FSx file share as a network drive.
Use an external storage system
Use an external storage system, such as an AWS Transfer Family server, OneDrive, or Dropbox. Copy the file to the external storage system. Then, open the external storage system on the WorkSpace, and download the file.
Use a VPN
Use AWS Client VPN to establish a VPN connection to a VPC.
High latency when you transfer data
If you experience performance issues when you transfer data between your WorkSpace and a local computer, then take the following actions:
- To view your resource usage during the transfer, check the CPUUsage, MemoryUsage, UserVolumeDiskUsage, and RootVolumeDiskUsage Amazon CloudWatch metrics.
- Run a Wireshark capture when you transfer the file to determine whether there are networking issues.
- Use the Process Monitor tool to run a capture when you transfer the file. To access the tool, see Process Monitor v4.01 on the Microsoft website.
Note: High CPU levels or overall low bandwidth from the client to the source can slow file transfers.
Conteúdo relevante
- AWS OFICIALAtualizada há 2 anos
- AWS OFICIALAtualizada há 2 anos
- AWS OFICIALAtualizada há 2 anos
- AWS OFICIALAtualizada há 2 anos