AGENT SKILL

transfer-family-workflow-deployer

Provisions AWS Transfer Family servers and managed workflows with production defaults: SFTP/FTPS/FTP protocol, identity provider (service-managed, AWS Directory Service, custom Lambda), endpoint type (PUBLIC, VPC, VPC_ENDPOINT), security groups and subnets, Route 53 hosted zone DNS, user home directory mapping (logical vs physical), S3 access via IAM role and session policy for per-user scoping, AS2 connectors for trading partner exchange, Managed Workflow with Step Functions for file processing, structured JSON logging, server host key, trusted host keys. Emits a READY_TO_DEPLOY checklist with verification commands. Use when creating a Transfer Family SFTP server, configuring custom Lambda authentication, setting up VPC endpoint for private SFTP, or deploying managed workflows. Triggers: create transfer family sftp server, transfer family custom lambda identity, transfer family vpc endpoint, transfer family managed workflow, transfer family as2 connector, sftp user session policy.

License 许可
Apache-2.0
最近更新
2026-09-24
Stars
★ 4
Forks
0

01 前言 Front Matter

name
transfer-family-workflow-deployer
license
Apache-2.0
metadata
{ "tags": "aws, transfer-family, sftp, cloudops, deploy, storage, provisioning, managed-file-transfer, session-policy, as2, managed-workflow, vpc-endpoint", "phase": "1", "author": "Jacky Chan — AWS Community Builder", "domain": "aws-cloudops", "family": "Storage", "version": "0.1.0", "keywords": "aws, transfer family, sftp, ftps, ftp, storage, cloudops, deploy, provisioning, managed file transfer, mft, session policy, as2, managed workflow, vpc endpoint, identity provider, custom lambda, service managed, home directory, host key", "task_type": "deploy", "complexity": "high", "entry_point": "false", "skill_class": "capability", "when_to_use": "Invoke when the user wants to create or configure an AWS Transfer Family server (SFTP, FTPS, FTP), set up identity provider (service-managed, Directory Service, custom Lambda), configure VPC or VPC_ENDPOINT for private SFTP access, manage user home directory mapping, configure per-user S3 access via session policy, deploy managed workflows for file processing, or set up AS2 connectors for B2B file exchange. Do NOT invoke for AWS DataSync (use datasync skills), S3 direct access patterns, or Storage Gateway.", "dependencies": "aws-orchestrator", "requires_llm": "true", "verdict_shape": "READY_TO_DEPLOY | PREREQUISITES_MISSING", "lifecycle_status": "active", "supports_pipeline": "true" }
description
Provisions AWS Transfer Family servers and managed workflows with production defaults: SFTP/FTPS/FTP protocol, identity provider (service-managed, AWS Directory Service, custom Lambda), endpoint type (PUBLIC, VPC, VPC_ENDPOINT), security groups and subnets, Route 53 hosted zone DNS, user home directory mapping (logical vs physical), S3 access via IAM role and session policy for per-user scoping, AS2 connectors for trading partner exchange, Managed Workflow with Step Functions for file processing, structured JSON logging, server host key, trusted host keys. Emits a READY_TO_DEPLOY checklist with verification commands. Use when creating a Transfer Family SFTP server, configuring custom Lambda authentication, setting up VPC endpoint for private SFTP, or deploying managed workflows. Triggers: create transfer family sftp server, transfer family custom lambda identity, transfer family vpc endpoint, transfer family managed workflow, transfer family as2 connector, sftp user session policy.
compatibility
Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS CLI v2 with transfer access, plus iam, s3, ec2, route53, and lambda access for custom identity providers and VPC endpoints. Works with Terraform aws_transfer_server / aws_transfer_user / aws_transfer_workflow resources and CloudFormation AWS::Transfer::Server / AWS::Transfer::User / AWS::Transfer::Workflow templates.

02 资源文件 20

03 SKILL.md 正文

Transfer Family Workflow Deployer

