[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ABC24YB0C6DAEJ11V0QDMK":3,"skill-same:01M7ABC24YB0C6DAEJ11V0QDMK":146},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M7ABC24YB0C6DAEJ11V0QDMK","rolesanywhere-trust-deployer",null,"Provisions IAM Roles Anywhere trust infrastructure with production defaults: trust anchor creation (binding an external certificate authority to AWS IAM), profile creation (mapping external certificates to IAM roles via role ARNs and role-passthrough), session policy attachment, credential helper configuration (AWS signing helper for certificate-based authentication), external CA (PKI) integration, role assumption workflow (exchange X.509 certificate for STS temporary credentials), session duration, managed-policy vs inline-policy selection, temporary credentials (access key \u002F secret \u002F session token), CloudTrail audit (AssumeRoot events), and revocation configuration (CRL\u002FOCSP). Emits a READY_TO_DEPLOY checklist with verification commands. Use when creating a Roles Anywhere trust. Triggers: create roles anywhere trust anchor, iam roles anywhere profile, credential helper, certificate based authentication aws, external ca aws, exchange cert for sts, roles anywhere session policy, roles anywhere revocation.","jhkchan\u002Faws-agent-skills","jhkchan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1083902?v=4","01M7A2SVQYP9GQTPTDXP5JKYQ4","Jacky Chan","01M7A2SVS117YWCTZABB75HZR1",4,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frolesanywhere-trust-deployer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: rolesanywhere-trust-deployer\ndescription: 'Provisions IAM Roles Anywhere trust infrastructure with production defaults: trust anchor creation (binding an external certificate authority to AWS IAM), profile creation (mapping external certificates to IAM roles via role ARNs and role-passthrough), session policy attachment, credential helper configuration (AWS signing helper for certificate-based authentication), external CA (PKI) integration, role assumption workflow (exchange X.509 certificate for STS temporary credentials), session duration, managed-policy vs inline-policy selection, temporary credentials (access key \u002F secret \u002F session token), CloudTrail audit (AssumeRoot events), and revocation configuration (CRL\u002FOCSP). Emits a READY_TO_DEPLOY checklist with verification commands. Use when creating a Roles Anywhere trust. Triggers: create roles anywhere trust anchor, iam roles anywhere profile, credential helper, certificate based authentication aws, external ca aws, exchange cert for sts, roles anywhere session policy, roles anywhere revocation.'\nlicense: Apache-2.0\ncompatibility: 'Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS CLI v2 with iam, rolesanywhere, sts, cloudwatch, and cloudtrail access, plus the aws_signing_helper binary (downloaded from AWS) on the client machine. Works with Terraform aws_rolesanywhere_trust_anchor, aws_rolesanywhere_profile, and aws_rolesanywhere_crl resources and CloudFormation AWS::RolesAnywhere::TrustAnchor \u002F AWS::RolesAnywhere::Profile templates.'\nmetadata:\n  domain: aws-cloudops\n  complexity: high\n  requires_llm: 'true'\n  phase: '1'\n  supports_pipeline: 'true'\n  entry_point: 'false'\n  family: Security\n  task_type: deploy\n  skill_class: capability\n  lifecycle_status: active\n  verdict_shape: READY_TO_DEPLOY | PREREQUISITES_MISSING\n  version: 0.1.0\n  author: Jacky Chan — AWS Community Builder\n  tags: aws, iam, roles-anywhere, trust-anchor, certificate-authority, pki, credential-helper, cloudops, deploy, security, session-policy, revocation\n  dependencies: aws-orchestrator\n  keywords: aws, iam, roles anywhere, trust anchor, certificate authority, pki, x.509, credential helper, signing helper, sts, temporary credentials, session policy, cloudops, deploy, security, revocation, crl, assume root\n  when_to_use: Invoke when the user wants to create an IAM Roles Anywhere trust anchor (binding an external certificate authority to AWS IAM), create a profile (mapping external certificates to IAM roles), configure the credential helper (AWS signing helper), set up certificate-based authentication to AWS APIs, integrate an external PKI with AWS, configure revocation (CRL\u002FOCSP), or understand the role assumption workflow (exchange X.509 cert for STS credentials). Do NOT invoke for standard IAM role assumption via STS (no certificate), AWS IAM Identity Center (SSO), or AWS Organizations SCC (service control policies).\n---\n\n# Roles Anywhere Trust Deployer\n\nAn AWS CloudOps agent skill that provisions IAM Roles Anywhere trust\ninfrastructure with correct defaults. The skill walks the operator\nthrough trust anchor creation (binding an external CA to AWS IAM),\nprofile creation (mapping external certificates to IAM roles), session\npolicy configuration, credential helper setup (AWS signing helper for\ncertificate-based authentication), role assumption workflow (exchanging\nan X.509 certificate for STS temporary credentials), revocation\nconfiguration (CRL\u002FOCSP), and CloudTrail audit (AssumeRoot events). The\nskill captures PKI and trust decisions, explains why each default\nmatters, and emits a READY_TO_DEPLOY checklist with copy-pasteable\nverification commands.\n\n## Activation keywords\n\ncreate Roles Anywhere trust anchor, IAM Roles Anywhere profile,\ncredential helper, certificate-based authentication AWS, external CA\nAWS, exchange cert for STS, Roles Anywhere session policy, Roles\nAnywhere revocation.\n\n## STRICT output contract\n\nWhen this skill is invoked with a Roles-Anywhere-provisioning request\n(create a trust anchor, create a profile, configure the credential\nhelper, set up cert-based authentication, integrate an external PKI,\nor configure revocation), the agent MUST respond with the\nREADY_TO_DEPLOY checklist defined in the \"Output format\" section using\nthe literal all-caps labels `ROLES_ANYWHERE:`, `VERDICT:`, `CHECKLIST:`,\nand `VERIFICATION_COMMANDS:`. Do NOT preface the checklist with prose,\nheadings, or disclaimers — emit the block as the first lines of the\nresponse. This contract is what assertion-based evals and downstream\nprovisioning pipelines rely on; deviating from the literal labels\nbreaks automation silently.\n\nIf any prerequisite is missing, the verdict is `PREREQUISITES_MISSING`\nwith a specific gap citation in the checklist (marked `[✗]`), and\n`READY_TO_DEPLOY` MUST NOT also appear.\n\n## Quick navigation\n\n| Section | When to read |\n|---|---|\n| Prerequisites | Always — verify before provisioning |\n| Step 1 — Trust anchor (bind external CA to AWS IAM) | Core trust model |\n| Step 2 — Profile (map external cert to IAM role) | Role mapping |\n| Step 3 — IAM role (trust policy for Roles Anywhere) | Permissions |\n| Step 4 — Session policy | Session scoping |\n| Step 5 — Credential helper (AWS signing helper) | Client-side auth |\n| Step 6 — Role assumption workflow (exchange cert for STS) | End-to-end flow |\n| Step 7 — Revocation configuration (CRL\u002FOCSP) | Trust lifecycle |\n| Step 8 — CloudTrail audit (AssumeRoot) | Compliance |\n| Step 9 — Recent features | Latest |\n| NEVER do these things | Review before signing off |\n| Output format | The literal checklist template |\n| references\u002Ftrust-anchor-and-profile.md | Trust anchor + profile detail |\n| references\u002Fcredential-helper-and-revocation.md | Helper + revocation detail |\n\n## Mindset\n\n**One-line takeaway:** IAM Roles Anywhere lets external workloads\n(on-prem servers, CI runners, edge devices) assume IAM roles using\nX.509 certificates from your own PKI instead of long-lived AWS access\nkeys. The trust anchor binds your external CA to AWS IAM; the profile\nmaps external certificates to IAM roles; the credential helper signs\nAWS API requests with the certificate and obtains STS temporary\ncredentials. Without the trust anchor, AWS does not trust your CA.\nWithout the profile, AWS does not know which role to assume. Without\nthe credential helper, the workload cannot sign requests.\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#common-misconceptions-from-mindset).\n> Three trust-model misconceptions: anchor-alone access, any-cert-any-role, automatic revocation.\n\n## Configuration dependency graph (novel heuristic)\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#configuration-dependency-graph-sequencing-notes).\n> Sequencing table, the IAM trust-policy trap, and cross-dependency gotchas.\n\n## Expert heuristic: the three-legged trust stool\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#expert-heuristic-the-three-legged-trust-stool).\n> Trust anchor + profile + IAM role trust policy; missing any one fails opaquely.\n\n## Expert heuristic: the credential helper signs requests with the certificate\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#expert-heuristic-the-credential-helper-signs-requests-with-the-certificate).\n> credential-process workflow: sign the AssumeRole request with the cert private key, receive STS credentials.\n\n## Expert heuristic: session policies restrict, never expand\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#expert-heuristic-session-policies-restrict-never-expand).\n> Effective permissions = role ∩ session policy; use to scope a shared role per profile.\n\n## Prerequisites (verify before provisioning)\n\nBefore emitting provisioning commands, verify these prerequisites. If\nany are missing, the verdict is **PREREQUISITES_MISSING**.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| External CA exists with X.509 signing capability | Trust anchor binds the CA cert to AWS IAM | Verify CA cert in PEM format: `openssl x509 -in ca-cert.pem -text -noout` |\n| Client certificate and private key generated | Credential helper needs both to sign requests | `openssl x509 -in client-cert.pem -text -noout` |\n| IAM role exists with Roles Anywhere trust policy | Role must be assumable by `rolesanywhere.amazonaws.com` | `aws iam get-role --role-name \u003Cname>` and check trust policy |\n| IAM role has appropriate permissions | Temporary credentials scope comes from the role | `aws iam list-attached-role-policies` and `aws iam list-role-policies` |\n| Region supports Roles Anywhere | Available in most regions but verify | `aws rolesanywhere list-trust-anchors --region \u003Cregion>` |\n| aws_signing_helper downloaded (for client-side testing) | Client needs the helper to exchange cert for STS | Check binary on the client machine |\n| CloudTrail logging enabled (for audit) | AssumeRoot events need CloudTrail to be recorded | `aws cloudtrail describe-trails` |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING`\nand cite the specific gap.\n\n## Step 1 — Trust anchor (bind external CA to AWS IAM)\n\nA trust anchor binds an external certificate authority (CA) to AWS IAM.\nIt tells AWS \"trust X.509 certificates signed by this CA.\"\n\n| Trust anchor field | Purpose | Required |\n|---|---|---|\n| `name` | Human-readable name | Yes |\n| `source.sourceType` | Type of CA source (`CERTIFICATE_BUNDLE` for self-managed CA, `AWS_ACM_PCA` for AWS Private CA) | Yes |\n| `source.sourceData.acmPcaArn` | ACM PCA ARN (if sourceType is `AWS_ACM_PCA`) | If using ACM PCA |\n| `source.sourceData.x509CertificateData` | PEM-encoded CA certificate (if sourceType is `CERTIFICATE_BUNDLE`) | If using self-managed CA |\n| `enabled` | Enable or disable the trust anchor | Yes (default: true) |\n| `notificationSettings` | Notify on cert expiry, etc. | Optional |\n\n**Create a trust anchor from a self-managed CA (CERTIFICATE_BUNDLE):**\n\n```bash\nCA_CERT=$(cat ca-cert.pem)\n\nTRUST_ANCHOR_ID=$(aws rolesanywhere create-trust-anchor \\\n  --name \"my-pki-trust-anchor\" \\\n  --source \"sourceType=CERTIFICATE_BUNDLE,sourceData={x509CertificateData=$CA_CERT}\" \\\n  --enabled \\\n  --region us-east-1 \\\n  --query 'trustAnchor.trustAnchorId' --output text)\n\necho \"Trust anchor: $TRUST_ANCHOR_ID\"\n```\n\n**Create a trust anchor from AWS Private CA (AWS_ACM_PCA):**\n\n```bash\nTRUST_ANCHOR_ID=$(aws rolesanywhere create-trust-anchor \\\n  --name \"acm-pca-trust-anchor\" \\\n  --source \"sourceType=AWS_ACM_PCA,sourceData={acmPcaArn=arn:aws:acm-pca:us-east-1:123456789012:certificate-authority\u002F12345678-1234-1234-1234-123456789012}\" \\\n  --enabled \\\n  --region us-east-1 \\\n  --query 'trustAnchor.trustAnchorId' --output text)\n```\n\n**Critical:** the trust anchor is immutable once created. To rotate\nthe CA, create a new trust anchor and update the profile to reference\nit.\n\n## Step 2 — Profile (map external cert to IAM role)\n\nA profile maps an external certificate (validated via the trust anchor)\nto one or more IAM roles.\n\n| Profile field | Purpose | Required |\n|---|---|---|\n| `name` | Human-readable name | Yes |\n| `trustAnchorId` | The trust anchor that validates the cert | Yes |\n| `roleArns` | List of IAM role ARNs the cert can assume | Yes (unless using role-passthrough) |\n| `durationSeconds` | Session duration (900-43200 seconds) | Yes (default: 3600) |\n| `enabled` | Enable or disable the profile | Yes (default: true) |\n| `sessionPolicy` | Inline session policy (further restricts permissions) | Optional |\n| `managedPolicyArns` | Managed policy ARNs to apply as session policies | Optional |\n\n**Create a profile:**\n\n```bash\nPROFILE_ID=$(aws rolesanywhere create-profile \\\n  --name \"ci-runner-profile\" \\\n  --trust-anchor-id \"$TRUST_ANCHOR_ID\" \\\n  --role-arns \"arn:aws:iam::123456789012:role\u002FRolesAnywhereCIRunner\" \\\n  --duration-seconds 3600 \\\n  --enabled \\\n  --region us-east-1 \\\n  --query 'profile.profileId' --output text)\n\necho \"Profile: $PROFILE_ID\"\n```\n\n**Role-passthrough mode:** if `roleArns` is omitted, the profile uses\nrole-passthrough mode, where the client specifies the role ARN at\nassume time. This is more flexible but less controlled. Use only when\nthe client should dynamically choose the role.\n\n**Critical:** the `roleArns` list determines which roles the\ncertificate can assume. Listing too many roles violates least\nprivilege. List only the role(s) this specific workload needs.\n\n## Step 3 — IAM role (trust policy for Roles Anywhere)\n\nThe IAM role must have a trust policy that allows Roles Anywhere to\nassume it. This is the #1 forgotten step.\n\n**Trust policy for Roles Anywhere:**\n\n```json\n{\n  \"Version\": \"2012-10-17\",\n  \"Statement\": [\n    {\n      \"Effect\": \"Allow\",\n      \"Principal\": {\n        \"Service\": \"rolesanywhere.amazonaws.com\"\n      },\n      \"Action\": \"sts:AssumeRole\",\n      \"Condition\": {\n        \"StringEquals\": {\n          \"aws:SourceProfileArn\": \"arn:aws:rolesanywhere:us-east-1:123456789012:profile\u002F\u003Cprofile-id>\"\n        }\n      }\n    }\n  ]\n}\n```\n\n**Create the IAM role:**\n\n```bash\naws iam create-role \\\n  --role-name RolesAnywhereCIRunner \\\n  --assume-role-policy-document file:\u002F\u002Ftrust-policy.json \\\n  --region us-east-1\n\naws iam attach-role-policy \\\n  --role-name RolesAnywhereCIRunner \\\n  --policy-arn arn:aws:iam::aws:policy\u002FAmazonS3ReadOnlyAccess\n```\n\n**Critical:** without the trust policy allowing\n`rolesanywhere.amazonaws.com`, the role CANNOT be assumed via Roles\nAnywhere. The credential helper returns `AccessDenied`.\n\n## Step 4 — Session policy\n\nA session policy is an optional inline or managed policy attached to\nthe profile. It further restricts the IAM role's permissions for\nsessions assumed via that profile.\n\n**Inline session policy (restrict to a specific S3 bucket):**\n\n```bash\naws rolesanywhere update-profile \\\n  --profile-id \"$PROFILE_ID\" \\\n  --session-policy file:\u002F\u002Fsession-policy.json \\\n  --region us-east-1\n```\n\n```json\n{\n  \"Version\": \"2012-10-17\",\n  \"Statement\": [\n    {\n      \"Effect\": \"Allow\",\n      \"Action\": [\"s3:GetObject\"],\n      \"Resource\": \"arn:aws:s3:::my-ci-artifacts\u002F*\"\n    }\n  ]\n}\n```\n\n**Critical:** session policies RESTRICT permissions; they never expand\nthem. Effective permissions = IAM role permissions intersected with\nthe session policy.\n\n## Step 5 — Credential helper (AWS signing helper)\n\nThe AWS signing helper (`aws_signing_helper`) is a client-side binary\nthat exchanges an X.509 certificate for STS temporary credentials.\n\n> Moved to [references\u002Fcredential-helper-and-revocation.md](references\u002Fcredential-helper-and-revocation.md#signing-helper-download-and-aws-cli-integration-from-skillmd).\n> Where to download aws_signing_helper per platform.\n\n**Exchange certificate for temporary credentials:**\n\n```bash\n.\u002Faws_signing_helper credential-process \\\n  --certificate client-cert.pem \\\n  --private-key client-key.pem \\\n  --trust-anchor-id \"$TRUST_ANCHOR_ID\" \\\n  --profile-id \"$PROFILE_ID\" \\\n  --role-arn arn:aws:iam::123456789012:role\u002FRolesAnywhereCIRunner \\\n  --region us-east-1\n```\n\nThis outputs JSON with `AccessKeyId`, `SecretAccessKey`, and\n`SessionToken`. The client can then use these credentials to call AWS\nAPIs.\n\n**Configure the AWS CLI to use the credential helper:**\n\n> Moved to [references\u002Fcredential-helper-and-revocation.md](references\u002Fcredential-helper-and-revocation.md#signing-helper-download-and-aws-cli-integration-from-skillmd).\n> AWS CLI credential_process profile block wired to the signing helper.\n\n**Critical:** the credential helper must run on the client machine. It\nis not an AWS service. Without it, the workload cannot sign requests.\n\n## Step 6 — Role assumption workflow (exchange cert for STS)\n\nEnd-to-end flow: the client generates a key pair and obtains a\ncertificate from the external CA, then runs `aws_signing_helper\ncredential-process` with `--certificate`, `--private-key`,\n`--trust-anchor-id`, `--profile-id`, and `--role-arn`. The signing\nhelper sends the request to the Roles Anywhere endpoint, which\nvalidates the certificate chain (signed by the trust anchor's CA, not\nexpired, not revoked if CRL is configured, profile maps the cert to the\nrequested role, IAM role's trust policy allows Roles Anywhere), then\nreturns STS temporary credentials. The client uses these credentials to\ncall AWS APIs; they expire after the session duration (default: 1 hour),\nand the credential helper re-runs to refresh.\n\n**Verify the temporary credentials work:**\n\n> Moved to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md#verify-the-temporary-credentials-work-step-6).\n> Use the assumed credentials: AWS_PROFILE=rolesanywhere aws s3 ls \u002F sts get-caller-identity.\n\n## Step 7 — Revocation configuration (CRL\u002FOCSP)\n\nBy default, a certificate remains valid until its expiration date. To\nrevoke a certificate before expiration, configure a Certificate\nRevocation List (CRL).\n\n**Create a CRL:**\n\n```bash\naws rolesanywhere enable-crl \\\n  --crl-name \"my-pki-crl\" \\\n  --crl-data \"$(base64 crl.pem)\" \\\n  --trust-anchor-arn \"arn:aws:rolesanywhere:us-east-1:123456789012:trust-anchor\u002F$TRUST_ANCHOR_ID\" \\\n  --region us-east-1\n```\n\n**Update the CRL when certificates are revoked:**\n\n```bash\n# Regenerate the CRL in your CA after revoking a certificate\nopenssl ca -gencrl -out crl.pem\n\n# Update the CRL in Roles Anywhere\naws rolesanywhere update-crl \\\n  --crl-id \"$CRL_ID\" \\\n  --crl-data \"$(base64 crl.pem)\" \\\n  --region us-east-1\n```\n\n**Critical:** without a CRL, a compromised certificate remains usable\nuntil it expires. Always configure revocation for production PKIs.\n\n## Step 8 — CloudTrail audit (AssumeRoot)\n\nRoles Anywhere sessions are logged in CloudTrail under the `AssumeRoot`\nevent name (source: `rolesanywhere.amazonaws.com`). Key fields include\n`requestParameters.profileArn`, `requestParameters.trustAnchorArn`, and\n`requestParameters.roleArn`.\n\n**Query CloudTrail for Roles Anywhere sessions:**\n\n> Moved to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md#query-cloudtrail-for-roles-anywhere-sessions-step-8).\n> cloudtrail lookup-events for AssumeRoot sessions in the last hour.\n\n## Step 9 — Recent features\n\n**Recent AWS features (2023-2026):**\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#recent-aws-features-2023-2026).\n> GA, ACM PCA anchors, session policies, role-passthrough, CRLs, helper updates, attribution, cross-account anchors.\n  enabling centralized PKI management.\n\n## NEVER do these things\n\n1. **NEVER assume the trust anchor alone grants access.** The trust\n   anchor only binds the CA to AWS IAM. A profile AND an IAM role with\n   the correct trust policy are ALSO required.\n\n2. **NEVER use an IAM role without a Roles Anywhere trust policy.**\n   The role's trust policy must allow `sts:AssumeRole` from\n   `rolesanywhere.amazonaws.com`. Without it, assume fails with\n   `AccessDenied`.\n\n3. **NEVER list too many roles in a profile.** The `roleArns` list\n   determines which roles the cert can assume. List only the role(s)\n   this specific workload needs. Over-permissive profiles violate\n   least privilege.\n\n4. **NEVER skip revocation configuration.** Without a CRL, a\n   compromised certificate remains usable until it expires. Always\n   configure revocation for production PKIs.\n\n5. **NEVER store the CA private key on the client machine.** The CA\n   private key must be securely stored (HSM, KMS, or offline CA). Only\n   the client certificate and its private key should be on the client.\n\n6. **NEVER assume session policies expand permissions.** Session\n   policies RESTRICT permissions; they never expand them. Effective\n   permissions = IAM role permissions intersected with the session\n   policy.\n\n7. **NEVER use long-lived certificates without expiration.** Certificates\n   should have a reasonable expiration (e.g., 90 days for CI runners,\n   1 year for servers). Avoid 10-year certificates.\n\n8. **NEVER forget the credential helper on the client.** The signing\n   helper must be installed on the client; without it, the workload\n   cannot sign requests with the certificate.\n\n9. **NEVER assume role-passthrough is safe without controls.**\n   Role-passthrough mode lets the client specify any role ARN at\n   assume time. Use only when the client is fully trusted, or when\n   the IAM roles' trust policies enforce strict Conditions.\n\n10. **NEVER ignore CloudTrail audit events.** Roles Anywhere sessions\n    are logged as `AssumeRoot` events. Regularly audit which\n    certificates assumed which roles, especially after a certificate\n    is compromised.\n\n## Output format\n\n```text\nROLES_ANYWHERE: \u003Ctrust-anchor-id> → \u003Cprofile-id> → \u003Crole-arn>\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Trust anchor: \u003Ctrust-anchor-id> — \u003Cca-source> (CERTIFICATE_BUNDLE | AWS_ACM_PCA)\n  [✓|✗] Profile: \u003Cprofile-id> — roleArns: \u003Crole-arn list> (duration: \u003Cseconds>s)\n  [✓|✗] IAM role: \u003Crole-arn> (trust: rolesanywhere.amazonaws.com; permissions: \u003Cdescription>)\n  [✓|✗] Session policy: \u003Cinline|managed|none> — \u003Cdescription>\n  [✓|✗] Credential helper: aws_signing_helper (client-side, cert: \u003Ccert-path>)\n  [✓|✗] Revocation: CRL configured (\u003Ccrl-name>) | Not configured\n  [✓|✗] CloudTrail audit: AssumeRoot events logged\n  [✓|✗] CA certificate verified: \u003Cca-cert-path> (PEM, expires \u003Cdate>)\n  [✓|✗] Client certificate verified: \u003Cclient-cert-path> (PEM, expires \u003Cdate>)\n  [✓|✗] Region: \u003Cregion>\n  [✓|✗] Tags: \u003Ckey=value list>\nVERIFICATION_COMMANDS:\n  aws rolesanywhere list-trust-anchors --region \u003Cregion>\n  aws rolesanywhere list-profiles --region \u003Cregion>\n  aws iam get-role --role-name \u003Crole-name>\n  .\u002Faws_signing_helper credential-process --certificate \u003Ccert> --private-key \u003Ckey> --trust-anchor-id \u003Cid> --profile-id \u003Cid> --role-arn \u003Carn> --region \u003Cregion>\n```\n\n### Worked example — CI runner with external PKI\n\n```text\nROLES_ANYWHERE: ta-aaa111222 → p-bbb222333 → arn:aws:iam::123456789012:role\u002FRolesAnywhereCIRunner\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Trust anchor: ta-aaa111222 — self-managed CA (CERTIFICATE_BUNDLE, ca-cert.pem)\n  [✓] Profile: p-bbb222333 — roleArns: arn:aws:iam::123456789012:role\u002FRolesAnywhereCIRunner (duration: 3600s)\n  [✓] IAM role: arn:aws:iam::123456789012:role\u002FRolesAnywhereCIRunner (trust: rolesanywhere.amazonaws.com; permissions: AmazonS3ReadOnlyAccess)\n  [✓] Session policy: inline — restrict to s3:GetObject on my-ci-artifacts\u002F*\n  [✓] Credential helper: aws_signing_helper (client-side, cert: client-cert.pem)\n  [✓] Revocation: CRL configured (my-pki-crl)\n  [✓] CloudTrail audit: AssumeRoot events logged\n  [✓] CA certificate verified: ca-cert.pem (PEM, expires 2027-12-31)\n  [✓] Client certificate verified: client-cert.pem (PEM, expires 2026-11-01)\n  [✓] Region: us-east-1\n  [✓] Tags: Environment=production, Workload=ci-runner\nVERIFICATION_COMMANDS:\n  aws rolesanywhere list-trust-anchors --region us-east-1\n  aws rolesanywhere list-profiles --region us-east-1\n  aws iam get-role --role-name RolesAnywhereCIRunner\n  .\u002Faws_signing_helper credential-process --certificate client-cert.pem --private-key client-key.pem --trust-anchor-id ta-aaa111222 --profile-id p-bbb222333 --role-arn arn:aws:iam::123456789012:role\u002FRolesAnywhereCIRunner --region us-east-1\n```\n\n## Error handling\n\n> Moved to [references\u002Ferror-handling.md](references\u002Ferror-handling.md#error-handling).\n> AccessDenied, cert not trusted, expired\u002Frevoked cert, helper missing, short sessions.\n\n## References (load on demand)\n\n- [advanced-patterns](references\u002Fadvanced-patterns.md) — misconceptions, dependency graph, expert heuristics, recent features\n- [diagnostic-commands](references\u002Fdiagnostic-commands.md) — credential verification and CloudTrail audit queries\n- [error-handling](references\u002Ferror-handling.md) — symptom-by-symptom troubleshooting\n- [trust-anchor-and-profile](references\u002Ftrust-anchor-and-profile.md) — trust anchor + profile detail (existing)\n- [credential-helper-and-revocation](references\u002Fcredential-helper-and-revocation.md) — helper setup, CRL revocation, CLI integration (existing)\n\n## Domain\n\nAWS CloudOps \u002F IAM Roles Anywhere Trust Infrastructure Provisioning &\nCertificate-Based Authentication.\n\n## AWS documentation\n\n- **IAM Roles Anywhere User Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Frolesanywhere\u002Flatest\u002Fuserguide\u002Fintroduction.html\n- **Create trust anchor** — https:\u002F\u002Fdocs.aws.amazon.com\u002Frolesanywhere\u002Flatest\u002Fuserguide\u002Ftrust-anchors.html\n- **Create profile** — https:\u002F\u002Fdocs.aws.amazon.com\u002Frolesanywhere\u002Flatest\u002Fuserguide\u002Fprofiles.html\n- **Credential helper** — https:\u002F\u002Fdocs.aws.amazon.com\u002Frolesanywhere\u002Flatest\u002Fuserguide\u002Fcredential-helper.html\n- **Revocation (CRL)** — https:\u002F\u002Fdocs.aws.amazon.com\u002Frolesanywhere\u002Flatest\u002Fuserguide\u002Frevocation.html\n- **CloudTrail audit** — https:\u002F\u002Fdocs.aws.amazon.com\u002Frolesanywhere\u002Flatest\u002Fuserguide\u002Fsecurity-logging.html\n- **AWS CLI rolesanywhere** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcli\u002Flatest\u002Freference\u002Frolesanywhere\u002F\n- **IAM Roles Anywhere best practices** — https:\u002F\u002Fdocs.aws.amazon.com\u002Frolesanywhere\u002Flatest\u002Fuserguide\u002Fbest-practices.html\n","# Roles Anywhere Trust Deployer\n\nAn AWS CloudOps agent skill that provisions IAM Roles Anywhere trust\ninfrastructure with correct defaults. The skill walks the operator\nthrough trust anchor creation (binding an external CA to AWS IAM),\nprofile creation (mapping external certificates to IAM roles), session\npolicy configuration, credential helper setup (AWS signing helper for\ncertificate-based authentication), role assumption workflow (exchanging\nan X.509 certificate for STS temporary credentials), revocation\nconfiguration (CRL\u002FOCSP), and CloudTrail audit (AssumeRoot events). The\nskill captures PKI and trust decisions, explains why each default\nmatters, and emits a READY_TO_DEPLOY checklist with copy-pasteable\nverification commands.\n\n## Activation keywords\n\ncreate Roles Anywhere trust anchor, IAM Roles Anywhere profile,\ncredential helper, certificate-based authentication AWS, external CA\nAWS, exchange cert for STS, Roles Anywhere session policy, Roles\nAnywhere revocation.\n\n## STRICT output contract\n\nWhen this skill is invoked with a Roles-Anywhere-provisioning request\n(create a trust anchor, create a profile, configure the credential\nhelper, set up cert-based authentication, integrate an external PKI,\nor configure revocation), the agent MUST respond with the\nREADY_TO_DEPLOY checklist defined in the \"Output format\" section using\nthe literal all-caps labels `ROLES_ANYWHERE:`, `VERDICT:`, `CHECKLIST:`,\nand `VERIFICATION_COMMANDS:`. Do NOT preface the checklist with prose,\nheadings, or disclaimers — emit the block as the first lines of the\nresponse. This contract is what assertion-based evals and downstream\nprovisioning pipelines rely on; deviating from the literal labels\nbreaks automation silently.\n\nIf any prerequisite is missing, the verdict is `PREREQUISITES_MISSING`\nwith a specific gap citation in the checklist (marked `[✗]`), and\n`READY_TO_DEPLOY` MUST NOT also appear.\n\n## Quick navigation\n\n| Section | When to read |\n|---|---|\n| Prerequisites | Always — verify before provisioning |\n| Step 1 — Trust anchor (bind external CA to AWS IAM) | Core trust model |\n| Step 2 — Profile (map external cert to IAM role) | Role mapping |\n| Step 3 — IAM role (trust policy for Roles Anywhere) | Permissions |\n| Step 4 — Session policy | Session scoping |\n| Step 5 — Credential helper (AWS signing helper) | Client-side auth |\n| Step 6 — Role assumption workflow (exchange cert for STS) | End-to-end flow |\n| Step 7 — Revocation configuration (CRL\u002FOCSP) | Trust lifecycle |\n| Step 8 — CloudTrail audit (AssumeRoot) | Compliance |\n| Step 9 — Recent features | Latest |\n| NEVER do these things | Review before signing off |\n| Output format | The literal checklist template |\n| references\u002Ftrust-anchor-and-profile.md | Trust anchor + profile detail |\n| references\u002Fcredential-helper-and-revocation.md | Helper + revocation detail |\n\n## Mindset\n\n**One-line takeaway:** IAM Roles Anywhere lets external workloads\n(on-prem servers, CI runners, edge devices) assume IAM roles using\nX.509 certificates from your own PKI instead of long-lived AWS access\nkeys. The trust anchor binds your external CA to AWS IAM; the profile\nmaps external certificates to IAM roles; the credential helper signs\nAWS API requests with the certificate and obtains STS temporary\ncredentials. Without the trust anchor, AWS does not trust your CA.\nWithout the profile, AWS does not know which role to assume. Without\nthe credential helper, the workload cannot sign requests.\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#common-misconceptions-from-mindset).\n> Three trust-model misconceptions: anchor-alone access, any-cert-any-role, automatic revocation.\n\n## Configuration dependency graph (novel heuristic)\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#configuration-dependency-graph-sequencing-notes).\n> Sequencing table, the IAM trust-policy trap, and cross-dependency gotchas.\n\n## Expert heuristic: the three-legged trust stool\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#expert-heuristic-the-three-legged-trust-stool).\n> Trust anchor + profile + IAM role trust policy; missing any one fails opaquely.\n\n## Expert heuristic: the credential helper signs requests with the certificate\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#expert-heuristic-the-credential-helper-signs-requests-with-the-certificate).\n> credential-process workflow: sign the AssumeRole request with the cert private key, receive STS credentials.\n\n## Expert heuristic: session policies restrict, never expand\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#expert-heuristic-session-policies-restrict-never-expand).\n> Effective permissions = role ∩ session policy; use to scope a shared role per profile.\n\n## Prerequisites (verify before provisioning)\n\nBefore emitting provisioning commands, verify these prerequisites. If\nany are missing, the verdict is **PREREQUISITES_MISSING**.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| External CA exists with X.509 signing capability | Trust anchor binds the CA cert to AWS IAM | Verify CA cert in PEM format: `openssl x509 -in ca-cert.pem -text -noout` |\n| Client certificate and private key generated | Credential helper needs both to sign requests | `openssl x509 -in client-cert.pem -text -noout` |\n| IAM role exists with Roles Anywhere trust policy | Role must be assumable by `rolesanywhere.amazonaws.com` | `aws iam get-role --role-name \u003Cname>` and check trust policy |\n| IAM role has appropriate permissions | Temporary credentials scope comes from the role | `aws iam list-attached-role-policies` and `aws iam list-role-policies` |\n| Region supports Roles Anywhere | Available in most regions but verify | `aws rolesanywhere list-trust-anchors --region \u003Cregion>` |\n| aws_signing_helper downloaded (for client-side testing) | Client needs the helper to exchange cert for STS | Check binary on the client machine |\n| CloudTrail logging enabled (for audit) | AssumeRoot events need CloudTrail to be recorded | `aws cloudtrail describe-trails` |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING`\nand cite the specific gap.\n\n## Step 1 — Trust anchor (bind external CA to AWS IAM)\n\nA trust anchor binds an external certificate authority (CA) to AWS IAM.\nIt tells AWS \"trust X.509 certificates signed by this CA.\"\n\n| Trust anchor field | Purpose | Required |\n|---|---|---|\n| `name` | Human-readable name | Yes |\n| `source.sourceType` | Type of CA source (`CERTIFICATE_BUNDLE` for self-managed CA, `AWS_ACM_PCA` for AWS Private CA) | Yes |\n| `source.sourceData.acmPcaArn` | ACM PCA ARN (if sourceType is `AWS_ACM_PCA`) | If using ACM PCA |\n| `source.sourceData.x509CertificateData` | PEM-encoded CA certificate (if sourceType is `CERTIFICATE_BUNDLE`) | If using self-managed CA |\n| `enabled` | Enable or disable the trust anchor | Yes (default: true) |\n| `notificationSettings` | Notify on cert expiry, etc. | Optional |\n\n**Create a trust anchor from a self-managed CA (CERTIFICATE_BUNDLE):**\n\n```bash\nCA_CERT=$(cat ca-cert.pem)\n\nTRUST_ANCHOR_ID=$(aws rolesanywhere create-trust-anchor \\\n  --name \"my-pki-trust-anchor\" \\\n  --source \"sourceType=CERTIFICATE_BUNDLE,sourceData={x509CertificateData=$CA_CERT}\" \\\n  --enabled \\\n  --region us-east-1 \\\n  --query 'trustAnchor.trustAnchorId' --output text)\n\necho \"Trust anchor: $TRUST_ANCHOR_ID\"\n```\n\n**Create a trust anchor from AWS Private CA (AWS_ACM_PCA):**\n\n```bash\nTRUST_ANCHOR_ID=$(aws rolesanywhere create-trust-anchor \\\n  --name \"acm-pca-trust-anchor\" \\\n  --source \"sourceType=AWS_ACM_PCA,sourceData={acmPcaArn=arn:aws:acm-pca:us-east-1:123456789012:certificate-authority\u002F12345678-1234-1234-1234-123456789012}\" \\\n  --enabled \\\n  --region us-east-1 \\\n  --query 'trustAnchor.trustAnchorId' --output text)\n```\n\n**Critical:** the trust anchor is immutable once created. To rotate\nthe CA, create a new trust anchor and update the profile to reference\nit.\n\n## Step 2 — Profile (map external cert to IAM role)\n\nA profile maps an external certificate (validated via the trust anchor)\nto one or more IAM roles.\n\n| Profile field | Purpose | Required |\n|---|---|---|\n| `name` | Human-readable name | Yes |\n| `trustAnchorId` | The trust anchor that validates the cert | Yes |\n| `roleArns` | List of IAM role ARNs the cert can assume | Yes (unless using role-passthrough) |\n| `durationSeconds` | Session duration (900-43200 seconds) | Yes (default: 3600) |\n| `enabled` | Enable or disable the profile | Yes (default: true) |\n| `sessionPolicy` | Inline session policy (further restricts permissions) | Optional |\n| `managedPolicyArns` | Managed policy ARNs to apply as session policies | Optional |\n\n**Create a profile:**\n\n```bash\nPROFILE_ID=$(aws rolesanywhere create-profile \\\n  --name \"ci-runner-profile\" \\\n  --trust-anchor-id \"$TRUST_ANCHOR_ID\" \\\n  --role-arns \"arn:aws:iam::123456789012:role\u002FRolesAnywhereCIRunner\" \\\n  --duration-seconds 3600 \\\n  --enabled \\\n  --region us-east-1 \\\n  --query 'profile.profileId' --output text)\n\necho \"Profile: $PROFILE_ID\"\n```\n\n**Role-passthrough mode:** if `roleArns` is omitted, the profile uses\nrole-passthrough mode, where the client specifies the role ARN at\nassume time. This is more flexible but less controlled. Use only when\nthe client should dynamically choose the role.\n\n**Critical:** the `roleArns` list determines which roles the\ncertificate can assume. Listing too many roles violates least\nprivilege. List only the role(s) this specific workload needs.\n\n## Step 3 — IAM role (trust policy for Roles Anywhere)\n\nThe IAM role must have a trust policy that allows Roles Anywhere to\nassume it. This is the #1 forgotten step.\n\n**Trust policy for Roles Anywhere:**\n\n```json\n{\n  \"Version\": \"2012-10-17\",\n  \"Statement\": [\n    {\n      \"Effect\": \"Allow\",\n      \"Principal\": {\n        \"Service\": \"rolesanywhere.amazonaws.com\"\n      },\n      \"Action\": \"sts:AssumeRole\",\n      \"Condition\": {\n        \"StringEquals\": {\n          \"aws:SourceProfileArn\": \"arn:aws:rolesanywhere:us-east-1:123456789012:profile\u002F\u003Cprofile-id>\"\n        }\n      }\n    }\n  ]\n}\n```\n\n**Create the IAM role:**\n\n```bash\naws iam create-role \\\n  --role-name RolesAnywhereCIRunner \\\n  --assume-role-policy-document file:\u002F\u002Ftrust-policy.json \\\n  --region us-east-1\n\naws iam attach-role-policy \\\n  --role-name RolesAnywhereCIRunner \\\n  --policy-arn arn:aws:iam::aws:policy\u002FAmazonS3ReadOnlyAccess\n```\n\n**Critical:** without the trust policy allowing\n`rolesanywhere.amazonaws.com`, the role CANNOT be assumed via Roles\nAnywhere. The credential helper returns `AccessDenied`.\n\n## Step 4 — Session policy\n\nA session policy is an optional inline or managed policy attached to\nthe profile. It further restricts the IAM role's permissions for\nsessions assumed via that profile.\n\n**Inline session policy (restrict to a specific S3 bucket):**\n\n```bash\naws rolesanywhere update-profile \\\n  --profile-id \"$PROFILE_ID\" \\\n  --session-policy file:\u002F\u002Fsession-policy.json \\\n  --region us-east-1\n```\n\n```json\n{\n  \"Version\": \"2012-10-17\",\n  \"Statement\": [\n    {\n      \"Effect\": \"Allow\",\n      \"Action\": [\"s3:GetObject\"],\n      \"Resource\": \"arn:aws:s3:::my-ci-artifacts\u002F*\"\n    }\n  ]\n}\n```\n\n**Critical:** session policies RESTRICT permissions; they never expand\nthem. Effective permissions = IAM role permissions intersected with\nthe session policy.\n\n## Step 5 — Credential helper (AWS signing helper)\n\nThe AWS signing helper (`aws_signing_helper`) is a client-side binary\nthat exchanges an X.509 certificate for STS temporary credentials.\n\n> Moved to [references\u002Fcredential-helper-and-revocation.md](references\u002Fcredential-helper-and-revocation.md#signing-helper-download-and-aws-cli-integration-from-skillmd).\n> Where to download aws_signing_helper per platform.\n\n**Exchange certificate for temporary credentials:**\n\n```bash\n.\u002Faws_signing_helper credential-process \\\n  --certificate client-cert.pem \\\n  --private-key client-key.pem \\\n  --trust-anchor-id \"$TRUST_ANCHOR_ID\" \\\n  --profile-id \"$PROFILE_ID\" \\\n  --role-arn arn:aws:iam::123456789012:role\u002FRolesAnywhereCIRunner \\\n  --region us-east-1\n```\n\nThis outputs JSON with `AccessKeyId`, `SecretAccessKey`, and\n`SessionToken`. The client can then use these credentials to call AWS\nAPIs.\n\n**Configure the AWS CLI to use the credential helper:**\n\n> Moved to [references\u002Fcredential-helper-and-revocation.md](references\u002Fcredential-helper-and-revocation.md#signing-helper-download-and-aws-cli-integration-from-skillmd).\n> AWS CLI credential_process profile block wired to the signing helper.\n\n**Critical:** the credential helper must run on the client machine. It\nis not an AWS service. Without it, the workload cannot sign requests.\n\n## Step 6 — Role assumption workflow (exchange cert for STS)\n\nEnd-to-end flow: the client generates a key pair and obtains a\ncertificate from the external CA, then runs `aws_signing_helper\ncredential-process` with `--certificate`, `--private-key`,\n`--trust-anchor-id`, `--profile-id`, and `--role-arn`. The signing\nhelper sends the request to the Roles Anywhere endpoint, which\nvalidates the certificate chain (signed by the trust anchor's CA, not\nexpired, not revoked if CRL is configured, profile maps the cert to the\nrequested role, IAM role's trust policy allows Roles Anywhere), then\nreturns STS temporary credentials. The client uses these credentials to\ncall AWS APIs; they expire after the session duration (default: 1 hour),\nand the credential helper re-runs to refresh.\n\n**Verify the temporary credentials work:**\n\n> Moved to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md#verify-the-temporary-credentials-work-step-6).\n> Use the assumed credentials: AWS_PROFILE=rolesanywhere aws s3 ls \u002F sts get-caller-identity.\n\n## Step 7 — Revocation configuration (CRL\u002FOCSP)\n\nBy default, a certificate remains valid until its expiration date. To\nrevoke a certificate before expiration, configure a Certificate\nRevocation List (CRL).\n\n**Create a CRL:**\n\n```bash\naws rolesanywhere enable-crl \\\n  --crl-name \"my-pki-crl\" \\\n  --crl-data \"$(base64 crl.pem)\" \\\n  --trust-anchor-arn \"arn:aws:rolesanywhere:us-east-1:123456789012:trust-anchor\u002F$TRUST_ANCHOR_ID\" \\\n  --region us-east-1\n```\n\n**Update the CRL when certificates are revoked:**\n\n```bash\n# Regenerate the CRL in your CA after revoking a certificate\nopenssl ca -gencrl -out crl.pem\n\n# Update the CRL in Roles Anywhere\naws rolesanywhere update-crl \\\n  --crl-id \"$CRL_ID\" \\\n  --crl-data \"$(base64 crl.pem)\" \\\n  --region us-east-1\n```\n\n**Critical:** without a CRL, a compromised certificate remains usable\nuntil it expires. Always configure revocation for production PKIs.\n\n## Step 8 — CloudTrail audit (AssumeRoot)\n\nRoles Anywhere sessions are logged in CloudTrail under the `AssumeRoot`\nevent name (source: `rolesanywhere.amazonaws.com`). Key fields include\n`requestParameters.profileArn`, `requestParameters.trustAnchorArn`, and\n`requestParameters.roleArn`.\n\n**Query CloudTrail for Roles Anywhere sessions:**\n\n> Moved to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md#query-cloudtrail-for-roles-anywhere-sessions-step-8).\n> cloudtrail lookup-events for AssumeRoot sessions in the last hour.\n\n## Step 9 — Recent features\n\n**Recent AWS features (2023-2026):**\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#recent-aws-features-2023-2026).\n> GA, ACM PCA anchors, session policies, role-passthrough, CRLs, helper updates, attribution, cross-account anchors.\n  enabling centralized PKI management.\n\n## NEVER do these things\n\n1. **NEVER assume the trust anchor alone grants access.** The trust\n   anchor only binds the CA to AWS IAM. A profile AND an IAM role with\n   the correct trust policy are ALSO required.\n\n2. **NEVER use an IAM role without a Roles Anywhere trust policy.**\n   The role's trust policy must allow `sts:AssumeRole` from\n   `rolesanywhere.amazonaws.com`. Without it, assume fails with\n   `AccessDenied`.\n\n3. **NEVER list too many roles in a profile.** The `roleArns` list\n   determines which roles the cert can assume. List only the role(s)\n   this specific workload needs. Over-permissive profiles violate\n   least privilege.\n\n4. **NEVER skip revocation configuration.** Without a CRL, a\n   compromised certificate remains usable until it expires. Always\n   configure revocation for production PKIs.\n\n5. **NEVER store the CA private key on the client machine.** The CA\n   private key must be securely stored (HSM, KMS, or offline CA). Only\n   the client certificate and its private key should be on the client.\n\n6. **NEVER assume session policies expand permissions.** Session\n   policies RESTRICT permissions; they never expand them. Effective\n   permissions = IAM role permissions intersected with the session\n   policy.\n\n7. **NEVER use long-lived certificates without expiration.** Certificates\n   should have a reasonable expiration (e.g., 90 days for CI runners,\n   1 year for servers). Avoid 10-year certificates.\n\n8. **NEVER forget the credential helper on the client.** The signing\n   helper must be installed on the client; without it, the workload\n   cannot sign requests with the certificate.\n\n9. **NEVER assume role-passthrough is safe without controls.**\n   Role-passthrough mode lets the client specify any role ARN at\n   assume time. Use only when the client is fully trusted, or when\n   the IAM roles' trust policies enforce strict Conditions.\n\n10. **NEVER ignore CloudTrail audit events.** Roles Anywhere sessions\n    are logged as `AssumeRoot` events. Regularly audit which\n    certificates assumed which roles, especially after a certificate\n    is compromised.\n\n## Output format\n\n```text\nROLES_ANYWHERE: \u003Ctrust-anchor-id> → \u003Cprofile-id> → \u003Crole-arn>\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Trust anchor: \u003Ctrust-anchor-id> — \u003Cca-source> (CERTIFICATE_BUNDLE | AWS_ACM_PCA)\n  [✓|✗] Profile: \u003Cprofile-id> — roleArns: \u003Crole-arn list> (duration: \u003Cseconds>s)\n  [✓|✗] IAM role: \u003Crole-arn> (trust: rolesanywhere.amazonaws.com; permissions: \u003Cdescription>)\n  [✓|✗] Session policy: \u003Cinline|managed|none> — \u003Cdescription>\n  [✓|✗] Credential helper: aws_signing_helper (client-side, cert: \u003Ccert-path>)\n  [✓|✗] Revocation: CRL configured (\u003Ccrl-name>) | Not configured\n  [✓|✗] CloudTrail audit: AssumeRoot events logged\n  [✓|✗] CA certificate verified: \u003Cca-cert-path> (PEM, expires \u003Cdate>)\n  [✓|✗] Client certificate verified: \u003Cclient-cert-path> (PEM, expires \u003Cdate>)\n  [✓|✗] Region: \u003Cregion>\n  [✓|✗] Tags: \u003Ckey=value list>\nVERIFICATION_COMMANDS:\n  aws rolesanywhere list-trust-anchors --region \u003Cregion>\n  aws rolesanywhere list-profiles --region \u003Cregion>\n  aws iam get-role --role-name \u003Crole-name>\n  .\u002Faws_signing_helper credential-process --certificate \u003Ccert> --private-key \u003Ckey> --trust-anchor-id \u003Cid> --profile-id \u003Cid> --role-arn \u003Carn> --region \u003Cregion>\n```\n\n### Worked example — CI runner with external PKI\n\n```text\nROLES_ANYWHERE: ta-aaa111222 → p-bbb222333 → arn:aws:iam::123456789012:role\u002FRolesAnywhereCIRunner\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Trust anchor: ta-aaa111222 — self-managed CA (CERTIFICATE_BUNDLE, ca-cert.pem)\n  [✓] Profile: p-bbb222333 — roleArns: arn:aws:iam::123456789012:role\u002FRolesAnywhereCIRunner (duration: 3600s)\n  [✓] IAM role: arn:aws:iam::123456789012:role\u002FRolesAnywhereCIRunner (trust: rolesanywhere.amazonaws.com; permissions: AmazonS3ReadOnlyAccess)\n  [✓] Session policy: inline — restrict to s3:GetObject on my-ci-artifacts\u002F*\n  [✓] Credential helper: aws_signing_helper (client-side, cert: client-cert.pem)\n  [✓] Revocation: CRL configured (my-pki-crl)\n  [✓] CloudTrail audit: AssumeRoot events logged\n  [✓] CA certificate verified: ca-cert.pem (PEM, expires 2027-12-31)\n  [✓] Client certificate verified: client-cert.pem (PEM, expires 2026-11-01)\n  [✓] Region: us-east-1\n  [✓] Tags: Environment=production, Workload=ci-runner\nVERIFICATION_COMMANDS:\n  aws rolesanywhere list-trust-anchors --region us-east-1\n  aws rolesanywhere list-profiles --region us-east-1\n  aws iam get-role --role-name RolesAnywhereCIRunner\n  .\u002Faws_signing_helper credential-process --certificate client-cert.pem --private-key client-key.pem --trust-anchor-id ta-aaa111222 --profile-id p-bbb222333 --role-arn arn:aws:iam::123456789012:role\u002FRolesAnywhereCIRunner --region us-east-1\n```\n\n## Error handling\n\n> Moved to [references\u002Ferror-handling.md](references\u002Ferror-handling.md#error-handling).\n> AccessDenied, cert not trusted, expired\u002Frevoked cert, helper missing, short sessions.\n\n## References (load on demand)\n\n- [advanced-patterns](references\u002Fadvanced-patterns.md) — misconceptions, dependency graph, expert heuristics, recent features\n- [diagnostic-commands](references\u002Fdiagnostic-commands.md) — credential verification and CloudTrail audit queries\n- [error-handling](references\u002Ferror-handling.md) — symptom-by-symptom troubleshooting\n- [trust-anchor-and-profile](references\u002Ftrust-anchor-and-profile.md) — trust anchor + profile detail (existing)\n- [credential-helper-and-revocation](references\u002Fcredential-helper-and-revocation.md) — helper setup, CRL revocation, CLI integration (existing)\n\n## Domain\n\nAWS CloudOps \u002F IAM Roles Anywhere Trust Infrastructure Provisioning &\nCertificate-Based Authentication.\n\n## AWS documentation\n\n- **IAM Roles Anywhere User Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Frolesanywhere\u002Flatest\u002Fuserguide\u002Fintroduction.html\n- **Create trust anchor** — https:\u002F\u002Fdocs.aws.amazon.com\u002Frolesanywhere\u002Flatest\u002Fuserguide\u002Ftrust-anchors.html\n- **Create profile** — https:\u002F\u002Fdocs.aws.amazon.com\u002Frolesanywhere\u002Flatest\u002Fuserguide\u002Fprofiles.html\n- **Credential helper** — https:\u002F\u002Fdocs.aws.amazon.com\u002Frolesanywhere\u002Flatest\u002Fuserguide\u002Fcredential-helper.html\n- **Revocation (CRL)** — https:\u002F\u002Fdocs.aws.amazon.com\u002Frolesanywhere\u002Flatest\u002Fuserguide\u002Frevocation.html\n- **CloudTrail audit** — https:\u002F\u002Fdocs.aws.amazon.com\u002Frolesanywhere\u002Flatest\u002Fuserguide\u002Fsecurity-logging.html\n- **AWS CLI rolesanywhere** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcli\u002Flatest\u002Freference\u002Frolesanywhere\u002F\n- **IAM Roles Anywhere best practices** — https:\u002F\u002Fdocs.aws.amazon.com\u002Frolesanywhere\u002Flatest\u002Fuserguide\u002Fbest-practices.html\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":41},{"tags":25,"phase":26,"author":27,"domain":28,"family":29,"version":30,"keywords":31,"task_type":32,"complexity":33,"entry_point":34,"skill_class":35,"when_to_use":36,"dependencies":37,"requires_llm":38,"verdict_shape":39,"lifecycle_status":40,"supports_pipeline":38},"aws, iam, roles-anywhere, trust-anchor, certificate-authority, pki, credential-helper, cloudops, deploy, security, session-policy, revocation","1","Jacky Chan — AWS Community Builder","aws-cloudops","Security","0.1.0","aws, iam, roles anywhere, trust anchor, certificate authority, pki, x.509, credential helper, signing helper, sts, temporary credentials, session policy, cloudops, deploy, security, revocation, crl, assume root","deploy","high","false","capability","Invoke when the user wants to create an IAM Roles Anywhere trust anchor (binding an external certificate authority to AWS IAM), create a profile (mapping external certificates to IAM roles), configure the credential helper (AWS signing helper), set up certificate-based authentication to AWS APIs, integrate an external PKI with AWS, configure revocation (CRL\u002FOCSP), or understand the role assumption workflow (exchange X.509 cert for STS credentials). Do NOT invoke for standard IAM role assumption via STS (no certificate), AWS IAM Identity Center (SSO), or AWS Organizations SCC (service control policies).","aws-orchestrator","true","READY_TO_DEPLOY | PREREQUISITES_MISSING","active","Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS CLI v2 with iam, rolesanywhere, sts, cloudwatch, and cloudtrail access, plus the aws_signing_helper binary (downloaded from AWS) on the client machine. Works with Terraform aws_rolesanywhere_trust_anchor, aws_rolesanywhere_profile, and aws_rolesanywhere_crl resources and CloudFormation AWS::RolesAnywhere::TrustAnchor \u002F AWS::RolesAnywhere::Profile templates.","main","eeace51bd5dd1db2030729d83eeab988861553aa","skills\u002Frolesanywhere-trust-deployer",0,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills","https:\u002F\u002Fgithub.com\u002Fjhkchan","CTO & Co-Founder @Beever-AI  & @votee. CAISP. AWS Community Builder. Organizer@GDGCloudHK. MongoDB Champion. Technopreneur + Infornographer.","2026-09-24 08:54:10",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add jhkchan\u002Faws-agent-skills --skill rolesanywhere-trust-deployer",{"tool":56,"command":57},"bunx","bunx skills add jhkchan\u002Faws-agent-skills --skill rolesanywhere-trust-deployer",{"tool":59,"command":60},"pnpm","pnpm dlx skills add jhkchan\u002Faws-agent-skills --skill rolesanywhere-trust-deployer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frolesanywhere-trust-deployer\u002FSKILL.md",true,[64,70,74,78,82,86,90,94,98,102,106,110,114,118,122,126,130,134,138,142],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"eval\u002Ftest-cases.yaml","REFERENCE","参考文档",6238,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frolesanywhere-trust-deployer\u002Feval\u002Ftest-cases.yaml",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"evals\u002Fbaselines\u002Fcredential-helper-sts-exchange.md",703,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frolesanywhere-trust-deployer\u002Fevals\u002Fbaselines\u002Fcredential-helper-sts-exchange.md",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"evals\u002Fbaselines\u002Fmissing-trust-anchor-ca.md",731,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frolesanywhere-trust-deployer\u002Fevals\u002Fbaselines\u002Fmissing-trust-anchor-ca.md",{"path":79,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":80,"sourceHtmlUrl":81},"evals\u002Fbaselines\u002Fprofile-role-mapping.md",652,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frolesanywhere-trust-deployer\u002Fevals\u002Fbaselines\u002Fprofile-role-mapping.md",{"path":83,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":84,"sourceHtmlUrl":85},"evals\u002Fbaselines\u002Frevocation-configuration.md",579,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frolesanywhere-trust-deployer\u002Fevals\u002Fbaselines\u002Frevocation-configuration.md",{"path":87,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":88,"sourceHtmlUrl":89},"evals\u002Fbaselines\u002Ftrust-anchor-certificate-authority.md",768,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frolesanywhere-trust-deployer\u002Fevals\u002Fbaselines\u002Ftrust-anchor-certificate-authority.md",{"path":91,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":92,"sourceHtmlUrl":93},"evals\u002Feval_config.yaml",1822,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frolesanywhere-trust-deployer\u002Fevals\u002Feval_config.yaml",{"path":95,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":96,"sourceHtmlUrl":97},"evals\u002Fevals.json",10552,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frolesanywhere-trust-deployer\u002Fevals\u002Fevals.json",{"path":99,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":100,"sourceHtmlUrl":101},"evals\u002Fprompts\u002Fcredential-helper-sts-exchange.md",647,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frolesanywhere-trust-deployer\u002Fevals\u002Fprompts\u002Fcredential-helper-sts-exchange.md",{"path":103,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":104,"sourceHtmlUrl":105},"evals\u002Fprompts\u002Fmissing-trust-anchor-ca.md",636,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frolesanywhere-trust-deployer\u002Fevals\u002Fprompts\u002Fmissing-trust-anchor-ca.md",{"path":107,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":108,"sourceHtmlUrl":109},"evals\u002Fprompts\u002Fprofile-role-mapping.md",642,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frolesanywhere-trust-deployer\u002Fevals\u002Fprompts\u002Fprofile-role-mapping.md",{"path":111,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":112,"sourceHtmlUrl":113},"evals\u002Fprompts\u002Frevocation-configuration.md",569,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frolesanywhere-trust-deployer\u002Fevals\u002Fprompts\u002Frevocation-configuration.md",{"path":115,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":116,"sourceHtmlUrl":117},"evals\u002Fprompts\u002Ftrust-anchor-certificate-authority.md",672,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frolesanywhere-trust-deployer\u002Fevals\u002Fprompts\u002Ftrust-anchor-certificate-authority.md",{"path":119,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":120,"sourceHtmlUrl":121},"examples\u002FREADME.md",7368,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frolesanywhere-trust-deployer\u002Fexamples\u002FREADME.md",{"path":123,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Fadvanced-patterns.md",9864,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frolesanywhere-trust-deployer\u002Freferences\u002Fadvanced-patterns.md",{"path":127,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":128,"sourceHtmlUrl":129},"references\u002Fcredential-helper-and-revocation.md",10323,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frolesanywhere-trust-deployer\u002Freferences\u002Fcredential-helper-and-revocation.md",{"path":131,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":132,"sourceHtmlUrl":133},"references\u002Fdiagnostic-commands.md",1054,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frolesanywhere-trust-deployer\u002Freferences\u002Fdiagnostic-commands.md",{"path":135,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":136,"sourceHtmlUrl":137},"references\u002Ferror-handling.md",1181,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frolesanywhere-trust-deployer\u002Freferences\u002Ferror-handling.md",{"path":139,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":140,"sourceHtmlUrl":141},"references\u002Ftrust-anchor-and-profile.md",9316,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frolesanywhere-trust-deployer\u002Freferences\u002Ftrust-anchor-and-profile.md",{"path":143,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":144,"sourceHtmlUrl":145},"skill.usf.yaml",4627,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Frolesanywhere-trust-deployer\u002Fskill.usf.yaml",[147,154,161,168,175,182],{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":19},"01M7ADVD60X4PCAPKSE58P9NDC","xray-tracing-deployer","Deploys AWS X-Ray distributed tracing with production-grade configuration: X-Ray daemon deployment (EC2 systemd, ECS sidecar, EKS DaemonSet, Lambda built-in), SDK instrumentation (Java, Python, Node.js, Go, .NET) with annotations and metadata, sampling rules (default reservoir + rate vs custom rules with URL \u002F method \u002F service-name predicates), service map generation, trace query and retrieval, groups and insights, CloudWatch ServiceLens integration, IAM permissions (PutTraceSegments, GetSamplingRules), and latest features (Lambda Powertools tracing, OpenTelemetry \u002F ADOT Collector support, W3C trace context). Emits a READY_TO_DEPLOY checklist with every configuration item verified. Use when enabling X-Ray on a new application, adding tracing to ECS \u002F EKS \u002F Lambda, validating a sampling configuration, or generating daemon deployment CLI and IaC templates. Triggers: X-Ray, distributed tracing, X-Ray daemon, sampling rules, service map, X-Ray SDK, OpenTelemetry, ADOT, Lambda Powertools, CloudWatch ServiceLens.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002FSKILL.md",[],[],{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":19},"01M7ADTVJ7DCBM9CB1FY51GH7J","wellarchitected-workload-auditor","Audits AWS Well-Architected Tool workloads for review staleness, per-pillar high-risk issue counts, milestone tracking gaps, and remediation plan completeness. Emits a deterministic verdict (STALE_REVIEW | HIGH_RISK | CONFIG_GAP | OK) per workload with per-pillar risk breakdown, milestone trend analysis, and specific remediation. Use when reviewing Well-Architected workloads, checking WA review freshness, auditing high-risk issues per pillar, validating milestone coverage, or tracking remediation plans.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwellarchitected-workload-auditor\u002FSKILL.md",[],[],{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":19},"01M7ADT59G6FTTNZYHT2QRPNNP","wellarchitected-review-operator","Operates AWS Well-Architected Tool reviews end-to-end — creates workloads, runs pillar reviews (operational excellence, security, reliability, performance, cost optimization, sustainability, Prosperity), answers questions with risk-tier rationale, generates reports and improvement plans, creates milestones, and integrates with Trusted Advisor and Well-Architected Labs. Runs deterministic pre-checks (workload existence, lens availability, pillar coverage), emits the exact update-answer \u002F get-consolidated-report CLI behind a CONFIRM gate, and verifies risk-tier transitions. Emits READY | BLOCKED | COMPLETED. Use when creating a workload, answering pillar questions, generating an improvement plan, creating a milestone, or integrating with Trusted Advisor. Triggers: well-architected tool, well architected review, workload review, pillar, operational excellence, security, reliability, performance, cost optimization, sustainability, prosperity, improvement plan, milestone, trusted advisor.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwellarchitected-review-operator\u002FSKILL.md",[],[],{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":174,"publishedAt":19},"01M7ADSH5JA9QHNPPHQCD7EVA7","wafv2-web-acl-deployer","Provisions AWS WAFv2 Web ACLs with correct production defaults: scope selection (CLOUDFRONT vs REGIONAL), managed rule groups (AWSManagedRulesCommonRuleSet, SQLiRuleSet, LinuxRuleSet, WindowsRuleSet, IPReputationList, BotControlRuleSet, AmazonIpReputationList, ATP), custom rules (byte match, IP set, regex pattern, geo match, size constraint, rate-based), rule priority ordering, logging destinations (Kinesis Firehose, CloudWatch Logs, S3), resource association (ALB, API Gateway, CloudFront), rate-based rules with aggregate keys (IP, forwarded IP), Challenge and CAPTCHA actions, and account takeover prevention. Emits a READY_TO_DEPLOY checklist. Use when creating a Web ACL, attaching managed rules, configuring rate limiting, enabling WAF logging, associating a Web ACL with an ALB\u002FAPI Gateway\u002FCloudFront, or configuring CAPTCHA\u002FChallenge actions. Triggers: create WAF Web ACL, WAFv2, managed rule groups, WAF rate limiting, WAF logging, WAF CAPTCHA, WAF Challenge action, bot control, ATP managed rules.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwafv2-web-acl-deployer\u002FSKILL.md",[],[],{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":19},"01M7ADRYFAT8R73FBNCHRC573X","wafv2-web-acl-auditor","Audits AWS WAFv2 Web ACL configurations to determine whether the ACL provides effective protection: default-action posture (Allow vs Block), managed-rule-group coverage gaps, rule effectiveness (BLOCK vs COUNT, shadow\u002Fbypass rules, stale exclusions), rate-based rule correctness, logging and visibility configuration, and text-transformation bypass vectors. Emits a deterministic verdict per Web ACL. Use when reviewing a WAFv2 Web ACL for security posture, checking managed-rule coverage, validating rate-limit configuration, auditing WAF logging, or hardening a WAF before production deployment. Triggers: WAF, WAFv2, Web ACL, managed rule group, AWSManagedRules, rate-based rule, CAPTCHA, Challenge, OverrideAction, Count mode, forwarded IP, Bot Control, ATP, text transformation, WAF logging, WAF visibility, OWASP, SQLi, XSS, RFI.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwafv2-web-acl-auditor\u002FSKILL.md",[],[],{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":19},"01M7ADR8W7G72JX4KFGN03QK8Q","waf-rule-deployer","Provisions AWS WAFv2 rule sets with production defaults: Web ACL creation (CloudFront scope in us-east-1 vs Regional scope), rule groups (managed vs custom) with capacity planning in WCU (Web ACL Capacity Units, 1500 default per ACL), managed rule groups (AWSManagedRulesCommonRuleSet, AWSManagedRulesSQLiRuleSet, AWSManagedRulesAmazonIpReputationList, AWSManagedRulesLinuxRuleSet, AWSManagedRulesWindowsRuleSet, AWSManagedRulesUnixRuleSet), custom rules (byte-match, regex pattern set, geo-match, rate-based), IP set and regex pattern set resources, rule priority ordering (lowest number evaluated first), action types (allow, block, count, CAPTCHA, Challenge), bot control managed rule group, account takeover. Triggers: create WAF rule, WAF managed rule group, WAF custom rule, WAF byte match, WAF geo match, WAF rate based rule, WAF IP set, WAF regex pattern set, WAF WCU budget, WAF CloudFront ACL, WAF logging Kinesis Firehose, WAF bot control, WAF ATP, WAF label matching, WAF Challenge action, WAF CAPTCHA.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwaf-rule-deployer\u002FSKILL.md",[],[]]