Next, we walk through how to configure this architecture in detail. First, we discuss the basic architectural components of a common deployment scenario for AWS SFTP. In this blog, we show you how to use these new features to further increase the security of your AWS SFTP servers. This enables end users behind firewalls to whitelist access to the SFTP server via a static IP, or a pair of IPs for failover. Additionally, customers can now associate Elastic IP addresses with their server endpoint. End users outside of the allowed IP address list are unable to connect to the server. Using security groups, customers can apply rules to limit SFTP access to specific public IPv4 addresses or IPv4 address ranges. To provide additional security for VPC hosted endpoints, we recently added support for VPC Security Groups and Elastic IP addresses. Alternatively, you can use VPC hosted endpoints for greater control over how users access your SFTP servers. You can use Public endpoints to quickly and easily provide internet access to your AWS SFTP servers. You can deploy an AWS SFTP server using Public endpoints or Virtual Private Cloud (VPC) hosted endpoints. AWS Transfer for SFTP (AWS SFTP) fulfills this need by providing a fully managed service enabling transfers over SFTP, while the data is stored in Amazon Simple Storage Service (Amazon S3). SFTP provides a mature and secure transport mechanism for transporting these files, using the same public and private key encryption mechanisms employed by the SSH protocol. Examples of such data include financial records, media files, or sensitive information such as health records or personal finance data. AWS customers across a wide variety of industries must often exchange data with other organizations using the standard SSH File Transfer Protocol (SFTP).
0 Comments
Leave a Reply. |