Multi-Account Architectures with AWS Landing Zone

Поделиться
HTML-код
  • Опубликовано: 21 июл 2024
  • When multiple teams require access to AWS, how do you automate permissions while limiting your exposure to threats and unintended changes? In the webinar, Logicworks' Solution Architect defines when it makes sense to abandon the traditional VPC Hub & Spoke model and instead build a multi-account environment - AWS Landing Zone.
  • НаукаНаука

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

  • @vbalahellomayicomein
    @vbalahellomayicomein 4 года назад +1

    Neat and clear explanation of landing zone 👍

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

    Link to slides? Very hard to see details in the video.

  • @laxplayer088
    @laxplayer088 5 лет назад

    11:40 - Why Landing Zone is perfect for SaaS companies with single-tenant applications!

  • @Leobatchops
    @Leobatchops 3 года назад

    Referring Slides, can publicly accessible?

  • @virabadrasana
    @virabadrasana 3 года назад

    Should we use Control Tower instead of Landing Zone these days?

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

      Depends on the granularity of the control you need. Control Tower gives some of that up for simplicity and automation.

  • @bvr333
    @bvr333 Год назад +1

    Hi @Logicworks,
    Could you answer the following doubts
    1.can we use unencrypted EBS volumes for EC2 in this Landing zone environment,
    2.can the IAM users be given Power admin access

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

    If your workload is running on 5 dollars then you are doing something wrong.