AWS re:Invent 2020: Building with AWS PrivateLink, Gateway Load Balancer, and AWS Partners

Поделиться
HTML-код
  • Опубликовано: 12 сен 2024

Комментарии • 4

  • @jameswenzel7545
    @jameswenzel7545 3 года назад +1

    Correction - At 10:17 In my example the NLB and the animation slides it and the ingress routing rules on top of the existing VPC to highlight that it needed to be hit first for decryption to work which can be confusing. To be clear the NLB (Network Load Balancer) needs to be in a different VPC than the GWLBEs for routing to work.

  • @laura7z416
    @laura7z416 17 дней назад

    The IGW table at 3:40 seems wrong. It should be Destination and Target, instead of Target and GW....

    • @awssupport
      @awssupport 17 дней назад

      Hi there, thanks for your feedback! After all it's how we get better. I will reach out to the appropriate team, and get some visibility on this. ^DC

  • @vnkalisa
    @vnkalisa 2 года назад

    Hello
    I would like can you spin up Gateway load balancer. In the same VPC in as your instance instead of having it in a separate VPC?
    I understand the best practice is to have it and firewalls in different VPC. But us we wanted in the same