github-app-token VS github-sls-rest-api

It's pretty annoying but basically you have to generate an access token each time... I use this GitHub actions to do it https://github.com/tibdex/github-app-token

Thanks u/numbstruck! Great question... When developing this, I basically was inspired by the Amazon S3 Storage Backend, but with less dependency requiring a DDB table and IAM user/role to do the juggling and let the TFState GitHub API and the GitHub Tokens for Identity/Auth do the heavy lifting instead of Terraform.

Greetings! I've developed a new service called TFstate.dev!

TFstate.dev is a free-to-use hosted HTTP Backend for Terraform State Storage that is accessible using a GitHub Token.

The backend API is Open Source for transparency and confidence that your state files are securely hosted: https://github.com/tfstate/github-sls-rest-api

There's no signup or registration, and with a GitHub token, you can immediately start using this as a Terraform Backend. State is secured and encrypted in Amazon S3 using KMS. State Locking is also natively supported.

Using it is as simple as generating a GitHub token, setting a few lines of config in Terraform, then enjoying the benefits of Shared and Secure state storage without first signing up for TF Cloud or creating S3 buckets, DDB tables and juggling Access Credentials just to get the same feature set.

I'd love to get everyone's feedback, and if you're currently using a different Terraform State backend, feel free to migrate to this service to store your state.

Let me know what you think!

Christian