AWS Organizations | Organizational Units | Service Control Policies | Detail Demo |

Поділитися
Вставка
  • Опубліковано 30 січ 2025

КОМЕНТАРІ • 14

  • @prashantsukhadeve9642
    @prashantsukhadeve9642 10 днів тому

    Thanks You so much

  • @sandipram5022
    @sandipram5022 Рік тому

    Great explanation. More than a teacher kind. Thanks Guruji.

  • @चाकूदेवी-तलवारवाली

    Awesome. I m using this from 1 yr. But some doubts cleared. Thanks

  • @sajliperween74
    @sajliperween74 Рік тому

    THANKS A LOT ❣

  • @chandershekher6631
    @chandershekher6631 Рік тому

    Awesome

  • @yogibisai647
    @yogibisai647 Рік тому

    Thank you.. very useful

  • @ajaydeepsinghrajpoot
    @ajaydeepsinghrajpoot 4 місяці тому

    "Automate aws acc creation and management, and provision resources with aws cloudformation stackset" you said you'll share this document at the end of series, but i couldn't find it anywhere.

  • @banjaraonweekends
    @banjaraonweekends 11 місяців тому

    Hey Bro, I have one query suppose in SCP we mention only T2 is allowed but we invite existing aws account in OU& it has M5 instance already.
    So what happens to existing instance ?

    • @Cloud4DevOps
      @Cloud4DevOps  11 місяців тому +2

      you will not be able to provision other then t2 , bt you will be able to see other then t2

  • @terrasystemlabs
    @terrasystemlabs 11 місяців тому

    if i have 10 clients should i create one account for each of them, OU is confusing me

  • @SarthakInUS
    @SarthakInUS Рік тому

    I have one doubt if a root user has aws full access policy it is delegated to all its children? how can we remove that in the children accounts.

  • @KarthikKumaresan-k1o
    @KarthikKumaresan-k1o Рік тому

    useful session but watch in 2x