codecommit-repository-deployer
Provisions AWS CodeCommit repositories with production defaults: repository creation (create-repository), default branch, KMS encryption with customer-managed key, approval rule templates and branch protection, notification rules, pull request templates, cross-account resource policy, repository triggers (Lambda/SNS), migration from external Git, IAM git credentials vs SSH keys vs git-remote-codecommit, and CodeBuild/CodePipeline connection. Emits a READY_TO_DEPLOY checklist with verification commands. Use when creating a CodeCommit repository, configuring approval rules, KMS encryption, cross-account access, or migrating from external Git. Triggers: create codecommit repository, codecommit approval rule, codecommit kms encryption, codecommit cross-account, codecommit trigger, git-remote-codecommit.
- License 许可
- Apache-2.0
- 最近更新
- 2026-09-24
- Stars
- ★ 4
- Forks
- 0
01 前言 Front Matter
- name
- codecommit-repository-deployer
- license
- Apache-2.0
- metadata
- { "tags": "aws, codecommit, git, cloudops, deploy, dev-tools, provisioning, approval-rule, branch-protection, kms, notification, cross-account, codebuild", "phase": "1", "author": "Jacky Chan — AWS Community Builder", "domain": "aws-cloudops", "family": "DevTools", "version": "0.1.0", "keywords": "aws, codecommit, repository, git, cloudops, deploy, provisioning, approval rule template, branch protection, kms encryption, notification rule, pull request template, cross-account, git-remote-codecommit, codebuild, codepipeline", "task_type": "deploy", "complexity": "high", "entry_point": "false", "skill_class": "capability", "when_to_use": "Invoke when the user wants to create a CodeCommit repository, configure a default branch, set up an approval rule template for branch protection, enable KMS encryption with a customer-managed key, create notification rules for repository events, add a pull request template, configure cross-account access via resource policy, set up repository triggers (Lambda/SNS), migrate from an external Git provider, connect the repository to CodeBuild or CodePipeline, or choose between IAM git credentials, SSH keys, and git-remote-codecommit (GRC) for authentication. Do NOT invoke for auditing existing repositories (use codecommit-repository-auditor), GitHub repository management, or CodeBuild/CodePipeline pipeline configuration itself.", "dependencies": "aws-orchestrator", "requires_llm": "true", "verdict_shape": "READY_TO_DEPLOY | PREREQUISITES_MISSING", "lifecycle_status": "active", "supports_pipeline": "true" }
- description
- Provisions AWS CodeCommit repositories with production defaults: repository creation (create-repository), default branch, KMS encryption with customer-managed key, approval rule templates and branch protection, notification rules, pull request templates, cross-account resource policy, repository triggers (Lambda/SNS), migration from external Git, IAM git credentials vs SSH keys vs git-remote-codecommit, and CodeBuild/CodePipeline connection. Emits a READY_TO_DEPLOY checklist with verification commands. Use when creating a CodeCommit repository, configuring approval rules, KMS encryption, cross-account access, or migrating from external Git. Triggers: create codecommit repository, codecommit approval rule, codecommit kms encryption, codecommit cross-account, codecommit trigger, git-remote-codecommit.
- compatibility
- Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS CLI v2 with codecommit, kms, iam, sns, and lambda access (and cross-account STS assume-role if cross-account repository access). Works with Terraform aws_codecommit_repository / aws_codecommit_approval_rule_template / aws_codecommit_trigger resources and CloudFormation AWS::CodeCommit::Repository templates.
02 资源文件 20
- 参考文档eval/test-cases.yaml6.2 KB
- 参考文档evals/baselines/branch-protection-and-notification.md741 B
- 参考文档evals/baselines/cross-account-resource-policy.md686 B
- 参考文档evals/baselines/git-remote-codecommit-iam-auth.md844 B
- 参考文档evals/baselines/missing-kms-key-policy-cross-account.md719 B
- 参考文档evals/baselines/standard-repo-with-kms.md710 B
- 参考文档evals/eval_config.yaml1.8 KB
- 参考文档evals/evals.json9.5 KB
- 参考文档evals/prompts/branch-protection-and-notification.md739 B
- 参考文档evals/prompts/cross-account-resource-policy.md578 B
- 参考文档evals/prompts/git-remote-codecommit-iam-auth.md524 B
- 参考文档evals/prompts/missing-kms-key-policy-cross-account.md579 B
- 参考文档evals/prompts/standard-repo-with-kms.md663 B
- 参考文档examples/README.md6.9 KB
- 参考文档references/advanced-patterns.md3.0 KB
- 参考文档references/approval-rules-and-protection.md6.5 KB
- 参考文档references/auth-and-cross-account.md9.0 KB
- 参考文档references/error-handling.md1.1 KB
- 参考文档references/worked-examples.md1.4 KB
- 参考文档skill.usf.yaml4.3 KB
03 SKILL.md 正文
CodeCommit Repository Deployer
An AWS CloudOps agent skill that provisions AWS CodeCommit repositories with correct defaults. The skill walks the operator through repository creation, default branch selection, KMS encryption with a customer- managed key, approval rule templates for branch protection, notification rules, pull request templates, cross-account access via resource policy, repository triggers, authentication method selection (IAM git credentials vs SSH vs git-remote-codecommit), and migration from external Git, captures configuration decisions, explains why each default matters, and emits a READY_TO_DEPLOY checklist with copy-pasteable verification commands.
Activation keywords
create CodeCommit repository, CodeCommit default branch, CodeCommit approval rule template, CodeCommit branch protection, CodeCommit KMS encryption, CodeCommit notification rule, CodeCommit pull request template, CodeCommit cross-account access, CodeCommit trigger, git-remote-codecommit, CodeCommit migration.
STRICT output contract
When this skill is invoked with a CodeCommit-provisioning request
(create a repository, configure branch protection, set up approval rule
templates, enable KMS encryption, configure cross-account access,
migrate from external Git, or a partial configuration), the agent MUST
respond with the READY_TO_DEPLOY checklist defined in the "Output
format" section using the literal all-caps labels CODECOMMIT_REPO:,
VERDICT:, CHECKLIST:, and VERIFICATION_COMMANDS:. Do NOT preface
the checklist with prose, headings, or disclaimers — emit the block as
the first lines of the response. This contract is what assertion-based
evals and downstream provisioning pipelines rely on; deviating from the
literal labels breaks automation silently.
If any prerequisite is missing, the verdict is PREREQUISITES_MISSING
with a specific gap citation in the checklist (marked [✗]), and
READY_TO_DEPLOY MUST NOT also appear.
FORBIDDEN output patterns
-
NEVER emit
VERDICT: READY_TO_DEPLOYwhen any CHECKLIST item is[✗]. If even one prerequisite is unmet, the verdict MUST bePREREQUISITES_MISSING. A mixed-verdict block is a contract violation. -
NEVER show KMS encryption as configured without verifying the key policy grants
codecommit.amazonaws.com. The repository creates successfully without the key policy grant — push/pull fails silently with AccessDenied at encryption time. The CHECKLIST MUST state "key policy grants codecommit.amazonaws.com" explicitly. -
NEVER show cross-account access as configured without verifying BOTH the repository resource policy AND the KMS key policy. Granting only one results in AccessDenied. If the repository is KMS-encrypted, the CHECKLIST MUST list both policy grants.
-
NEVER list an approval rule template without confirming it is ASSOCIATED with the repository. Creating a template alone does nothing — it must be explicitly associated via
associate-approval-rule-template-with-repository. The CHECKLIST MUST state "associated" or the item is[✗]. -
NEVER confuse notification rules (CodeStar Notifications) with repository triggers (Lambda/SNS direct invocation) in the CHECKLIST. These are separate mechanisms. The CHECKLIST MUST list them as distinct items, not collapse them into a single "notifications" line.
-
NEVER omit the git-remote-codecommit (GRC) URL from the output. The GRC clone URL (
codecommit://<region>@<repo-name>) is the primary verification artifact for IAM-role-based authentication. The CHECKLIST MUST include the auth method and URL. -
NEVER substitute lowercase or camelCase labels. The literal all-caps labels (
CODECOMMIT_REPO:,VERDICT:,CHECKLIST:,VERIFICATION_COMMANDS:) are parsed by downstream automation. Markdown headings or bold variants break the parser silently.
Quick navigation
| Section | When to read |
|---|---|
| Prerequisites | Always — verify before provisioning |
| Step 1 — Repository creation and default branch | Core creation |
| Step 2 — KMS encryption (customer-managed key) | Encryption config |
| Step 3 — Approval rule templates and branch protection | Governance |
| Step 4 — Notification rules (SNS/EventBridge) | Event routing |
| Step 5 — Pull request templates | PR standardization |
| Step 6 — Cross-account access via resource policy | Cross-account |
| Step 7 — Repository triggers (Lambda/SNS) | Automation hooks |
| Step 8 — Authentication: git credentials vs SSH vs GRC | Auth selection |
| Step 9 — Migration from external Git | Repository migration |
| Step 10 — CodeBuild/CodePipeline connection | CI/CD wiring |
| NEVER do these things | Review before signing off |
| Output format | The literal checklist template |
| references/approval-rules-and-protection.md | Approval rule detail |
| references/auth-and-cross-account.md | Auth + cross-account detail |
Mindset
One-line takeaway: A CodeCommit repository is a managed Git
repository. The default branch must be explicitly created on first
push (or via the console). KMS encryption with a customer-managed key
requires the key policy to grant CodeCommit (kms:GenerateDataKey and
kms:Encrypt/Decrypt). Approval rule templates enforce required
reviewers on pull requests BEFORE merge — branch protection prevents
direct pushes to protected branches.
Three misconceptions (default branch does not exist until first push; KMS key policy grant; GRC vs git credentials) — full text: Advanced patterns.
Configuration dependency graph (novel heuristic)
Full dependency table (repository, KMS encryption, default branch, approval rule template, notification rule, cross-account resource policy, repository trigger) with silent-failure modes: Advanced patterns.
Expert heuristic: git-remote-codecommit for IAM auth
Auth-method decision tree (GRC vs IAM git credentials vs SSH): Auth and cross-account.
Expert heuristic: approval rule template scope
Approval rule template lifecycle and the approval-rules vs branch-protection split: Approval rules and protection.
Expert heuristic: KMS key policy cross-account grant
Cross-account resource policy + KMS key policy grant pair (missing either = AccessDenied): Auth and cross-account.
Prerequisites (verify before provisioning)
Before emitting provisioning commands, verify these prerequisites. If any are missing, the verdict is PREREQUISITES_MISSING.
| Prerequisite | Why it matters | How to verify |
|---|---|---|
| Repository name available | Must be unique within the account+region | aws codecommit get-repository --repository-name <name> (should fail) |
| KMS key exists (if encryption) | Customer-managed key must exist | aws kms describe-key --key-id <key-id> |
| KMS key policy grants CodeCommit | Without it, push/pull fails silently | aws kms get-key-policy --key-id <key-id> |
| SNS topic exists (if notifications) | Notification rule target must exist | aws sns get-topic-attributes --topic-arn <arn> |
| SNS topic policy grants CodeStar | Without it, notifications never fire | Check topic attributes |
| Cross-account principal identified | Resource policy + KMS key policy need it | aws sts get-caller-identity in cross-account |
| Lambda function exists (if triggers) | Trigger target must exist | aws lambda get-function --function-name <name> |
| IAM auth method decided | GRC vs git credentials vs SSH | Confirm auth model |
Step 1 — Repository creation and default branch
REPO_ARN=$(aws codecommit create-repository \
--repository-name my-app-repo \
--repository-description "Microservice repository for my-app" \
--tags Environment=production,Team=platform \
--query 'repositoryMetadata.Arn' --output text --region us-east-1)
Default branch caveat: --default-branch main sets the default
branch name in metadata, but the main branch does NOT exist until you
push the first commit. The repository is empty at creation.
git remote add origin codecommit://us-east-1@my-app-repo
echo "# my-app" > README.md
git add . && git commit -m "initial commit"
git push -u origin main
Common mistake: configuring approval rules or branch protection on
main before the first push. The protections have nothing to act on.
Step 2 — KMS encryption (customer-managed key)
CodeCommit encrypts repositories at rest. By default, it uses an AWS-managed key. For customer-managed key encryption, the key must have a policy granting CodeCommit.
Required KMS key policy statement:
{
"Sid": "AllowCodeCommitServiceAccess",
"Effect": "Allow",
"Principal": { "Service": "codecommit.amazonaws.com" },
"Action": ["kms:Encrypt", "kms:Decrypt", "kms:ReEncrypt*",
"kms:GenerateDataKey*", "kms:DescribeKey"],
"Resource": "*"
}
Critical: the KMS key policy grant to codecommit.amazonaws.com is
the most commonly forgotten configuration. Without it, the repository
creates successfully, but all push/pull operations fail with
AccessDenied. Use CloudFormation/Terraform for IaC to ensure the key
policy is correct.
Step 3 — Approval rule templates and branch protection
# Create an approval rule template
aws codecommit create-approval-rule-template \
--approval-rule-template-name "require-two-reviewers" \
--approval-rule-template-content '{
"Version": "2018-02-08",
"Statements": [{
"Type": "Approvers",
"NumberOfApprovalsNeeded": 2,
"ApprovalPoolMembers": [
"arn:aws:iam::123456789012:user/alice",
"arn:aws:iam::123456789012:user/bob"
]
}]
}' --region us-east-1
# Associate the template with the repository (CRITICAL — template alone does nothing)
aws codecommit associate-approval-rule-template-with-repository \
--approval-rule-template-name "require-two-reviewers" \
--repository-name "my-app-repo" --region us-east-1
Branch protection via IAM policy (deny direct push to main):
{
"Sid": "DenyDirectPushToMain",
"Effect": "Deny",
"Action": "codecommit:GitPush",
"Resource": "arn:aws:codecommit:us-east-1:123456789012:my-app-repo",
"Condition": {
"StringEquals": { "codecommit:References": ["refs/heads/main"] }
}
}
This IAM policy, attached to developers, forces them to use pull requests (which are then governed by the approval rule template).
Step 4 — Notification rules (SNS/EventBridge)
Notification rules route repository events to SNS topics. Notification rules use AWS CodeStar Notifications — NOT EventBridge directly.
# Create SNS topic and set policy granting CodeStar Notifications
TOPIC_ARN=$(aws sns create-topic --name "codecommit-notifications" \
--query 'TopicArn' --output text --region us-east-1)
aws sns set-topic-attributes --topic-arn "$TOPIC_ARN" \
--attribute-name Policy \
--attribute-value '{"Version":"2012-10-17","Statement":[{"Effect":"Allow","Principal":{"Service":"codestar-notifications.amazonaws.com"},"Action":"sns:Publish","Resource":"'"$TOPIC_ARN"'"}]}'
# Create the notification rule
aws codestar-notifications create-notification-rule \
--name "my-app-pr-notifications" \
--resource "arn:aws:codecommit:us-east-1:123456789012:my-app-repo" \
--event-type-ids pull-request-created pull-request-updated pull-request-merged \
--targets '[{"Id":"'"$TOPIC_ARN"'"}]' --detail-type FULL --region us-east-1
Critical: the SNS topic policy grant to
codestar-notifications.amazonaws.com is the #1 forgotten configuration
for notification rules. Without it, the rule creates but no
notifications fire.
Step 5 — Pull request templates
A pull request template is a markdown file committed to the repository.
When a developer creates a PR, the template pre-populates the
description. Commit the file to a standard path
(e.g., .github/PULL_REQUEST_TEMPLATE.md). The template appears on new
PRs after the file is committed.
Step 6 — Cross-account access via resource policy
Cross-account access requires the repository resource policy to grant the cross-account principal CodeCommit permissions. If the repository is KMS-encrypted, the KMS key policy must ALSO grant the cross-account principal.
Repository resource policy:
Principal: arn:aws:iam::999999999999:root
Actions: codecommit:GitPull, codecommit:GitPush, GetRepository
KMS key policy (ALSO required):
Principal: arn:aws:iam::999999999999:root
Actions: kms:Decrypt, kms:Encrypt, kms:ReEncrypt*,
kms:GenerateDataKey*, kms:DescribeKey
Critical: BOTH the repository resource policy AND the KMS key policy must grant the cross-account principal. Granting only one results in AccessDenied. This is the #1 cause of cross-account CodeCommit failures.
Step 7 — Repository triggers (Lambda/SNS)
Repository triggers are a LEGACY mechanism that invokes Lambda or SNS directly when repository events occur. Triggers are SEPARATE from notification rules.
aws codecommit put-repository-triggers \
--repository-name "my-app-repo" \
--trigger-name "lambda-on-push" \
--trigger-target-arn "arn:aws:lambda:us-east-1:123456789012:function:trigger-handler" \
--branches "main" "develop" --events "all" --region us-east-1
The Lambda resource policy must allow CodeCommit to invoke:
aws lambda add-permission \
--function-name "trigger-handler" \
--statement-id "AllowCodeCommitInvoke" \
--action "lambda:InvokeFunction" \
--principal "codecommit.amazonaws.com" \
--source-arn "arn:aws:codecommit:us-east-1:123456789012:my-app-repo" --region us-east-1
Step 8 — Authentication: git credentials vs SSH vs GRC
| Method | Best for | Credential type | Rotation |
|---|---|---|---|
| git-remote-codecommit (GRC) | SSO/federated, IAM-role-based | Session token (auto) | Automatic |
| IAM git credentials | CI/CD pipelines with fixed identity | Static username + password | Manual |
| SSH keys | Developers preferring key-based auth | Per-IAM-user SSH key | Manual |
GRC and IAM git-credential setup commands: Auth and cross-account.
Step 9 — Migration from external Git
To migrate from GitHub, GitLab, or Bitbucket to CodeCommit, mirror the repository.
# 1. Create the target CodeCommit repository (empty)
# 2. Clone the source repository as a mirror
git clone --mirror https://github.com/org/source-repo.git
cd source-repo.git
# 3. Push the mirror to CodeCommit (using GRC)
git push codecommit://us-east-1@migrated-repo --all
git push codecommit://us-east-1@migrated-repo --tags
# 4. Verify all branches and tags are present
aws codecommit list-branches --repository-name "migrated-repo" --region us-east-1
Migration checklist: all branches mirrored; all tags pushed
explicitly (--tags); pull request history is NOT migrated (CodeCommit
does not import PRs from external providers); webhooks/CI must be
reconfigured; developer access must be reconfigured.
Step 10 — CodeBuild/CodePipeline connection
The pipeline service role needs CodeCommit permissions:
{
"Effect": "Allow",
"Action": ["codecommit:GetRepository", "codecommit:GitPull",
"codecommit:UploadArchive", "codecommit:GetUploadArchiveStatus",
"codecommit:CancelUploadArchive"],
"Resource": "arn:aws:codecommit:us-east-1:123456789012:my-app-repo"
}
Pipeline source action: SourceType: CODECOMMIT,
SourceLocation: https://codecommit.us-east-1.amazonaws.com/v1/repos/my-app-repo,
Branch: main. If the repository is KMS-encrypted, the pipeline service
role also needs kms:Decrypt on the key.
NEVER do these things
-
NEVER assume the default branch exists at creation. The
defaultBranchNameis metadata. The branch does NOT exist until the first commit is pushed. -
NEVER create a KMS-encrypted repository without verifying the key policy grants CodeCommit. The repository creates successfully, but all push/pull operations fail with AccessDenied.
-
NEVER grant cross-account access via only the repository resource policy. If the repository is KMS-encrypted, the KMS key policy must ALSO grant the cross-account principal.
-
NEVER confuse notification rules with repository triggers. Notification rules use CodeStar Notifications. Repository triggers invoke Lambda/SNS directly. They are separate mechanisms.
-
NEVER create a notification rule without verifying the SNS topic policy. The SNS topic policy must grant
codestar-notifications.amazonaws.comthesns:Publishaction. -
NEVER create a repository trigger without verifying the target resource policy. Lambda must grant
codecommit.amazonaws.comlambda:InvokeFunction. SNS must grant CodeCommitsns:Publish. -
NEVER assume approval rule templates auto-apply to repositories. Templates must be explicitly ASSOCIATED via
associate-approval-rule-template-with-repository. -
NEVER rely on approval rules alone for branch protection. Approval rules govern PR merges. Branch protection requires an IAM policy denying
codecommit:GitPushto specific branches. -
NEVER use static git credentials for SSO/federated environments. Use git-remote-codecommit (GRC) for federated/IAM-role-based auth.
-
NEVER forget to migrate tags during external Git migration.
git push --mirrordoes NOT always carry tags. Rungit push --tagsexplicitly.
Output format
CODECOMMIT_REPO: <repository-name> (<repository-arn>)
VERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING
CHECKLIST:
[✓|✗] Repository name: <name> (unique in account+region)
[✓|✗] Default branch: <branch> (created at first push)
[✓|✗] Description: <description>
[✓|✗] KMS encryption: customer-managed key <key-id> (key policy grants CodeCommit) | AWS-managed
[✓|✗] KMS key policy cross-account: granted to <cross-acct> | N/A
[✓|✗] Approval rule template: <template-name> (associated, <N> approvals needed)
[✓|✗] Branch protection: IAM policy denies direct push to <branch> | Not configured
[✓|✗] Notification rule: <rule-name> → SNS <topic-arn> (topic policy grants CodeStar)
[✓|✗] Pull request template: <path> (committed to repo)
[✓|✗] Cross-account access: resource policy grants <cross-acct-principal>
[✓|✗] Repository trigger: <trigger-name> → <target-arn> | None
[✓|✗] Auth method: git-remote-codecommit (GRC) | IAM git credentials | SSH keys
[✓|✗] CodePipeline/CodeBuild: service role has codecommit:GetRepository
[✓|✗] Tags: <key=value list>
VERIFICATION_COMMANDS:
aws codecommit get-repository --repository-name <name> --region <region>
aws kms describe-key --key-id <key-id> --region <region>
aws codecommit list-approval-rule-templates --region <region>
aws codestar-notifications list-notification-rules --region <region>
Worked example — repository with KMS encryption, approval rules, and cross-account resource policy
CODECOMMIT_REPO: shared-platform-repo (arn:aws:codecommit:us-east-1:123456789012:shared-platform-repo)
VERDICT: READY_TO_DEPLOY
CHECKLIST:
[✓] Repository name: shared-platform-repo (unique in account 123456789012, us-east-1)
[✓] Default branch: main (created at first push)
[✓] Description: Cross-platform shared library repository
[✓] KMS encryption: customer-managed key arn:aws:kms:us-east-1:123456789012:key/a1b2c3d4-5678-90ef-1234-567890abcdef (key policy grants codecommit.amazonaws.com: kms:Encrypt, Decrypt, ReEncrypt*, GenerateDataKey*, DescribeKey)
[✓] KMS key policy cross-account: granted to arn:aws:iam::999999999999:root (kms:Decrypt, Encrypt, ReEncrypt*, GenerateDataKey*, DescribeKey)
[✓] Cross-account resource policy: grants arn:aws:iam::999999999999:root (codecommit:GitPull, GitPush, GetRepository, UploadArchive)
[✓] Approval rule template: require-two-reviewers (associated, 2 approvals needed, pool: arn:aws:iam::123456789012:user/alice, arn:aws:iam::123456789012:user/bob)
[✓] Branch protection: IAM policy DenyDirectPushToMain denies codecommit:GitPush on refs/heads/main
[✓] Notification rule: platform-pr-notifications → SNS arn:aws:sns:us-east-1:123456789012:codecommit-notifications (topic policy grants codestar-notifications.amazonaws.com sns:Publish)
[✓] Pull request template: .github/PULL_REQUEST_TEMPLATE.md (committed to repo)
[✓] Repository trigger: lambda-on-push → arn:aws:lambda:us-east-1:123456789012:function:trigger-handler (Lambda policy grants codecommit.amazonaws.com lambda:InvokeFunction)
[✓] Auth method: git-remote-codecommit (GRC) — clone URL: codecommit://us-east-1@shared-platform-repo
[✓] CodePipeline/CodeBuild: service role has codecommit:GetRepository + GitPull on arn:aws:codecommit:us-east-1:123456789012:shared-platform-repo
[✓] Tags: Environment=production, Team=platform, CrossAccount=true
VERIFICATION_COMMANDS:
aws codecommit get-repository --repository-name shared-platform-repo --region us-east-1
aws kms describe-key --key-id arn:aws:kms:us-east-1:123456789012:key/a1b2c3d4-5678-90ef-1234-567890abcdef --region us-east-1
aws kms get-key-policy --key-id arn:aws:kms:us-east-1:123456789012:key/a1b2c3d4-5678-90ef-1234-567890abcdef --policy-name default --region us-east-1
aws codecommit list-approval-rule-templates --region us-east-1
aws codestar-notifications list-notification-rules --region us-east-1
# Cross-account verification (run in account 999999999999):
git clone codecommit://us-east-1@shared-platform-repo
Worked example — PREREQUISITES_MISSING (KMS key policy not granted)
Full checklist block: Worked examples.
Error handling
Symptom fixes (KMS AccessDenied, cross-account AccessDenied, silent notifications, trigger not firing, approval rule not enforced): Error handling.
References (load on demand)
- Advanced patterns — three-misconception deep dive, configuration dependency graph
- Worked examples — PREREQUISITES_MISSING (KMS key policy not granted) checklist
- Error handling — provisioning failure symptom fixes
- Approval rules and protection — approval rule template lifecycle and scope
- Auth and cross-account — GRC heuristic, KMS cross-account grants, GRC/SSH/credential setup
Domain
AWS CloudOps / AWS CodeCommit Repository Provisioning & Developer Tools Configuration.
AWS documentation
- CodeCommit User Guide — https://docs.aws.amazon.com/codecommit/latest/userguide/welcome.html
- KMS encryption — https://docs.aws.amazon.com/codecommit/latest/userguide/encryption.html
- Approval rule templates — https://docs.aws.amazon.com/codecommit/latest/userguide/approval-rule-templates.html
- Notification rules — https://docs.aws.amazon.com/dtconsole/latest/userguide/notifications.html
- Repository triggers — https://docs.aws.amazon.com/codecommit/latest/userguide/how-to-notify.html
- git-remote-codecommit — https://docs.aws.amazon.com/codecommit/latest/userguide/setting-up-git-remote-codecommit.html
- Cross-account access — https://docs.aws.amazon.com/codecommit/latest/userguide/cross-account.html
04 同仓库更多 Skills
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 / method / 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 / 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 / EKS / 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.
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.
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 / 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.
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/API Gateway/CloudFront, or configuring CAPTCHA/Challenge 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.
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/bypass 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.
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.