SAP on AWS · Hybrid Connectivity: On-Premises to AWS

A global company wants its multiple data centers and offices to talk to each other through AWS, not over the internet. Someone proposes a mesh of site-to-site VPNs. Which Direct Connect feature is the cleaner fit, and what's the key distinction?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in Hybrid Connectivity: On-Premises to AWS

You need to connect a remote branch office network (not individual laptops) to AWS over an encrypted tunnel, and you want redundancy. Which of the four AWS VPN options fits, and which one is the trap?

An SAP org refuses any internet-path connectivity to AWS. Given that a VPN is encrypted and quick to set up, why do most of them still choose Direct Connect instead?

You have one VPN/Direct Connect on-prem link and a growing number of VPCs that all need to reach it and each other. Why does stitching them with VPC peering break down, and what fixes it?

Two requirements land separately: (a) traffic must be encrypted in transit, (b) traffic must never touch the public internet. One is satisfied by VPN, the other by Direct Connect. Which is which, and why can't you assume one gives you both?

You need a Direct Connect link sized above 10 Gbps. Does it matter whether you go dedicated or hosted (through a delivery partner), and why?

Your footprint is expanding into a second AWS region. Can a single Transit Gateway cover both, and what does its OSI layer tell you about what it can route?

Start learning today

Free to start — download the app or use it in your browser.