A studio needs its own AWS Direct Connect port speed, not a slice of a partner's shared port. Which attachment matches?
Select an answer to reveal the explanation.
Short Explanation
You asked for the whole driveway, not a painted lane on someone else's. You order a dedicated Direct Connect connection at the port speed you need. A hosted connection is a slice of a partner port, and an internet VPN does not reserve the port at all.
Full Explanation
A dedicated Direct Connect connection is the customer's own port at a stated speed. That matches a studio that refuses a slice of a shared partner port. A hosted connection is allocated bandwidth on a partner's port. It can be the right commercial choice, and it is still a shared port rather than the studio's own. An internet VPN has no Direct Connect port speed. Throughput follows the public path and the VPN gateway. A public virtual interface on someone else's connection does not give the studio a private port, and a public virtual interface is aimed at public AWS services rather than a private VPC attachment the studio controls. Exam caveat: dedicated still needs a virtual interface and a gateway association before the VPC is reachable. The port alone is not the route. Operational check: the connection should show a dedicated port at the ordered speed in the studio's own account, not a hosted VLAN allocated by a partner.