AWS Github Oidc Scoped Role
Configure GitHub Actions OIDC trust in AWS IAM using audience and exact subject conditions, including custom subjects for reusable workflows, Bedrock inference-profile permissions and explicit Deny guardrails. Use when designing or reviewing AWS roles assumed by GitHub Actions.
Install
npx skills add mizchi/skills --skill aws-github-oidc-scoped-rolegit clone --depth 1 https://github.com/mizchi/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/aws-github-oidc-scoped-role ~/.claude/skills/aws-github-oidc-scoped-rolePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# AWS GitHub Actions OIDC — Scoped IAM Role
## OIDC Provider Setup
```hcl
data "tls_certificate" "github_oidc" {
url = "https://token.actions.githubusercontent.com"
}
resource "aws_iam_openid_connect_provider" "github" {
url = "https://token.actions.githubusercontent.com"
client_id_list = ["sts.amazonaws.com"]
thumbprint_list = [data.tls_certificate.github_oidc.certificates[0].sha1_fingerprint]
}
```
One provider per AWS account. If it already exists, use a `data` source instead.
## Scope trust through `aud` and `sub`
AWS IAM does not expose GitHub's custom JWT claims as arbitrary condition keys.
Use `token.actions.githubusercontent.com:aud` and an exact
`token.actions.githubusercontent.com:sub`; a direct `:job_workflow_ref` condition
is not a supported way to scope AWS trust. Checked against the
[GitHub AWS guide](https://docs.github.com/en/actions/how-tos/secure-your-work/security-harden-deployments/oidc-in-aws)
on 2026-11-16.
For a repository using the legacy default subject, a branch-bound policy is:
```hcl
condition {
test = "StringEquals"
variable = "token.actions.githubusercontent.com:aud"
values = ["sts.amazonaws.com"]
}
condition {
test = "StringEquals"
variable = "token.actions.githubusercontent.com:sub"
values = ["repo:ORG/REPO:ref:refs/heads/main"]
}
```
The exact subject is repository-specific. New repositories using immutable
subjects include owner/repository IDs. Environment jobs use an environmentDetails
- Skill name
aws-github-oidc-scoped-role- Repository
- mizchi/skills
- Path
aws-github-oidc-scoped-role/SKILL.md- Repo updated
- 18 November 2026
FAQ
What does the AWS Github Oidc Scoped Role skill do?
Configure GitHub Actions OIDC trust in AWS IAM using audience and exact subject conditions, including custom subjects for reusable workflows, Bedrock inference-profile permissions and explicit Deny guardrails. Use when designing or reviewing AWS roles assumed by GitHub Actions.
How do I install the AWS Github Oidc Scoped Role skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add mizchi/skills --skill aws-github-oidc-scoped-role. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is AWS Github Oidc Scoped Role popular?
It lives in mizchi/skills, which has 423 GitHub stars and 6 forks.
Related skills
Actions CI Tuning
423mizchi/skills
Use when auditing or improving GitHub Actions workflows for a project. Covers cache setup (npm/pnpm/yarn), job parallelism, shard-based test splitting, artifact handling pitfalls, and Playwright-specific patterns. Trigger on: slow CI, cache miss, flaky shard jobs, merge-reports failures, or an explicit 'tune CI' request.
AI Index
423mizchi/skills
Method and tooling for measuring how AI-generated a piece of prose reads, in Japanese or English. Two layers — a deterministic lint for removable surface tells (scripts/slopscore.py, no API) and a judgment layer of typed probabilistic questions (Jev noul/score) for the tells that survive editing. Includes measured human/AI baselines, a gap-first calibration procedure, and labeled fixtures. Use when building or calibrating an AI-likeness score, or when a draft needs a defensible number rather than a vibe. For writing guidance use natural-writing-ja / natural-writing-en instead.
Apm Usage
423mizchi/skills
Reference for APM manifests, installation, targeted updates, deployment paths and lockfiles. Invoke when the user explicitly asks about APM or apm.yml, or an unfamiliar APM command/error needs exact CLI details. Do not automatically invoke for every project that happens to have installed skills.
AWS Vault Mfa Iam
423mizchi/skills
Use when AWS account の IAM API が MFA 必須 policy で弾かれて、 `sts:GetCallerIdentity` は通るのに `iam:*` が `InvalidClientTokenId` で拒否されるとき、 または FIDO2 passkey で MFA が CLI から使えないとき。 aws-vault / aws-cli / MFA / passkey 関連で「アクセス拒否」 「token expired」 「IAM 操作のみ失敗」 等の症状から起動 (user が aws-vault を名指しでなくても OK)。
AWS Ecs Service Connect Ipv6
423mizchi/skills
Use when ECS Service Connect の DNS alias が IPv6 アドレスを返し、 IPv4-only の Fargate task から `network is unreachable` / `EAI_AGAIN` 等で接続できない問題に遭遇したとき。 OTel Collector → Tempo の OTLP gRPC、 Fargate → Service Connect の HTTP/gRPC 通信が突然失敗する症状が典型。 ECS / Fargate / Service Connect / OTLP / IPv6 dual-stack 関連の接続障害から起動して良い (user が原因を IPv6 と特定していなくても OK)。
Cloudflare Access App Setup
423mizchi/skills
One-shot Cloudflare Access self-hosted application provisioning via the API — app + email allowlist policy + service token. Use when you want to gate a Worker behind Access without a full Pulumi stack.
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.