Improve your security with Dynamic Provider Credentials for Terraform Cloud and Azure

Terraform Cloud and Azure | Hands-on Tutorial | Terraform

Dynamic provider credentials in Terraform Cloud automates the creation of short-lived credentials for access to Azure. This eliminates the risk and effort involved in handling and rotating static credentials for Terraform runs.

Using static credentials in your workspaces to authenticate providers presents a security risk, even if you rotate your credentials regularly. Dynamic provider credentials improve your security posture by letting you provision new, temporary credentials for each run. This capability is available for all tiers of Terraform Cloud and it's also available now in Terraform Enterprise.

▬▬▬▬▬▬ TIMESTAMPS ⌚ ▬▬▬▬▬▬

0:52 - Challenges with static credentials
3:06 - What are dynamic provider credentials?
4:23 - Demo: bootstrap the trust relationship
6:48 - Demo: workspace configuration
8:14 - How the process works
9:04 - End result and summary

▬▬▬▬▬▬ WANT TO LEARN MORE? 🚀 ▬▬▬▬▬▬



#IaC #infrastructureascode #DevOps #Azure #Learning #Cloud #devopstutorial @MicrosoftDeveloper @MicrosoftReactor ​

[acodersjourney]

Thanks for being a reliable source of knowledge.

[koodauskanava]

Do you need to specify claim so exact, or can you just define terraform cloud organization and maybe project? So all workspaces in certain project can use the client id/app reg? How does this scale if one have 1000 workspaces? Do you need to create 1000 app regs with claims to each workspace?