Question
Is it possible to encrypt communication in HULFT Transfer with IPsec?
Answer
It is not possible to encrypt the entire file transfer communication in HULFT Transfer with IPSec.
However, it is possible to encrypt a part of the communication path with IPsec under the following conditions.
[Description]
HULFT Transfer communicates with a destination system via a VPC that is created on a customer's AWS environment.
E.g. HULFT Square - VPC on customer's AWS environment - On-premise HULFT
In this case, HULFT Square and VPC on customer's AWS environment communicates with PrivateLink, and VPC on customer's AWS environment and on-premise HULFT communicates with DirectConnect or VPN.
Considering the above, only when VPC on customer's AWS environment and on-premise HULFT communicates with VPN, it is possible to encrypt this route with IPsec.
Connect your VPC to remote networks using AWS Virtual Private Network
https://docs.aws.amazon.com/vpc/latest/userguide/vpn-connections.html
VPN connectivity option: AWS Site-to-Site VPN
Description: You can create an IPsec VPN connection between your VPC and your remote network.
What is AWS Site-to-Site VPN?
https://docs.aws.amazon.com/vpn/latest/s2svpn/VPC_VPN.html
Site-to-Site VPN supports Internet Protocol security (IPsec) VPN connections.
Please contact AWS for more information on how to encrypt communication between a VPC and an on-premise server using a VPN with IPsec.
Supplementary information
PrivateLink is a private connection within the AWS network, so the security during file transfer in HULFT Transfer is ensured by PrivateLink.
For details on PrivateLink, please refer to the following manual.
PrivateLink
Comments
0 comments
Article is closed for comments.