AWS transfer documentation change
Summary
Added troubleshooting section for VPC egress type SFTP connector issues including connectivity, security groups, and configuration guidance
Security assessment
The changes document security-related configurations like security group rules (port 22) and NAT Gateway requirements, but do not address a specific security vulnerability. They provide operational guidance for secure network configurations rather than patching a security flaw.
Diff
diff --git a/transfer/latest/userguide/sftp-connectivity-issues.md b/transfer/latest/userguide/sftp-connectivity-issues.md index 32e27733a..e10c052bb 100644 --- a//transfer/latest/userguide/sftp-connectivity-issues.md +++ b//transfer/latest/userguide/sftp-connectivity-issues.md @@ -5 +5 @@ -Troubleshoot SFTP connectivity issuesTroubleshoot SFTP client issuesTroubleshoot file upload issues +Troubleshoot SFTP connectivity issuesTroubleshoot SFTP client issuesTroubleshoot file upload issuesTroubleshoot VPC egress type SFTP connector issues @@ -18,0 +19,2 @@ This section describes possible solutions for SFTP connectivity and file transfe + * Troubleshoot VPC egress type SFTP connector issues + @@ -90,0 +93,74 @@ To solve this problem, review your client application for file name character en +## Troubleshoot VPC egress type SFTP connector issues + +If you're experiencing issues with VPC egress type SFTP connectors, check the following: + +### Connector status is PENDING + +Description + +Your VPC egress type connector remains in PENDING status for several minutes after creation, and TestConnection returns "Connector not available". + +Cause + +DNS resolution for VPC connectors can take several minutes to complete after creation. + +Solution + +Wait for the connector status to become ACTIVE before attempting file transfers. This is normal behavior for VPC egress type connectors. + +### Connection timeouts + +Description + +Your VPC egress type connector times out when attempting to connect to the SFTP server. + +Cause + +Security groups may not allow traffic on port 22 between your Resource Gateway subnets and the target SFTP server. + +Solution + +Verify that security groups allow traffic on port 22 between your Resource Gateway subnets and the target SFTP server. + +### Resource Configuration errors + +Description + +Your VPC egress type connector fails to connect due to Resource Configuration issues. + +Cause + +The Resource Configuration may point to an incorrect IP address or DNS name, or the Resource Gateway may not be in the same VPC as your SFTP server (for private endpoints). + +Solution + +Ensure your Resource Configuration points to the correct IP address or DNS name, and that the Resource Gateway is in the same VPC as your SFTP server (for private endpoints). For more information, see [Resource configurations](https://docs.aws.amazon.com/vpc-lattice/latest/ug/resource-configuration.html) in the _Amazon VPC Lattice User Guide_. + +### Public endpoint issues + +Description + +Your VPC egress type connector cannot connect to public SFTP endpoints. + +Cause + +For public endpoints, you must use a DNS name (not an IP address) in your Resource Configuration, and your VPC must have a NAT Gateway for outbound internet access. + +Solution + +Ensure you're using a DNS name, not an IP address, in your Resource Configuration. Verify that your VPC has a NAT Gateway for outbound internet access. + +### Availability Zone issues + +Description + +You cannot create a Resource Gateway due to Availability Zone limitations. + +Cause + +Resource Gateways require subnets in at least 2 Availability Zones, and not all AZs support VPC Lattice. + +Solution + +Check the supported Availability Zones for VPC Lattice in your region and ensure you have subnets in at least 2 supported AZs. + @@ -97 +173 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Authentication issues +SFTP connector issues