We are committed to providing learning resources that are accessible to all. If you see a resource that is not compliant, please let us know by creating an issue.
After you have a scratch AWS account setup and connected with AWS CLI, the first step to getting started with Terraform is to use the AWS module to create an S3 bucket.
Once this bucket is created, we can create a DynamoDB table and use this DynamoDB table instance to 'lock state' to prevent state corruption.
We will use a 'partial configuration' instead of specifying the same configuration over and over again in Terraform files, which lets us 'keep things DRY' -- "Don't Repeat Yourself".
A DevContainer allows you to standardize your development environment using Colima. To use the provided DevContainer:
- Ensure you have Colima installed on your machine.
- Install Visual Studio Code and the Dev Containers extension.
- Open this project in VS Code.
- When prompted, reopen the project in the DevContainer. Alternatively, press
F1, search for "Dev Containers: Reopen in Container," and select it. - Once the container is built and running, you can start working with all the required tools pre-installed.
This setup ensures consistency across development environments and simplifies onboarding for new contributors.
This guide sets up SSH key-based Git commit signing (not just repository authentication) using Git and GitHub.
ssh-keygen -t ed25519 -C "your_email@example.com"This creates:
~/.ssh/id_ed25519 (private key)
~/.ssh/id_ed25519.pub (public key)
git config --global gpg.format ssh
git config --global user.signingkey ~/.ssh/id_ed25519.pub
git config --global commit.gpgsign trueCheck your Git email:
git config --global user.email
Make sure that email is added and verified in GitHub.
cat ~/.ssh/id_ed25519.pub`Go to: GitHub → Settings → SSH and GPG Keys
Click "New SSH Key"
Select "Signing key" as the key type
Paste your key and save
git commit -S -m "Your signed commit message"
git pushYou should now see ✅ Verified next to your commits on GitHub.