Public VIF for filetransfer over AWS Direct Connect

0

A public VIF uses a public IP address to access all AWS public services such as S3. Does this means that file transfer will take place over internet and not direct connect ?

Use case here is to push the data from On Prem FTP Client over P2P link and receive it over AWS Direct Connect on S3.

Just want to keep everything secure.

5 Answers
0

Hi,

The right way to ensure that your traffic doesn't leave your private VPC is to create a private service endpoint in your VPC. S3 supports private service endpoints.

This excellent blog will show you all the options at hand with S3 to best match your use case.

Best,

Didier

profile pictureAWS
EXPERT
answered 6 months ago
  • please share the blog link

0

No. Using public VIF you can access all AWS public services using public IP addresses through AWS Direct Connect.

Public virtual interface prefix advertisement rules: We advertise appropriate Amazon prefixes to you so that you can reach either your VPCs or other AWS services. You can access all AWS prefixes through this connection; for example, Amazon EC2, Amazon S3, and Amazon.com. You do not have access to non-Amazon prefixes. For a current list of prefixes advertised by AWS, see AWS IP Address Ranges in the Amazon Web Services General Reference. AWS does not re-advertise customer prefixes that were received over AWS Direct Connect public virtual interfaces to other customers. For more information about public virtual interfaces and routing policies, see Public virtual interface routing policies. https://docs.aws.amazon.com/directconnect/latest/UserGuide/WorkingWithVirtualInterfaces.html

Note We recommend that you use a firewall filter (based on the source/destination address of packets) to control traffic to and from some prefixes. If you're using a prefix filter (route map), ensure that it accepts prefixes with an exact match or longer. Prefixes advertised from AWS Direct Connect may be aggregated and may differ from the prefixes defined in your prefix filter.

AWS
answered 6 months ago
0

See this re:Post article:

How can I access my Amazon S3 bucket over Direct Connect?

After the BGP over Public Virtual Interface is up and established, the Direct Connect router advertises all global public IP prefixes, including Amazon S3 prefixes. Traffic heading to Amazon S3 is routed through the Direct Connect public virtual interface. The public virtual interface is routed through a private network connection between AWS and your data center or corporate network.

profile pictureAWS
EXPERT
answered 6 months ago
0

This YouTube video discusses Public VIF and how connectivity to public-facing AWS services: https://youtu.be/X_4ekgRc4C8?si=k0B4im6Feonv7EC3&t=328

profile pictureAWS
EXPERT
answered 6 months ago
0

Topology and Routing: AWS Service (e.g., Amazon S3) <> AWS Direct Connect (Public VIF) <> On-Premises

This setup offers direct on-premises network access to AWS services within a specific region. It involves handling public IP addresses and a large volume of routes. To manage this effectively:

1/ Route Filtering: Use BGP communities and/or the ipranges.json file to filter routes. This controls how your traffic is routed within AWS, either locally, continent-wide, or globally. BGP Communities [1]: These tags (like 7224:9100 for local regions, 7224:9200 for all AWS Regions for a continent (North America, Asia Pacific and Europe, the Middle East and Africa), or 7224:9300 for global AWS regions) help in advertising your prefixes appropriately, based on your geographical or network needs. By default, prefixes are advertised globally to all public AWS Regions. For outbound routing policies, AWS Direct Connect applies the BGP communities to its advertised routes mentioned in the document [1]. If you want to receive all AWS public prefixes, you need not apply any filter. ipranges.json [2]: Utilize this AWS-provided JSON file for a more tailored approach to routing, especially if you're focusing on specific services like S3.

2/ Enhanced Security Measures: Adding a security layer is crucial for protecting your data as it moves between AWS and your on-premises network: Recommended Setup: AWS ServiceAWS Direct Connect (Public VIF)  {Firewall/NAT} On-Premises

This setup helps safeguard against vulnerabilities and unauthorized access. For Example: Other VPCs (VPC-B, VPC-C): Ensures that traffic from VPCs outside your control doesn’t compromise your on-premises network security.

(You are NOT owner) Application VPC-B ↔ IGW ↔ AWS Direct Connect (Public VIF) ↔ On-Premises (You are NOT owner) Application VPC-C ←VGW→ VPN ←→ AWS Direct Connect (Public VIF) ←→On-Premises

Implementing a Firewall or NAT provides a monitored and controlled access point, maintaining a secure flow of authorized traffic and bolstering your defense against potential security threats. Proper configuration and ongoing maintenance of these security measures are vital.

References: [1]: Public VIF BGP communities: https://docs.aws.amazon.com/directconnect/latest/UserGuide/routing-and-bgp.html#bgp-communities [2]: AWS IP address ranges: https://docs.aws.amazon.com/vpc/latest/userguide/aws-ip-ranges.html

AWS
answered a month ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions