Terraform backend using S3 and Dynamodb with state locking | DevOps | Infrastructure as code

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

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

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

    Great explanation to the point, Thanks for uploading

  • @riyasudheen94
    @riyasudheen94 Год назад

    Awesome dear . You truly deserve a comment . Life changing

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

    Great explanation bruh

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

    Great explanations! Direct to the point and well done demo with all steps that were done

  • @atexnik
    @atexnik 3 месяца назад +1

    Thank you!

  • @akinsojihammed6057
    @akinsojihammed6057 2 года назад +1

    Well done, the demo is awesome

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

      Thanks Akinsoji. Glad it was helpful for you.

  • @legion_29
    @legion_29 2 года назад +1

    Great explanation

  • @vishnukr4573
    @vishnukr4573 2 года назад +1

    Good explanation sir. It is literally brief and straight to the point :), Thanks

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

    Good job 🔥 🔥 prithiviraj

  • @amanmanapure7753
    @amanmanapure7753 2 года назад +1

    Thanks, very well explained.

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

    you are awesome man..

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

    hello, i have done the state locking but in the console it is only showing release locks and in the dynamo db table it is showing the items , pleasse can you tell the issue

    • @ajitinamdartech
      @ajitinamdartech  Год назад

      Hi Utkarsh,
      Can you elaborate more on the issue?

    • @utkarshpatel7839
      @utkarshpatel7839 Год назад

      @@ajitinamdartech like when i am doing terraform plan so like in normal it shows acquiring locks and in the end show releasing locks but in my case in starting it is not showing acquiring lock but in the end it is showing releasing locks

  • @vladeb1104
    @vladeb1104 2 года назад +1

    in my case i've had to provide the access key for backend init: terraform init -backend-config="access_key=" -backend-config="secret_key="

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

      Did you configure aws credentials on your local machine. If yes, this was not required.

    • @samtx
      @samtx Год назад

      Maybe for running in gitlab click button terraform?

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

    Pease make a video for understanding the basic of Terraform.

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

      Sure Rahul. I have planned for more videos on Terraform.

  • @swapnapaleti6612
    @swapnapaleti6612 2 года назад +1

    Hi, I've three terraform state files as we are creating them module wise. Is there a way to store them in different paths rather than using workspaces?

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

      I don't know whether I understand your question correctly, but I keep my state files in S3 in different paths for individual projects / environments.

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

    Hi all,
    I have 4 envionmnets dev,testing,non prod and prod.
    how to manage my state files using s3 and dynamodb?
    do i need to create new s3 and dynamodb for every environment?
    what are the charges for using dynamodb?

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

      Maybe try workspaces

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

      Hi Harish,
      You can use the same S3 and DynamoDB for all environments. However if you want a tighter control over your state files, you may separate the dynamodb and s3 bucket if required.