AWS re:Invent 2024 -Simplify cross-VPC resource access with PrivateLink and VPC Lattice (NET218-NEW)

แชร์
ฝัง
  • เผยแพร่เมื่อ 14 ธ.ค. 2024

ความคิดเห็น • 6

  • @CarlosMendioroz
    @CarlosMendioroz 4 วันที่ผ่านมา

    Why do you say TG works at layer 4 ?

    • @awssupport
      @awssupport 3 วันที่ผ่านมา

      Hi Carlos, great question! I found our documentation on How Amazon VPC Transit Gateways work, which may help clarify: ➡️ go.aws/4gdxFRW. You can also share your question on re:Post to gain further insights from the community: go.aws/aws-repost. 🔎 ^TH

    • @CarlosMendioroz
      @CarlosMendioroz 3 วันที่ผ่านมา

      @@awssupport Well, AFAIK TG works at layer 3, PL at layer 4. It confuses me and I guess anyone with networking backgroud. IP routes are L3...

    • @nismerf9518
      @nismerf9518 2 วันที่ผ่านมา

      @@CarlosMendioroz Hi Carlos Thanks for watching the video. In this video I was speaking about TCP (transfer control protocol) which operates at 4 in the OSI model. While it is true that IP is layer 3, the main functionality of TGW is not addressing, but connectivity and routing. Thanks for the question!

    • @CarlosMendioroz
      @CarlosMendioroz 2 วันที่ผ่านมา

      @@nismerf9518 I can review your video again, but TGW works at layer 3 and you where talking about TGW and stated layer 4...
      I understand you where comparing TGW to PL (which is a L4 solution) but still, I think your presentation is confusing.
      Just reviewed and you state, at 2'50: TGW and VPC peering, L4 access types in AWS. This is wrong.

    • @nismerf9518
      @nismerf9518 วันที่ผ่านมา

      You are correct, I reviewed the section and I misspoke, that is at layer 3. Good catch!