---
title: "Discussion on \"Deploying Terraform to AWS with GitHub Actions and OIDC\" | Hashnode"
description: "Discussion on \"Deploying Terraform to AWS with GitHub Actions and OIDC\". With Terraform and GitHub Actions, you can automate infrastructure deployments to AWS while keeping control over what gets deployed. This guide shows how to build that pipeline and use OpenID Connect to give it temporary AWS access without storing long-lived access keys."
url: "https://hashnode.com/posts/deploying-terraform-to-aws-with-github-actions-and-oidc/6ae4f89cd1f5980215892834"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Deploying Terraform to AWS with GitHub Actions and OIDC](https://blog.turingts.com/deploying-terraform-to-aws-with-github-actions-and-oidc?utm_source=hashnode&utm_medium=feed)

With Terraform and GitHub Actions, you can automate infrastructure deployments to AWS while keeping control over what gets deployed. This guide shows how to build that pipeline and use OpenID Connect to give it temporary AWS access without storing long-lived access keys.

Oct 30 · 26 min read · blog.turingts.com  
Read the article

-   [#terraform](https://hashnode.com/tag/terraform)
-   [#aws](https://hashnode.com/tag/aws)
-   [#github-actions](https://hashnode.com/tag/github-actions)
-   [#infrastructure-as-code](https://hashnode.com/tag/infrastructure-as-code)
-   [#ci-cd](https://hashnode.com/tag/ci-cd)

## Written by

[Ferhat Yildiz](https://hashnode.com/@turingts)

@turingts · Amstelveen, Netherlands

  
[View profile](https://hashnode.com/@turingts)

Owner at Turing Technology Services

I’m a hands-on technology architect, engineer and founder of Turing Technology Services, with nearly two decades of experience in software engineering, platform engineering, site reliability engineering and cloud infrastructure. My work combines architecture and implementation with technical leadership, coaching and helping organisations adopt new engineering practices. I’ve worked with organisations including Shell, ING, ABN AMRO, Rabobank, Schiphol Group and Ahold Delhaize, across complex and regulated enterprise environments. On this blog, I share practical guides and perspectives on software architecture, cloud platforms, reliability and AI, explaining the reasoning behind technical choices as well as how to implement them.

## Responses 1

Comments are turned off for this post.

[Rishabh Mishra](https://hashnode.com/@rushdeploy)

[Oct 31](https://hashnode.com/posts/deploying-terraform-to-aws-with-github-actions-and-oidc/6ae4f89cd1f5980215892834/comment/6ae55a2cc682f92fba631f50)

The saved-plan rule is the part I would keep. Applying exactly what was reviewed removes a whole class of surprises. I would also keep each plan artifact tied to its run, so a re-run cannot quietly apply a newer change.