An AWS CloudOps agent skill that provisions AWS Transfer Family servers and managed workflows with correct defaults. The skill walks the operator through protocol selection (SFTP/FTPS/FTP), identity provider choice (service-managed, Directory Service, custom Lambda), endpoint type (PUBLIC, VPC, VPC_ENDPOINT), VPC and security group configuration, Route 53 hosted zone DNS, user home directory mapping (logical vs physical), per-user S3 access via IAM role and session policy, AS2 connectors for trading partner exchange, managed workflow with Step Functions for file landing zone automation, structured JSON logging, CloudWatch metrics and throttling, server host key generation, and trusted host keys for partner verification, captures architecture decisions, explains why each default matters, and emits a READY_TO_DEPLOY checklist with copy-pasteable verification commands.

Activation keywords

create Transfer Family SFTP server, Transfer Family custom Lambda identity, Transfer Family VPC endpoint, Transfer Family managed workflow, Transfer Family AS2 connector, SFTP user session policy, Transfer Family hosted zone Route 53, SFTP home directory mapping, Transfer Family server host key, Transfer Family trusted host keys.

STRICT output contract

When this skill is invoked with a Transfer-Family-provisioning request (create a server, configure identity provider, set up VPC endpoint, deploy managed workflow, configure AS2 connector, 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 TRANSFER_FAMILY:, 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.

Quick navigation

Section When to read
Prerequisites Always — verify before provisioning
Step 1 — Server model and protocols Core Transfer Family model
Step 2 — Identity provider (service-managed, DS, Lambda) Authentication
Step 3 — Endpoint type (PUBLIC, VPC, VPC_ENDPOINT) Network placement
Step 4 — VPC, subnets, security groups Private connectivity
Step 5 — Route 53 hosted zone DNS Custom hostname
Step 6 — User home directory mapping S3 path mapping
Step 7 — IAM role and session policy Per-user S3 scoping
Step 8 — Server host key and trusted host keys SSH key management
Step 9 — AS2 connectors B2B trading partner exchange
Step 10 — Managed workflows File landing zone automation
Step 11 — Structured JSON logging and CloudWatch Observability
Step 12 — Throttling and limits Performance
Step 13 — Recent features Latest
NEVER do these things Review before signing off
Output format The literal checklist template
references/identity-providers-and-endpoints.md IDP + endpoint detail
references/managed-workflows-and-as2.md Workflow + AS2 detail

Mindset

One-line takeaway: AWS Transfer Family is a managed SFTP/FTPS/FTP server that bridges legacy file transfer protocols with AWS S3 (and EFS). Users authenticate via service-managed SSH keys, AWS Directory Service, or a custom Lambda identity provider. Each user is scoped to specific S3 paths via a session policy applied at connection time. Managed workflows automate pre/post file processing via Step Functions.

Three misconceptions dominate Transfer Family misdesign at provisioning time:

  • "Public endpoint with service-managed auth is fine for production." For B2B or internal file transfers, a PUBLIC endpoint exposes the SFTP server to the entire internet. VPC or VPC_ENDPOINT provides private connectivity. Combined with a custom Lambda identity provider, this gives enterprise-grade access control including MFA, credential brokering, and audit trails.

  • "The IAM role's S3 permissions are sufficient." They are not. The IAM role defines the MAXIMUM permissions, but the session policy defines the EFFECTIVE per-user scope. A user with an IAM role that grants s3:* on * but a session policy that restricts to s3:GetObject on my-bucket/home/alice/* can only read their own directory. Without a session policy, the user inherits the full IAM role permissions — a security risk.

  • "Managed workflows are optional post-processing." They are the core value of a file landing zone. Without a managed workflow, files land in S3 and sit there. A managed workflow with Step Functions can trigger virus scanning, format validation, transformation, and routing on every upload — turning SFTP from a passive file store into an active data pipeline.

Configuration dependency graph (novel heuristic)

Transfer Family configurations are NOT independent. The endpoint type determines whether VPC subnets and security groups are required. The identity provider determines whether a Lambda function needs to be deployed. The session policy must reference S3 paths that match the user's home directory mapping. Use this graph to sequence provisioning.

Configuration Hard dependencies (API error without) Silent failure / immutability Enables downstream
Transfer server IAM role for logging; S3 bucket exists server creation succeeds but USERS cannot connect until identity provider is configured SFTP/FTPS/FTP endpoint
Identity provider Lambda function (for custom); Directory Service (for managed DS) service-managed users created via create-user but cannot authenticate without SSH key upload user authentication
Endpoint type — VPC VPC ID, subnet IDs, security group IDs VPC endpoint requires a VPC with DNS resolution enabled; NLB is provisioned automatically private SFTP connectivity
Endpoint type — VPC_ENDPOINT VPC ID, subnet IDs, security group IDs uses PrivateLink (no NLB); clients connect from within the VPC or via peering/TGW private SFTP via PrivateLink
User home directory S3 bucket exists; logical mapping if HomeDirectoryType=LOGICAL physical mapping uses HomeDirectory=/bucket/path; logical mapping uses HomeDirectoryDetails with entry/ target pairs per-user S3 path
IAM role (user) trust policy allowing transfer.amazonaws.com; S3 permissions without S3 permissions, user authenticates but CANNOT read/write files S3 access for the user
Session policy IAM role attached; policy scopes S3 to user's home directory WITHOUT session policy, user inherits FULL IAM role permissions — security risk per-user S3 scoping
Server host key generated automatically or uploaded via create-server with host-key SSH clients see a host key warning until trusted host key is distributed SSH host verification
AS2 connector trading partner certificate; local profile (private key) AS2 requires mutual certificate exchange; without partner's public cert, messages cannot be encrypted/verified B2B AS2 file exchange
Managed workflow S3 bucket for file landing; Step Functions state machine workflow steps run AFTER the file is uploaded; pre-processing steps run before the file is available to the user automated file processing pipeline

The session-policy row is the one a baseline model misses. Creating a user without a session policy means the user inherits the full IAM role permissions. If the IAM role grants broad S3 access, every SFTP user can access every bucket. The session policy is the mechanism that scopes each user to their own home directory. The endpoint-type row is another commonly misunderstood configuration — operators default to PUBLIC without considering that VPC_ENDPOINT provides private SFTP with no internet exposure.

Cross-dependency gotchas:

  • The IAM role's trust policy MUST allow transfer.amazonaws.com as principal. Without it, Transfer Family cannot assume the role on behalf of the connecting user.
  • Session policy and IAM role permissions are INTERSECTED, not unioned. The effective permissions are the INTERSECTION of the session policy and the IAM role. If either is restrictive, the effective permission is restrictive.
  • VPC_ENDPOINT type uses AWS PrivateLink. Clients connect from within the VPC or via VPC peering / Transit Gateway. No NLB is provisioned. VPC type provisions an NLB inside the VPC.
  • AS2 connectors require certificate exchange. You need the trading partner's public certificate AND your own private key pair.
  • Managed workflow steps are executed via Step Functions. The workflow must be deployed and the Transfer server must reference the workflow ID in its configuration.

Expert heuristic: session policy for per-user S3 scoping

Session-policy scoping model and full walkthrough moved verbatim to references/worked-examples.md.

Expert heuristic: managed workflow for file landing zone automation

Managed-workflow landing-zone pipeline walkthrough moved verbatim to references/worked-examples.md.

Expert heuristic: VPC endpoint for private SFTP

A baseline model uses a PUBLIC endpoint. The correct heuristic recognizes that VPC_ENDPOINT provides private SFTP with zero internet exposure.

Endpoint type decision tree:
  ├── B2B with external partners → PUBLIC endpoint (internet-facing)
  │     + service-managed or custom Lambda IDP
  │     + restrict by IP in security group (if partner IPs are known)
  ├── Internal users, within VPC → VPC_ENDPOINT (PrivateLink)
  │     + no internet exposure; clients connect via VPC internals
  │     + requires VPC with DNS resolution
  │     + accessible via VPC peering, TGW, VPN, DX
  └── Internal users, need NLB features → VPC (NLB-based)
        + full NLB control (cross-zone, DNS, health checks)
        + more expensive (NLB hourly + data processing)
        + use when you need NLB-specific features

Key: VPC_ENDPOINT is preferred for private SFTP because it uses
PrivateLink (no NLB cost) and provides a private IP within the VPC.

Key implication: VPC_ENDPOINT is the recommended endpoint type for internal file transfers. It provides a private SFTP endpoint without exposing the server to the internet and without the cost of an NLB.

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
S3 bucket exists Users need an S3 bucket for home directory aws s3 ls s3://<bucket>
IAM role for Transfer Family Server needs a logging role; users need an access role aws iam get-role --role-name <name>
IAM role trust policy Must allow transfer.amazonaws.com as principal Check trust policy document
VPC and subnets (for VPC/VPC_ENDPOINT) Private endpoints need VPC infrastructure aws ec2 describe-subnets
Security group (for VPC/VPC_ENDPOINT) Controls inbound traffic to the endpoint aws ec2 describe-security-groups
Route 53 hosted zone (for custom DNS) Optional: custom hostname for the server aws route53 list-hosted-zones
Lambda function (for custom IDP) Custom identity provider needs a Lambda function aws lambda get-function --function-name <name>
SSL/TLS certificate (for FTPS) FTPS requires a certificate aws acm describe-certificate --certificate-arn <arn>
Trading partner certificate (for AS2) AS2 requires the partner's public certificate Confirm certificate availability

If any prerequisite is missing, output VERDICT: PREREQUISITES_MISSING and cite the specific gap.

Step 1 — Server model and protocols

Transfer Family provides managed file transfer servers supporting SFTP, FTPS, and FTP protocols.

Protocol Port Encryption Authentication Use case
SFTP 22 SSH-based SSH key (service-managed), password (DS/Lambda) B2B, partner integration
FTPS 990 TLS Password (DS/Lambda) Compliance (explicit TLS)
FTP 21 None Password (DS/Lambda) Legacy (VPC-only)

FTP requires VPC or VPC_ENDPOINT — it is NOT available on PUBLIC endpoints (no encryption). FTPS requires an ACM or imported certificate.

A single server supports ONE protocol family. For SFTP + FTPS, create two servers.

Step 2 — Identity provider (service-managed, DS, Lambda)

Provider How it works Best for
Service-managed SSH keys stored in Transfer Family Simple SFTP with known users
AWS Directory Service Integrates with AWS Managed AD Enterprise AD integration
Custom (Lambda) Lambda function validates credentials Custom auth, MFA, external IdP

Service-managed: store each user's public SSH key via create-user with SshPublicKeys. Transfer Family validates the SSH key against the connecting user.

Custom Lambda: deploy a Lambda function that receives the username and password (or SSH key) and returns the user's S3 home directory, IAM role, and session policy. This enables integration with any external identity provider (Okta, Auth0, Active Directory via LDAP, database lookup).

Step 3 — Endpoint type (PUBLIC, VPC, VPC_ENDPOINT)

Type Accessibility Cost Network Use case
PUBLIC Internet-facing Server only Direct internet B2B partner access
VPC VPC-internal via NLB Server + NLB NLB in your VPC Internal with NLB features
VPC_ENDPOINT VPC-internal via PrivateLink Server only PrivateLink endpoint Private SFTP (recommended)

VPC_ENDPOINT uses AWS PrivateLink. No NLB is provisioned. The server is accessible via a private IP in your VPC. Clients connect from within the VPC, via VPC peering, Transit Gateway, VPN, or Direct Connect.

Step 4 — VPC, subnets, security groups

For VPC and VPC_ENDPOINT types, specify subnets and security groups:

The create-server VPC_ENDPOINT CLI example moved verbatim to references/worked-examples.md.

Security group rules: allow inbound TCP 22 (SFTP) from the expected client CIDR ranges. For VPC_ENDPOINT, the security group is attached to the VPC endpoint network interface.

Step 5 — Route 53 hosted zone DNS

To use a custom hostname (e.g., sftp.example.com), create a Route 53 record pointing to the server endpoint:

The Route 53 CNAME CLI sequence moved verbatim to references/worked-examples.md.

Step 6 — User home directory mapping

Mapping type How it works Flexibility
Physical (HomeDirectoryType=PATH) Direct S3 path: /bucket/home/alice One directory per user
Logical (HomeDirectoryType=LOGICAL) Virtual paths mapped to real S3 paths Multiple directories, chroot-like

Logical mapping uses HomeDirectoryDetails to map virtual paths to real S3 paths:

The logical home-directory-mapping CLI example moved verbatim to references/worked-examples.md.

Alice sees /uploads and /downloads as top-level directories, but they map to different S3 buckets.

Step 7 — IAM role and session policy

The IAM role is assumed BY Transfer Family on behalf of the user. The session policy scopes the role to the user's home directory.

Trust policy JSON, session policy JSON, and create-user CLI moved verbatim to references/worked-examples.md.

Critical: the session policy INTERSECTS with the IAM role. The effective permissions are the intersection of both. If the IAM role does not grant S3 access, the session policy cannot add it.

Step 8 — Server host key and trusted host keys

The server host key identifies the Transfer Family server to SSH clients. Transfer Family generates one automatically, but you can upload a custom host key for brand consistency or compliance.

The custom host-key CLI example moved verbatim to references/worked-examples.md.

Trusted host keys are used by clients to verify the server. When a client connects, SSH compares the server's host key against its known_hosts entry. Distribute the host key to clients via a secure channel.

Step 9 — AS2 connectors

AS2 (Applicability Statement 2) is a B2B file transfer protocol for EDI (Electronic Data Interchange) trading partner exchange.

The AS2 create-connector CLI example moved verbatim to references/worked-examples.md.

AS2 requires certificate exchange: you need the partner's public certificate (for encryption) and your own private key (for signing). Certificates are managed via Transfer Family profiles.

Step 10 — Managed workflows

Managed workflows automate file processing via Step Functions. Each file upload triggers the workflow.

The create-workflow and update-server CLI sequences moved verbatim to references/worked-examples.md.

Every file upload now triggers the workflow: copy to the data lake, tag as processed, and on exception tag as failed.

Step 11 — Structured JSON logging and CloudWatch

Transfer Family supports structured JSON logging to CloudWatch Logs. Each connection, authentication, and file transfer is logged.

The structured-logging CLI example moved verbatim to references/worked-examples.md.

Structured logs include connection timestamp, client IP, username, authentication result, file transfer details, and session duration.

Step 12 — Throttling and limits

Limit Default Adjustable
Files per second (per server) 100 Yes (support ticket)
Concurrent connections 10,000 Yes
Users per server 10,000 (service-managed) Yes
File size 5 GB max (S3 limit) No
Workflows per server 1 No

CloudWatch metrics (FilesIn, FilesOut, BytesIn, BytesOut) provide throughput visibility.

Step 13 — Recent features

The 2023-2026 feature timeline moved verbatim to references/advanced-patterns.md.

NEVER do these things

  1. NEVER create a Transfer Family user without a session policy. Without a session policy, the user inherits the FULL IAM role permissions. If the role grants broad S3 access, every SFTP user can access every bucket. ALWAYS attach a session policy that scopes the user to their home directory.

  2. NEVER use a PUBLIC endpoint for internal file transfers. PUBLIC endpoints expose the SFTP server to the entire internet. For internal transfers, use VPC_ENDPOINT (PrivateLink, recommended) or VPC (NLB-based).

  3. NEVER assume the IAM role alone provides per-user scoping. The IAM role defines MAXIMUM permissions. The session policy provides EFFECTIVE per-user scoping. Both are required.

  4. NEVER deploy an SFTP server without a server host key strategy. SSH clients will see a host key warning on first connection if the key is not distributed via a trusted channel. Upload a custom host key for brand consistency and distribute it to clients.

  5. NEVER forget the IAM role trust policy. The role assumed by Transfer Family on behalf of users MUST have a trust policy allowing transfer.amazonaws.com. Without it, the role cannot be assumed and users cannot connect.

  6. NEVER create a managed workflow without on-exception steps. If a workflow step fails and there are no on-exception steps, the file is left in an indeterminate state. Always define cleanup or notification steps for exceptions.

  7. NEVER use FTP on a PUBLIC endpoint. FTP sends credentials in plaintext. FTP is ONLY available on VPC and VPC_ENDPOINT types. For external partners, use SFTP or FTPS.

  8. NEVER assume logical home directory mapping is chroot. Logical mapping provides virtual paths but does NOT prevent a user from navigating to other paths if the session policy permits. The session policy is the security boundary, not the home directory mapping.

  9. NEVER deploy AS2 connectors without certificate verification. AS2 requires mutual certificate exchange. Verify the trading partner's certificate fingerprint before configuring the connector.

  10. NEVER ignore Transfer Family CloudWatch metrics. Monitor FilesIn, FilesOut, BytesIn, BytesOut, and authentication failure rates. Sudden spikes or drops indicate issues with partner connectivity or automated processes.

Output format

TRANSFER_FAMILY: <server-id> (<protocols>) — <endpoint-type>
VERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING
CHECKLIST:
  [✓|✗] Server: <server-id> (<protocol: SFTP|FTPS|FTP>)
  [✓|✗] Endpoint type: PUBLIC | VPC | VPC_ENDPOINT
  [✓|✗] Identity provider: Service-managed | Directory Service | Custom Lambda
  [✓|✗] VPC: <vpc-id> (subnets: <subnet-list>) | N/A (PUBLIC)
  [✓|✗] Security groups: <sg-list> | N/A (PUBLIC)
  [✓|✗] Route 53: <hostname> → <endpoint> | N/A
  [✓|✗] S3 bucket: <bucket-name>
  [✓|✗] Users: <user-list> (home directory: <mapping-type>)
  [✓|✗] IAM role: <role-name> (trust: transfer.amazonaws.com)
  [✓|✗] Session policy: attached per-user (S3 scoped) | MISSING (RISK)
  [✓|✗] Server host key: custom | auto-generated
  [✓|✗] Managed workflow: <workflow-id> (<steps>) | none
  [✓|✗] AS2 connector: <connector-id> (<partner>) | N/A
  [✓|✗] Structured logging: CloudWatch <log-group> | disabled
  [✓|✗] Tags: <key=value list>
VERIFICATION_COMMANDS:
  aws transfer describe-server --server-id <server-id>
  aws transfer list-users --server-id <server-id>
  aws transfer describe-workflow --workflow-id <workflow-id>

Worked example — SFTP with VPC_ENDPOINT, custom Lambda, and managed workflow

TRANSFER_FAMILY: s-abc123 (SFTP) — VPC_ENDPOINT
VERDICT: READY_TO_DEPLOY
CHECKLIST:
  [✓] Server: s-abc123 (SFTP)
  [✓] Endpoint type: VPC_ENDPOINT (PrivateLink)
  [✓] Identity provider: Custom Lambda (transfer-idp-auth)
  [✓] VPC: vpc-aaa11122 (subnets: subnet-aaa, subnet-bbb)
  [✓] Security groups: sg-sftp-internal
  [✓] Route 53: sftp.internal.example.com → vpce-xxx
  [✓] S3 bucket: file-landing-zone
  [✓] Users: alice, bob, carol (home directory: LOGICAL)
  [✓] IAM role: TransferFamilyS3Access (trust: transfer.amazonaws.com)
  [✓] Session policy: attached per-user (scoped to /home/<user>/*)
  [✓] Server host key: custom (RSA 4096)
  [✓] Managed workflow: w-def456 (COPY → TAG → CUSTOM Lambda scan)
  [✓] AS2 connector: N/A
  [✓] Structured logging: CloudWatch /aws/transfer/sftp
  [✓] Tags: Environment=production, App=file-landing-zone
VERIFICATION_COMMANDS:
  aws transfer describe-server --server-id s-abc123
  aws transfer list-users --server-id s-abc123
  aws transfer describe-workflow --workflow-id w-def456

Error handling

All five failure-mode playbooks moved verbatim to references/error-handling.md.

References (load on demand)

Domain

AWS CloudOps / AWS Transfer Family Managed File Transfer & Automation.

AWS documentation

04 同仓库更多 Skills

jhkchan
jhkchan/aws-agent-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.

★ 4
jhkchan
jhkchan/aws-agent-skills

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.

★ 4
jhkchan
jhkchan/aws-agent-skills

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.

★ 4
jhkchan
jhkchan/aws-agent-skills

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.

★ 4
jhkchan
jhkchan/aws-agent-skills

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.

★ 4
jhkchan
jhkchan/aws-agent-skills

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.

★ 4