Establishing a Private Connection to Amazon Redshift from On-Premises Network

Establishing a Private Connection to Amazon Redshift from On-Premises Network

Prev Question Next Question

Question

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)?

Answers

Explanations

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.html

When migrating an on-premises data warehouse to Amazon Redshift, it's important to establish a secure and reliable connection between the on-premises network and Amazon Redshift. Two methods that can be used to establish a private connection are:

  1. Site-to-site VPN: A VPN, or Virtual Private Network, creates an encrypted connection between the on-premises network and Amazon Redshift. With a site-to-site VPN, the on-premises network and Amazon Redshift are connected as if they were on the same network, allowing for secure and direct communication. A site-to-site VPN is a good option when there is an existing VPN infrastructure in place and the on-premises network is not located near an AWS Direct Connect location.

  2. Direct Connect: AWS Direct Connect provides a dedicated network connection between the on-premises network and Amazon Redshift. This connection bypasses the public internet, providing a more reliable and consistent connection. Direct Connect can be a good option when large amounts of data need to be transferred between the on-premises network and Amazon Redshift, as it provides a high-bandwidth, low-latency connection.

Additionally, the other options mentioned in the question are:

  • VPC Peering: VPC peering allows for private connectivity between VPCs in the same or different AWS accounts. However, it cannot be used to establish a private connection between an on-premises network and Amazon Redshift.
  • PrivateLink Interface Endpoint: A PrivateLink interface endpoint allows for private connectivity between VPCs and AWS services over the AWS network. It is not used for connecting an on-premises network to Amazon Redshift.
  • PrivateLink Gateway Endpoint: A PrivateLink gateway endpoint allows for private connectivity between an on-premises network and AWS services over the AWS network. However, it is not used for connecting an on-premises network to Amazon Redshift.

Therefore, the correct answers to the question are A. Site-to-site VPN and C. Direct Connect.

Prev Question Next Question