A company is migrating its on-premises data warehouse to Amazon Redshift.
What methods can be used to establish a private connection from on-premises network to Amazon Redshift (Select TWO)?
Click on the arrows to vote for the correct answer
A. B. C. D. E.Answer: B and C.
Option A is incorrect because VPC peering is used to establish connectivity between two Amazon VPC's.
Option B is CORRECT because Site-to-site VPN can be used to establish a secure and private connection between an on-premises network and Amazon VPC over the Internet.
Option C is CORRECT because AWS Direct Connect can be used to establish a secure and private connection between an on-premises network and Amazon VPC over a dedicated line.
Options D and E are incorrect because PrivateLink endpoints are used to integrate AWS services to Amazon VPC without the use of Internet Gateway.
Reference:
https://docs.aws.amazon.com/redshift/latest/mgmt/network-isolation.htmlWhen a company migrates its on-premises data warehouse to Amazon Redshift, it needs to establish a secure and reliable connection between its on-premises network and Amazon Redshift. There are several methods to establish a private connection from on-premises network to Amazon Redshift. Two possible methods are VPC Peering and Site-to-site VPN.
VPC Peering: Amazon Virtual Private Cloud (VPC) peering allows you to connect two VPCs privately through a virtual network. VPC peering can be used to connect your on-premises network with Amazon Redshift by creating a VPC peering connection between your VPC and the Amazon Redshift VPC. This method is simple and cost-effective because it uses the Amazon network to securely transfer data between the two networks. Additionally, it enables you to use the Amazon Redshift VPC security groups to control access to your Redshift cluster.
Site-to-site VPN: Site-to-site VPN is another option for connecting your on-premises network with Amazon Redshift. This method uses an encrypted virtual tunnel to securely transfer data between your on-premises network and Amazon Redshift. It requires you to configure a VPN gateway on your on-premises network and a virtual private gateway on the Amazon Redshift VPC. Once configured, the VPN tunnel can be used to transfer data between the two networks.
The other three options listed in the question are not relevant to connecting an on-premises network to Amazon Redshift:
Direct Connect: Direct Connect is a method for establishing a dedicated network connection between your on-premises network and AWS. It is used for high-bandwidth and low-latency connectivity to AWS services, but it is not necessary for connecting to Amazon Redshift.
PrivateLink Interface Endpoint: PrivateLink Interface Endpoint enables private connectivity between your VPC and services powered by AWS PrivateLink. It is used to access AWS services through a private IP address within your VPC. However, it is not used to establish a private connection to Amazon Redshift.
PrivateLink Gateway Endpoint: PrivateLink Gateway Endpoint is used to access services outside your VPC that are not available through AWS PrivateLink. It does not provide a private connection to Amazon Redshift.
In summary, the two methods that can be used to establish a private connection from an on-premises network to Amazon Redshift are VPC Peering and Site-to-site VPN.