GitHub Actions — Complete Guide
GitHub Actions — Complete Guide: free step-by-step lesson with examples, common mistakes, and interview tips — part of AWS Cloud Tutorial on Toolliyo Academy.
On this page
AWS Cloud Tutorial · Lesson 48 of 100
GitHub Actions
Core services → Projects
Core services · 1 — AWS basics · ~6 min · AWS — DevOps & Automation
What is this?
GitHub Actions runs CI/CD workflows on GitHub events. AWS integrates via OIDC federation so workflows assume IAM roles without long-lived keys.
Why should you care?
AwsVerse open-source SDK repos deploy docs to S3 using short-lived OIDC credentials.
See it live — copy this example
Run in AWS CloudShell / local AWS CLI v2, or follow the matching steps in the AWS Console (Free Tier).
- name: Configure AWS credentials
uses: aws-actions/configure-aws-credentials@v4
with:
role-to-assume: arn:aws:iam::123456789012:role/github-awsverse-deploy
aws-region: ap-south-1
- name: Sync docs
run: aws s3 sync ./dist s3://awsverse-docs-site/ --deleteWhat happened?
- Workflow assumes IAM role via OIDC trust on GitHub repo.
- s3 sync publishes static docs without storing AWS keys in GitHub secrets.
Practice next
- Create IAM OIDC provider for token.actions.githubusercontent.com.
- Trust policy limited to your repo branch.
- Add workflow on push to main.
- Add environment protection on prod deploy job.
- Matrix build across node 18 and 20.
Remember
OIDC = keyless GitHub to AWS. Scope role to one repo/ref. Use official configure-aws-credentials action.
AwsVerse docs deploy
Every merge to main updates developer portal.
Outcome: GitHub Action syncs to CloudFront origin bucket in 90 seconds.
Interview prep for this lesson
Practice these questions aloud after reading—each links to a full structured answer.
Sign in to ask a question or upvote helpful answers.
No questions yet — be the first to ask!
