[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ADE7MWK6RCG136N2DY1YS0":3,"skill-same:01M7ADE7MWK6RCG136N2DY1YS0":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},"01M7ADE7MWK6RCG136N2DY1YS0","transfer-family-workflow-deployer",null,"Provisions AWS Transfer Family servers and managed workflows with production defaults: SFTP\u002FFTPS\u002FFTP 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.","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\u002Ftransfer-family-workflow-deployer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: transfer-family-workflow-deployer\ndescription: 'Provisions AWS Transfer Family servers and managed workflows with production defaults: SFTP\u002FFTPS\u002FFTP 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.'\nlicense: Apache-2.0\ncompatibility: '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 \u002F aws_transfer_user \u002F aws_transfer_workflow resources and CloudFormation AWS::Transfer::Server \u002F AWS::Transfer::User \u002F AWS::Transfer::Workflow 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: Storage\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, transfer-family, sftp, cloudops, deploy, storage, provisioning, managed-file-transfer, session-policy, as2, managed-workflow, vpc-endpoint\n  dependencies: aws-orchestrator\n  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\n  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.\n---\n\n# Transfer Family Workflow Deployer\n\nAn AWS CloudOps agent skill that provisions AWS Transfer Family\nservers and managed workflows with correct defaults. The skill walks\nthe operator through protocol selection (SFTP\u002FFTPS\u002FFTP), identity\nprovider choice (service-managed, Directory Service, custom Lambda),\nendpoint type (PUBLIC, VPC, VPC_ENDPOINT), VPC and security group\nconfiguration, Route 53 hosted zone DNS, user home directory mapping\n(logical vs physical), per-user S3 access via IAM role and session\npolicy, AS2 connectors for trading partner exchange, managed workflow\nwith Step Functions for file landing zone automation, structured JSON\nlogging, CloudWatch metrics and throttling, server host key generation,\nand trusted host keys for partner verification, captures architecture\ndecisions, explains why each default matters, and emits a\nREADY_TO_DEPLOY checklist with copy-pasteable verification commands.\n\n## Activation keywords\n\ncreate Transfer Family SFTP server, Transfer Family custom Lambda\nidentity, Transfer Family VPC endpoint, Transfer Family managed\nworkflow, Transfer Family AS2 connector, SFTP user session policy,\nTransfer Family hosted zone Route 53, SFTP home directory mapping,\nTransfer Family server host key, Transfer Family trusted host keys.\n\n## STRICT output contract\n\nWhen this skill is invoked with a Transfer-Family-provisioning request\n(create a server, configure identity provider, set up VPC endpoint,\ndeploy managed workflow, configure AS2 connector, or a partial\nconfiguration), the agent MUST respond with the READY_TO_DEPLOY\nchecklist defined in the \"Output format\" section using the literal\nall-caps labels `TRANSFER_FAMILY:`, `VERDICT:`, `CHECKLIST:`, and\n`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 — Server model and protocols | Core Transfer Family model |\n| Step 2 — Identity provider (service-managed, DS, Lambda) | Authentication |\n| Step 3 — Endpoint type (PUBLIC, VPC, VPC_ENDPOINT) | Network placement |\n| Step 4 — VPC, subnets, security groups | Private connectivity |\n| Step 5 — Route 53 hosted zone DNS | Custom hostname |\n| Step 6 — User home directory mapping | S3 path mapping |\n| Step 7 — IAM role and session policy | Per-user S3 scoping |\n| Step 8 — Server host key and trusted host keys | SSH key management |\n| Step 9 — AS2 connectors | B2B trading partner exchange |\n| Step 10 — Managed workflows | File landing zone automation |\n| Step 11 — Structured JSON logging and CloudWatch | Observability |\n| Step 12 — Throttling and limits | Performance |\n| Step 13 — Recent features | Latest |\n| NEVER do these things | Review before signing off |\n| Output format | The literal checklist template |\n| references\u002Fidentity-providers-and-endpoints.md | IDP + endpoint detail |\n| references\u002Fmanaged-workflows-and-as2.md | Workflow + AS2 detail |\n\n## Mindset\n\n**One-line takeaway:** AWS Transfer Family is a managed SFTP\u002FFTPS\u002FFTP\nserver that bridges legacy file transfer protocols with AWS S3 (and\nEFS). Users authenticate via service-managed SSH keys, AWS Directory\nService, or a custom Lambda identity provider. Each user is scoped to\nspecific S3 paths via a session policy applied at connection time.\nManaged workflows automate pre\u002Fpost file processing via Step Functions.\n\nThree misconceptions dominate Transfer Family misdesign at provisioning\ntime:\n\n- **\"Public endpoint with service-managed auth is fine for production.\"**\n  For B2B or internal file transfers, a PUBLIC endpoint exposes the\n  SFTP server to the entire internet. VPC or VPC_ENDPOINT provides\n  private connectivity. Combined with a custom Lambda identity\n  provider, this gives enterprise-grade access control including MFA,\n  credential brokering, and audit trails.\n\n- **\"The IAM role's S3 permissions are sufficient.\"** They are not. The\n  IAM role defines the MAXIMUM permissions, but the session policy\n  defines the EFFECTIVE per-user scope. A user with an IAM role that\n  grants `s3:*` on `*` but a session policy that restricts to\n  `s3:GetObject` on `my-bucket\u002Fhome\u002Falice\u002F*` can only read their own\n  directory. Without a session policy, the user inherits the full IAM\n  role permissions — a security risk.\n\n- **\"Managed workflows are optional post-processing.\"** They are the\n  core value of a file landing zone. Without a managed workflow, files\n  land in S3 and sit there. A managed workflow with Step Functions can\n  trigger virus scanning, format validation, transformation, and\n  routing on every upload — turning SFTP from a passive file store\n  into an active data pipeline.\n\n## Configuration dependency graph (novel heuristic)\n\nTransfer Family configurations are NOT independent. The endpoint type\ndetermines whether VPC subnets and security groups are required. The\nidentity provider determines whether a Lambda function needs to be\ndeployed. The session policy must reference S3 paths that match the\nuser's home directory mapping. Use this graph to sequence provisioning.\n\n| Configuration | Hard dependencies (API error without) | Silent failure \u002F immutability | Enables downstream |\n|---|---|---|---|\n| Transfer server | IAM role for logging; S3 bucket exists | server creation succeeds but USERS cannot connect until identity provider is configured | SFTP\u002FFTPS\u002FFTP endpoint |\n| 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 |\n| 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 |\n| Endpoint type — VPC_ENDPOINT | VPC ID, subnet IDs, security group IDs | uses PrivateLink (no NLB); clients connect from within the VPC or via peering\u002FTGW | private SFTP via PrivateLink |\n| User home directory | S3 bucket exists; logical mapping if `HomeDirectoryType=LOGICAL` | physical mapping uses `HomeDirectory=\u002Fbucket\u002Fpath`; logical mapping uses `HomeDirectoryDetails` with entry\u002F target pairs | per-user S3 path |\n| IAM role (user) | trust policy allowing `transfer.amazonaws.com`; S3 permissions | without S3 permissions, user authenticates but CANNOT read\u002Fwrite files | S3 access for the user |\n| 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 |\n| 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 |\n| AS2 connector | trading partner certificate; local profile (private key) | AS2 requires mutual certificate exchange; without partner's public cert, messages cannot be encrypted\u002Fverified | B2B AS2 file exchange |\n| 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 |\n\n**The session-policy row is the one a baseline model misses.** Creating\na user without a session policy means the user inherits the full IAM\nrole permissions. If the IAM role grants broad S3 access, every SFTP\nuser can access every bucket. The session policy is the mechanism that\nscopes each user to their own home directory. The endpoint-type row is\nanother commonly misunderstood configuration — operators default to\nPUBLIC without considering that VPC_ENDPOINT provides private SFTP with\nno internet exposure.\n\n**Cross-dependency gotchas:**\n- The IAM role's trust policy MUST allow `transfer.amazonaws.com` as\n  principal. Without it, Transfer Family cannot assume the role on\n  behalf of the connecting user.\n- Session policy and IAM role permissions are INTERSECTED, not unioned.\n  The effective permissions are the INTERSECTION of the session policy\n  and the IAM role. If either is restrictive, the effective permission\n  is restrictive.\n- VPC_ENDPOINT type uses AWS PrivateLink. Clients connect from within\n  the VPC or via VPC peering \u002F Transit Gateway. No NLB is provisioned.\n  VPC type provisions an NLB inside the VPC.\n- AS2 connectors require certificate exchange. You need the trading\n  partner's public certificate AND your own private key pair.\n- Managed workflow steps are executed via Step Functions. The workflow\n  must be deployed and the Transfer server must reference the workflow\n  ID in its configuration.\n\n## Expert heuristic: session policy for per-user S3 scoping\n\nSession-policy scoping model and full walkthrough moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\n\n## Expert heuristic: managed workflow for file landing zone automation\n\nManaged-workflow landing-zone pipeline walkthrough moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\n\n## Expert heuristic: VPC endpoint for private SFTP\n\nA baseline model uses a PUBLIC endpoint. The correct heuristic\nrecognizes that VPC_ENDPOINT provides private SFTP with zero internet\nexposure.\n\n```text\nEndpoint type decision tree:\n  ├── B2B with external partners → PUBLIC endpoint (internet-facing)\n  │     + service-managed or custom Lambda IDP\n  │     + restrict by IP in security group (if partner IPs are known)\n  ├── Internal users, within VPC → VPC_ENDPOINT (PrivateLink)\n  │     + no internet exposure; clients connect via VPC internals\n  │     + requires VPC with DNS resolution\n  │     + accessible via VPC peering, TGW, VPN, DX\n  └── Internal users, need NLB features → VPC (NLB-based)\n        + full NLB control (cross-zone, DNS, health checks)\n        + more expensive (NLB hourly + data processing)\n        + use when you need NLB-specific features\n\nKey: VPC_ENDPOINT is preferred for private SFTP because it uses\nPrivateLink (no NLB cost) and provides a private IP within the VPC.\n```\n\n**Key implication:** VPC_ENDPOINT is the recommended endpoint type for\ninternal file transfers. It provides a private SFTP endpoint without\nexposing the server to the internet and without the cost of an NLB.\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| S3 bucket exists | Users need an S3 bucket for home directory | `aws s3 ls s3:\u002F\u002F\u003Cbucket>` |\n| IAM role for Transfer Family | Server needs a logging role; users need an access role | `aws iam get-role --role-name \u003Cname>` |\n| IAM role trust policy | Must allow `transfer.amazonaws.com` as principal | Check trust policy document |\n| VPC and subnets (for VPC\u002FVPC_ENDPOINT) | Private endpoints need VPC infrastructure | `aws ec2 describe-subnets` |\n| Security group (for VPC\u002FVPC_ENDPOINT) | Controls inbound traffic to the endpoint | `aws ec2 describe-security-groups` |\n| Route 53 hosted zone (for custom DNS) | Optional: custom hostname for the server | `aws route53 list-hosted-zones` |\n| Lambda function (for custom IDP) | Custom identity provider needs a Lambda function | `aws lambda get-function --function-name \u003Cname>` |\n| SSL\u002FTLS certificate (for FTPS) | FTPS requires a certificate | `aws acm describe-certificate --certificate-arn \u003Carn>` |\n| Trading partner certificate (for AS2) | AS2 requires the partner's public certificate | Confirm certificate availability |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING`\nand cite the specific gap.\n\n## Step 1 — Server model and protocols\n\nTransfer Family provides managed file transfer servers supporting\nSFTP, FTPS, and FTP protocols.\n\n| Protocol | Port | Encryption | Authentication | Use case |\n|---|---|---|---|---|\n| SFTP | 22 | SSH-based | SSH key (service-managed), password (DS\u002FLambda) | B2B, partner integration |\n| FTPS | 990 | TLS | Password (DS\u002FLambda) | Compliance (explicit TLS) |\n| FTP | 21 | None | Password (DS\u002FLambda) | Legacy (VPC-only) |\n\n**FTP requires VPC or VPC_ENDPOINT** — it is NOT available on PUBLIC\nendpoints (no encryption). FTPS requires an ACM or imported certificate.\n\nA single server supports ONE protocol family. For SFTP + FTPS, create\ntwo servers.\n\n## Step 2 — Identity provider (service-managed, DS, Lambda)\n\n| Provider | How it works | Best for |\n|---|---|---|\n| Service-managed | SSH keys stored in Transfer Family | Simple SFTP with known users |\n| AWS Directory Service | Integrates with AWS Managed AD | Enterprise AD integration |\n| Custom (Lambda) | Lambda function validates credentials | Custom auth, MFA, external IdP |\n\n**Service-managed:** store each user's public SSH key via `create-user`\nwith `SshPublicKeys`. Transfer Family validates the SSH key against the\nconnecting user.\n\n**Custom Lambda:** deploy a Lambda function that receives the username\nand password (or SSH key) and returns the user's S3 home directory, IAM\nrole, and session policy. This enables integration with any external\nidentity provider (Okta, Auth0, Active Directory via LDAP, database\nlookup).\n\n## Step 3 — Endpoint type (PUBLIC, VPC, VPC_ENDPOINT)\n\n| Type | Accessibility | Cost | Network | Use case |\n|---|---|---|---|---|\n| PUBLIC | Internet-facing | Server only | Direct internet | B2B partner access |\n| VPC | VPC-internal via NLB | Server + NLB | NLB in your VPC | Internal with NLB features |\n| VPC_ENDPOINT | VPC-internal via PrivateLink | Server only | PrivateLink endpoint | Private SFTP (recommended) |\n\n**VPC_ENDPOINT** uses AWS PrivateLink. No NLB is provisioned. The\nserver is accessible via a private IP in your VPC. Clients connect\nfrom within the VPC, via VPC peering, Transit Gateway, VPN, or Direct\nConnect.\n\n## Step 4 — VPC, subnets, security groups\n\nFor VPC and VPC_ENDPOINT types, specify subnets and security groups:\n\nThe create-server VPC_ENDPOINT CLI example moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\n\n**Security group rules:** allow inbound TCP 22 (SFTP) from the\nexpected client CIDR ranges. For VPC_ENDPOINT, the security group\nis attached to the VPC endpoint network interface.\n\n## Step 5 — Route 53 hosted zone DNS\n\nTo use a custom hostname (e.g., `sftp.example.com`), create a Route 53\nrecord pointing to the server endpoint:\n\nThe Route 53 CNAME CLI sequence moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\n\n## Step 6 — User home directory mapping\n\n| Mapping type | How it works | Flexibility |\n|---|---|---|\n| Physical (`HomeDirectoryType=PATH`) | Direct S3 path: `\u002Fbucket\u002Fhome\u002Falice` | One directory per user |\n| Logical (`HomeDirectoryType=LOGICAL`) | Virtual paths mapped to real S3 paths | Multiple directories, chroot-like |\n\n**Logical mapping** uses `HomeDirectoryDetails` to map virtual paths\nto real S3 paths:\n\nThe logical home-directory-mapping CLI example moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\n\nAlice sees `\u002Fuploads` and `\u002Fdownloads` as top-level directories, but\nthey map to different S3 buckets.\n\n## Step 7 — IAM role and session policy\n\nThe IAM role is assumed BY Transfer Family on behalf of the user. The\nsession policy scopes the role to the user's home directory.\n\nTrust policy JSON, session policy JSON, and create-user CLI moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\n\n**Critical:** the session policy INTERSECTS with the IAM role. The\neffective permissions are the intersection of both. If the IAM role\ndoes not grant S3 access, the session policy cannot add it.\n\n## Step 8 — Server host key and trusted host keys\n\nThe server host key identifies the Transfer Family server to SSH\nclients. Transfer Family generates one automatically, but you can\nupload a custom host key for brand consistency or compliance.\n\nThe custom host-key CLI example moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\n\n**Trusted host keys** are used by clients to verify the server. When a\nclient connects, SSH compares the server's host key against its\nknown_hosts entry. Distribute the host key to clients via a secure channel.\n\n## Step 9 — AS2 connectors\n\nAS2 (Applicability Statement 2) is a B2B file transfer protocol for\nEDI (Electronic Data Interchange) trading partner exchange.\n\nThe AS2 create-connector CLI example moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\n\nAS2 requires certificate exchange: you need the partner's public\ncertificate (for encryption) and your own private key (for signing).\nCertificates are managed via Transfer Family profiles.\n\n## Step 10 — Managed workflows\n\nManaged workflows automate file processing via Step Functions. Each\nfile upload triggers the workflow.\n\nThe create-workflow and update-server CLI sequences moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\n\nEvery file upload now triggers the workflow: copy to the data lake,\ntag as processed, and on exception tag as failed.\n\n## Step 11 — Structured JSON logging and CloudWatch\n\nTransfer Family supports structured JSON logging to CloudWatch Logs.\nEach connection, authentication, and file transfer is logged.\n\nThe structured-logging CLI example moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\n\nStructured logs include connection timestamp, client IP, username,\nauthentication result, file transfer details, and session duration.\n\n## Step 12 — Throttling and limits\n\n| Limit | Default | Adjustable |\n|---|---|---|\n| Files per second (per server) | 100 | Yes (support ticket) |\n| Concurrent connections | 10,000 | Yes |\n| Users per server | 10,000 (service-managed) | Yes |\n| File size | 5 GB max (S3 limit) | No |\n| Workflows per server | 1 | No |\n\nCloudWatch metrics (`FilesIn`, `FilesOut`, `BytesIn`, `BytesOut`)\nprovide throughput visibility.\n\n## Step 13 — Recent features\n\nThe 2023-2026 feature timeline moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## NEVER do these things\n\n1. **NEVER create a Transfer Family user without a session policy.**\n   Without a session policy, the user inherits the FULL IAM role\n   permissions. If the role grants broad S3 access, every SFTP user\n   can access every bucket. ALWAYS attach a session policy that scopes\n   the user to their home directory.\n\n2. **NEVER use a PUBLIC endpoint for internal file transfers.** PUBLIC\n   endpoints expose the SFTP server to the entire internet. For\n   internal transfers, use VPC_ENDPOINT (PrivateLink, recommended) or\n   VPC (NLB-based).\n\n3. **NEVER assume the IAM role alone provides per-user scoping.** The\n   IAM role defines MAXIMUM permissions. The session policy provides\n   EFFECTIVE per-user scoping. Both are required.\n\n4. **NEVER deploy an SFTP server without a server host key strategy.**\n   SSH clients will see a host key warning on first connection if the\n   key is not distributed via a trusted channel. Upload a custom host\n   key for brand consistency and distribute it to clients.\n\n5. **NEVER forget the IAM role trust policy.** The role assumed by\n   Transfer Family on behalf of users MUST have a trust policy allowing\n   `transfer.amazonaws.com`. Without it, the role cannot be assumed and\n   users cannot connect.\n\n6. **NEVER create a managed workflow without on-exception steps.** If a\n   workflow step fails and there are no on-exception steps, the file is\n   left in an indeterminate state. Always define cleanup or notification\n   steps for exceptions.\n\n7. **NEVER use FTP on a PUBLIC endpoint.** FTP sends credentials in\n   plaintext. FTP is ONLY available on VPC and VPC_ENDPOINT types. For\n   external partners, use SFTP or FTPS.\n\n8. **NEVER assume logical home directory mapping is chroot.** Logical\n   mapping provides virtual paths but does NOT prevent a user from\n   navigating to other paths if the session policy permits. The session\n   policy is the security boundary, not the home directory mapping.\n\n9. **NEVER deploy AS2 connectors without certificate verification.** AS2\n   requires mutual certificate exchange. Verify the trading partner's\n   certificate fingerprint before configuring the connector.\n\n10. **NEVER ignore Transfer Family CloudWatch metrics.** Monitor\n    `FilesIn`, `FilesOut`, `BytesIn`, `BytesOut`, and authentication\n    failure rates. Sudden spikes or drops indicate issues with partner\n    connectivity or automated processes.\n\n## Output format\n\n```text\nTRANSFER_FAMILY: \u003Cserver-id> (\u003Cprotocols>) — \u003Cendpoint-type>\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Server: \u003Cserver-id> (\u003Cprotocol: SFTP|FTPS|FTP>)\n  [✓|✗] Endpoint type: PUBLIC | VPC | VPC_ENDPOINT\n  [✓|✗] Identity provider: Service-managed | Directory Service | Custom Lambda\n  [✓|✗] VPC: \u003Cvpc-id> (subnets: \u003Csubnet-list>) | N\u002FA (PUBLIC)\n  [✓|✗] Security groups: \u003Csg-list> | N\u002FA (PUBLIC)\n  [✓|✗] Route 53: \u003Chostname> → \u003Cendpoint> | N\u002FA\n  [✓|✗] S3 bucket: \u003Cbucket-name>\n  [✓|✗] Users: \u003Cuser-list> (home directory: \u003Cmapping-type>)\n  [✓|✗] IAM role: \u003Crole-name> (trust: transfer.amazonaws.com)\n  [✓|✗] Session policy: attached per-user (S3 scoped) | MISSING (RISK)\n  [✓|✗] Server host key: custom | auto-generated\n  [✓|✗] Managed workflow: \u003Cworkflow-id> (\u003Csteps>) | none\n  [✓|✗] AS2 connector: \u003Cconnector-id> (\u003Cpartner>) | N\u002FA\n  [✓|✗] Structured logging: CloudWatch \u003Clog-group> | disabled\n  [✓|✗] Tags: \u003Ckey=value list>\nVERIFICATION_COMMANDS:\n  aws transfer describe-server --server-id \u003Cserver-id>\n  aws transfer list-users --server-id \u003Cserver-id>\n  aws transfer describe-workflow --workflow-id \u003Cworkflow-id>\n```\n\n### Worked example — SFTP with VPC_ENDPOINT, custom Lambda, and managed workflow\n\n```text\nTRANSFER_FAMILY: s-abc123 (SFTP) — VPC_ENDPOINT\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Server: s-abc123 (SFTP)\n  [✓] Endpoint type: VPC_ENDPOINT (PrivateLink)\n  [✓] Identity provider: Custom Lambda (transfer-idp-auth)\n  [✓] VPC: vpc-aaa11122 (subnets: subnet-aaa, subnet-bbb)\n  [✓] Security groups: sg-sftp-internal\n  [✓] Route 53: sftp.internal.example.com → vpce-xxx\n  [✓] S3 bucket: file-landing-zone\n  [✓] Users: alice, bob, carol (home directory: LOGICAL)\n  [✓] IAM role: TransferFamilyS3Access (trust: transfer.amazonaws.com)\n  [✓] Session policy: attached per-user (scoped to \u002Fhome\u002F\u003Cuser>\u002F*)\n  [✓] Server host key: custom (RSA 4096)\n  [✓] Managed workflow: w-def456 (COPY → TAG → CUSTOM Lambda scan)\n  [✓] AS2 connector: N\u002FA\n  [✓] Structured logging: CloudWatch \u002Faws\u002Ftransfer\u002Fsftp\n  [✓] Tags: Environment=production, App=file-landing-zone\nVERIFICATION_COMMANDS:\n  aws transfer describe-server --server-id s-abc123\n  aws transfer list-users --server-id s-abc123\n  aws transfer describe-workflow --workflow-id w-def456\n```\n\n## Error handling\n\nAll five failure-mode playbooks moved verbatim to [references\u002Ferror-handling.md](references\u002Ferror-handling.md).\n\n## References (load on demand)\n\n- [references\u002Fworked-examples.md](references\u002Fworked-examples.md) — per-step CLI sequences (Steps 4-11) plus session-policy and managed-workflow heuristic walkthroughs\n- [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) — 2023-2026 recent-feature timeline\n- [references\u002Ferror-handling.md](references\u002Ferror-handling.md) — five failure-mode playbooks (auth\u002Fno-file-access, VPC_ENDPOINT timeout, workflow not triggering, AS2 delivery, Lambda auth)\n- [references\u002Fidentity-providers-and-endpoints.md](references\u002Fidentity-providers-and-endpoints.md) — identity provider and endpoint detail\n- [references\u002Fmanaged-workflows-and-as2.md](references\u002Fmanaged-workflows-and-as2.md) — managed workflow and AS2 detail\n\n## Domain\n\nAWS CloudOps \u002F AWS Transfer Family Managed File Transfer & Automation.\n\n## AWS documentation\n\n- **Transfer Family User Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Ftransfer\u002Flatest\u002Fuserguide\u002Fwhat-is-aws-transfer.html\n- **Creating a server** — https:\u002F\u002Fdocs.aws.amazon.com\u002Ftransfer\u002Flatest\u002Fuserguide\u002Fcreate-server.html\n- **Identity providers** — https:\u002F\u002Fdocs.aws.amazon.com\u002Ftransfer\u002Flatest\u002Fuserguide\u002Fauthenticating-users.html\n- **Custom Lambda IDP** — https:\u002F\u002Fdocs.aws.amazon.com\u002Ftransfer\u002Flatest\u002Fuserguide\u002Fconfiguring-custom-idp.html\n- **Session policies** — https:\u002F\u002Fdocs.aws.amazon.com\u002Ftransfer\u002Flatest\u002Fuserguide\u002Fsession-policy.html\n- **Managed workflows** — https:\u002F\u002Fdocs.aws.amazon.com\u002Ftransfer\u002Flatest\u002Fuserguide\u002Fcreate-workflow.html\n- **AS2 connectors** — https:\u002F\u002Fdocs.aws.amazon.com\u002Ftransfer\u002Flatest\u002Fuserguide\u002Fas2.html\n- **VPC endpoints** — https:\u002F\u002Fdocs.aws.amazon.com\u002Ftransfer\u002Flatest\u002Fuserguide\u002Fconfiguring-endpoints.html\n- **Structured logging** — https:\u002F\u002Fdocs.aws.amazon.com\u002Ftransfer\u002Flatest\u002Fuserguide\u002Fstructured-logging.html\n","# Transfer Family Workflow Deployer\n\nAn AWS CloudOps agent skill that provisions AWS Transfer Family\nservers and managed workflows with correct defaults. The skill walks\nthe operator through protocol selection (SFTP\u002FFTPS\u002FFTP), identity\nprovider choice (service-managed, Directory Service, custom Lambda),\nendpoint type (PUBLIC, VPC, VPC_ENDPOINT), VPC and security group\nconfiguration, Route 53 hosted zone DNS, user home directory mapping\n(logical vs physical), per-user S3 access via IAM role and session\npolicy, AS2 connectors for trading partner exchange, managed workflow\nwith Step Functions for file landing zone automation, structured JSON\nlogging, CloudWatch metrics and throttling, server host key generation,\nand trusted host keys for partner verification, captures architecture\ndecisions, explains why each default matters, and emits a\nREADY_TO_DEPLOY checklist with copy-pasteable verification commands.\n\n## Activation keywords\n\ncreate Transfer Family SFTP server, Transfer Family custom Lambda\nidentity, Transfer Family VPC endpoint, Transfer Family managed\nworkflow, Transfer Family AS2 connector, SFTP user session policy,\nTransfer Family hosted zone Route 53, SFTP home directory mapping,\nTransfer Family server host key, Transfer Family trusted host keys.\n\n## STRICT output contract\n\nWhen this skill is invoked with a Transfer-Family-provisioning request\n(create a server, configure identity provider, set up VPC endpoint,\ndeploy managed workflow, configure AS2 connector, or a partial\nconfiguration), the agent MUST respond with the READY_TO_DEPLOY\nchecklist defined in the \"Output format\" section using the literal\nall-caps labels `TRANSFER_FAMILY:`, `VERDICT:`, `CHECKLIST:`, and\n`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 — Server model and protocols | Core Transfer Family model |\n| Step 2 — Identity provider (service-managed, DS, Lambda) | Authentication |\n| Step 3 — Endpoint type (PUBLIC, VPC, VPC_ENDPOINT) | Network placement |\n| Step 4 — VPC, subnets, security groups | Private connectivity |\n| Step 5 — Route 53 hosted zone DNS | Custom hostname |\n| Step 6 — User home directory mapping | S3 path mapping |\n| Step 7 — IAM role and session policy | Per-user S3 scoping |\n| Step 8 — Server host key and trusted host keys | SSH key management |\n| Step 9 — AS2 connectors | B2B trading partner exchange |\n| Step 10 — Managed workflows | File landing zone automation |\n| Step 11 — Structured JSON logging and CloudWatch | Observability |\n| Step 12 — Throttling and limits | Performance |\n| Step 13 — Recent features | Latest |\n| NEVER do these things | Review before signing off |\n| Output format | The literal checklist template |\n| references\u002Fidentity-providers-and-endpoints.md | IDP + endpoint detail |\n| references\u002Fmanaged-workflows-and-as2.md | Workflow + AS2 detail |\n\n## Mindset\n\n**One-line takeaway:** AWS Transfer Family is a managed SFTP\u002FFTPS\u002FFTP\nserver that bridges legacy file transfer protocols with AWS S3 (and\nEFS). Users authenticate via service-managed SSH keys, AWS Directory\nService, or a custom Lambda identity provider. Each user is scoped to\nspecific S3 paths via a session policy applied at connection time.\nManaged workflows automate pre\u002Fpost file processing via Step Functions.\n\nThree misconceptions dominate Transfer Family misdesign at provisioning\ntime:\n\n- **\"Public endpoint with service-managed auth is fine for production.\"**\n  For B2B or internal file transfers, a PUBLIC endpoint exposes the\n  SFTP server to the entire internet. VPC or VPC_ENDPOINT provides\n  private connectivity. Combined with a custom Lambda identity\n  provider, this gives enterprise-grade access control including MFA,\n  credential brokering, and audit trails.\n\n- **\"The IAM role's S3 permissions are sufficient.\"** They are not. The\n  IAM role defines the MAXIMUM permissions, but the session policy\n  defines the EFFECTIVE per-user scope. A user with an IAM role that\n  grants `s3:*` on `*` but a session policy that restricts to\n  `s3:GetObject` on `my-bucket\u002Fhome\u002Falice\u002F*` can only read their own\n  directory. Without a session policy, the user inherits the full IAM\n  role permissions — a security risk.\n\n- **\"Managed workflows are optional post-processing.\"** They are the\n  core value of a file landing zone. Without a managed workflow, files\n  land in S3 and sit there. A managed workflow with Step Functions can\n  trigger virus scanning, format validation, transformation, and\n  routing on every upload — turning SFTP from a passive file store\n  into an active data pipeline.\n\n## Configuration dependency graph (novel heuristic)\n\nTransfer Family configurations are NOT independent. The endpoint type\ndetermines whether VPC subnets and security groups are required. The\nidentity provider determines whether a Lambda function needs to be\ndeployed. The session policy must reference S3 paths that match the\nuser's home directory mapping. Use this graph to sequence provisioning.\n\n| Configuration | Hard dependencies (API error without) | Silent failure \u002F immutability | Enables downstream |\n|---|---|---|---|\n| Transfer server | IAM role for logging; S3 bucket exists | server creation succeeds but USERS cannot connect until identity provider is configured | SFTP\u002FFTPS\u002FFTP endpoint |\n| 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 |\n| 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 |\n| Endpoint type — VPC_ENDPOINT | VPC ID, subnet IDs, security group IDs | uses PrivateLink (no NLB); clients connect from within the VPC or via peering\u002FTGW | private SFTP via PrivateLink |\n| User home directory | S3 bucket exists; logical mapping if `HomeDirectoryType=LOGICAL` | physical mapping uses `HomeDirectory=\u002Fbucket\u002Fpath`; logical mapping uses `HomeDirectoryDetails` with entry\u002F target pairs | per-user S3 path |\n| IAM role (user) | trust policy allowing `transfer.amazonaws.com`; S3 permissions | without S3 permissions, user authenticates but CANNOT read\u002Fwrite files | S3 access for the user |\n| 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 |\n| 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 |\n| AS2 connector | trading partner certificate; local profile (private key) | AS2 requires mutual certificate exchange; without partner's public cert, messages cannot be encrypted\u002Fverified | B2B AS2 file exchange |\n| 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 |\n\n**The session-policy row is the one a baseline model misses.** Creating\na user without a session policy means the user inherits the full IAM\nrole permissions. If the IAM role grants broad S3 access, every SFTP\nuser can access every bucket. The session policy is the mechanism that\nscopes each user to their own home directory. The endpoint-type row is\nanother commonly misunderstood configuration — operators default to\nPUBLIC without considering that VPC_ENDPOINT provides private SFTP with\nno internet exposure.\n\n**Cross-dependency gotchas:**\n- The IAM role's trust policy MUST allow `transfer.amazonaws.com` as\n  principal. Without it, Transfer Family cannot assume the role on\n  behalf of the connecting user.\n- Session policy and IAM role permissions are INTERSECTED, not unioned.\n  The effective permissions are the INTERSECTION of the session policy\n  and the IAM role. If either is restrictive, the effective permission\n  is restrictive.\n- VPC_ENDPOINT type uses AWS PrivateLink. Clients connect from within\n  the VPC or via VPC peering \u002F Transit Gateway. No NLB is provisioned.\n  VPC type provisions an NLB inside the VPC.\n- AS2 connectors require certificate exchange. You need the trading\n  partner's public certificate AND your own private key pair.\n- Managed workflow steps are executed via Step Functions. The workflow\n  must be deployed and the Transfer server must reference the workflow\n  ID in its configuration.\n\n## Expert heuristic: session policy for per-user S3 scoping\n\nSession-policy scoping model and full walkthrough moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\n\n## Expert heuristic: managed workflow for file landing zone automation\n\nManaged-workflow landing-zone pipeline walkthrough moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\n\n## Expert heuristic: VPC endpoint for private SFTP\n\nA baseline model uses a PUBLIC endpoint. The correct heuristic\nrecognizes that VPC_ENDPOINT provides private SFTP with zero internet\nexposure.\n\n```text\nEndpoint type decision tree:\n  ├── B2B with external partners → PUBLIC endpoint (internet-facing)\n  │     + service-managed or custom Lambda IDP\n  │     + restrict by IP in security group (if partner IPs are known)\n  ├── Internal users, within VPC → VPC_ENDPOINT (PrivateLink)\n  │     + no internet exposure; clients connect via VPC internals\n  │     + requires VPC with DNS resolution\n  │     + accessible via VPC peering, TGW, VPN, DX\n  └── Internal users, need NLB features → VPC (NLB-based)\n        + full NLB control (cross-zone, DNS, health checks)\n        + more expensive (NLB hourly + data processing)\n        + use when you need NLB-specific features\n\nKey: VPC_ENDPOINT is preferred for private SFTP because it uses\nPrivateLink (no NLB cost) and provides a private IP within the VPC.\n```\n\n**Key implication:** VPC_ENDPOINT is the recommended endpoint type for\ninternal file transfers. It provides a private SFTP endpoint without\nexposing the server to the internet and without the cost of an NLB.\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| S3 bucket exists | Users need an S3 bucket for home directory | `aws s3 ls s3:\u002F\u002F\u003Cbucket>` |\n| IAM role for Transfer Family | Server needs a logging role; users need an access role | `aws iam get-role --role-name \u003Cname>` |\n| IAM role trust policy | Must allow `transfer.amazonaws.com` as principal | Check trust policy document |\n| VPC and subnets (for VPC\u002FVPC_ENDPOINT) | Private endpoints need VPC infrastructure | `aws ec2 describe-subnets` |\n| Security group (for VPC\u002FVPC_ENDPOINT) | Controls inbound traffic to the endpoint | `aws ec2 describe-security-groups` |\n| Route 53 hosted zone (for custom DNS) | Optional: custom hostname for the server | `aws route53 list-hosted-zones` |\n| Lambda function (for custom IDP) | Custom identity provider needs a Lambda function | `aws lambda get-function --function-name \u003Cname>` |\n| SSL\u002FTLS certificate (for FTPS) | FTPS requires a certificate | `aws acm describe-certificate --certificate-arn \u003Carn>` |\n| Trading partner certificate (for AS2) | AS2 requires the partner's public certificate | Confirm certificate availability |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING`\nand cite the specific gap.\n\n## Step 1 — Server model and protocols\n\nTransfer Family provides managed file transfer servers supporting\nSFTP, FTPS, and FTP protocols.\n\n| Protocol | Port | Encryption | Authentication | Use case |\n|---|---|---|---|---|\n| SFTP | 22 | SSH-based | SSH key (service-managed), password (DS\u002FLambda) | B2B, partner integration |\n| FTPS | 990 | TLS | Password (DS\u002FLambda) | Compliance (explicit TLS) |\n| FTP | 21 | None | Password (DS\u002FLambda) | Legacy (VPC-only) |\n\n**FTP requires VPC or VPC_ENDPOINT** — it is NOT available on PUBLIC\nendpoints (no encryption). FTPS requires an ACM or imported certificate.\n\nA single server supports ONE protocol family. For SFTP + FTPS, create\ntwo servers.\n\n## Step 2 — Identity provider (service-managed, DS, Lambda)\n\n| Provider | How it works | Best for |\n|---|---|---|\n| Service-managed | SSH keys stored in Transfer Family | Simple SFTP with known users |\n| AWS Directory Service | Integrates with AWS Managed AD | Enterprise AD integration |\n| Custom (Lambda) | Lambda function validates credentials | Custom auth, MFA, external IdP |\n\n**Service-managed:** store each user's public SSH key via `create-user`\nwith `SshPublicKeys`. Transfer Family validates the SSH key against the\nconnecting user.\n\n**Custom Lambda:** deploy a Lambda function that receives the username\nand password (or SSH key) and returns the user's S3 home directory, IAM\nrole, and session policy. This enables integration with any external\nidentity provider (Okta, Auth0, Active Directory via LDAP, database\nlookup).\n\n## Step 3 — Endpoint type (PUBLIC, VPC, VPC_ENDPOINT)\n\n| Type | Accessibility | Cost | Network | Use case |\n|---|---|---|---|---|\n| PUBLIC | Internet-facing | Server only | Direct internet | B2B partner access |\n| VPC | VPC-internal via NLB | Server + NLB | NLB in your VPC | Internal with NLB features |\n| VPC_ENDPOINT | VPC-internal via PrivateLink | Server only | PrivateLink endpoint | Private SFTP (recommended) |\n\n**VPC_ENDPOINT** uses AWS PrivateLink. No NLB is provisioned. The\nserver is accessible via a private IP in your VPC. Clients connect\nfrom within the VPC, via VPC peering, Transit Gateway, VPN, or Direct\nConnect.\n\n## Step 4 — VPC, subnets, security groups\n\nFor VPC and VPC_ENDPOINT types, specify subnets and security groups:\n\nThe create-server VPC_ENDPOINT CLI example moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\n\n**Security group rules:** allow inbound TCP 22 (SFTP) from the\nexpected client CIDR ranges. For VPC_ENDPOINT, the security group\nis attached to the VPC endpoint network interface.\n\n## Step 5 — Route 53 hosted zone DNS\n\nTo use a custom hostname (e.g., `sftp.example.com`), create a Route 53\nrecord pointing to the server endpoint:\n\nThe Route 53 CNAME CLI sequence moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\n\n## Step 6 — User home directory mapping\n\n| Mapping type | How it works | Flexibility |\n|---|---|---|\n| Physical (`HomeDirectoryType=PATH`) | Direct S3 path: `\u002Fbucket\u002Fhome\u002Falice` | One directory per user |\n| Logical (`HomeDirectoryType=LOGICAL`) | Virtual paths mapped to real S3 paths | Multiple directories, chroot-like |\n\n**Logical mapping** uses `HomeDirectoryDetails` to map virtual paths\nto real S3 paths:\n\nThe logical home-directory-mapping CLI example moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\n\nAlice sees `\u002Fuploads` and `\u002Fdownloads` as top-level directories, but\nthey map to different S3 buckets.\n\n## Step 7 — IAM role and session policy\n\nThe IAM role is assumed BY Transfer Family on behalf of the user. The\nsession policy scopes the role to the user's home directory.\n\nTrust policy JSON, session policy JSON, and create-user CLI moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\n\n**Critical:** the session policy INTERSECTS with the IAM role. The\neffective permissions are the intersection of both. If the IAM role\ndoes not grant S3 access, the session policy cannot add it.\n\n## Step 8 — Server host key and trusted host keys\n\nThe server host key identifies the Transfer Family server to SSH\nclients. Transfer Family generates one automatically, but you can\nupload a custom host key for brand consistency or compliance.\n\nThe custom host-key CLI example moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\n\n**Trusted host keys** are used by clients to verify the server. When a\nclient connects, SSH compares the server's host key against its\nknown_hosts entry. Distribute the host key to clients via a secure channel.\n\n## Step 9 — AS2 connectors\n\nAS2 (Applicability Statement 2) is a B2B file transfer protocol for\nEDI (Electronic Data Interchange) trading partner exchange.\n\nThe AS2 create-connector CLI example moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\n\nAS2 requires certificate exchange: you need the partner's public\ncertificate (for encryption) and your own private key (for signing).\nCertificates are managed via Transfer Family profiles.\n\n## Step 10 — Managed workflows\n\nManaged workflows automate file processing via Step Functions. Each\nfile upload triggers the workflow.\n\nThe create-workflow and update-server CLI sequences moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\n\nEvery file upload now triggers the workflow: copy to the data lake,\ntag as processed, and on exception tag as failed.\n\n## Step 11 — Structured JSON logging and CloudWatch\n\nTransfer Family supports structured JSON logging to CloudWatch Logs.\nEach connection, authentication, and file transfer is logged.\n\nThe structured-logging CLI example moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\n\nStructured logs include connection timestamp, client IP, username,\nauthentication result, file transfer details, and session duration.\n\n## Step 12 — Throttling and limits\n\n| Limit | Default | Adjustable |\n|---|---|---|\n| Files per second (per server) | 100 | Yes (support ticket) |\n| Concurrent connections | 10,000 | Yes |\n| Users per server | 10,000 (service-managed) | Yes |\n| File size | 5 GB max (S3 limit) | No |\n| Workflows per server | 1 | No |\n\nCloudWatch metrics (`FilesIn`, `FilesOut`, `BytesIn`, `BytesOut`)\nprovide throughput visibility.\n\n## Step 13 — Recent features\n\nThe 2023-2026 feature timeline moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## NEVER do these things\n\n1. **NEVER create a Transfer Family user without a session policy.**\n   Without a session policy, the user inherits the FULL IAM role\n   permissions. If the role grants broad S3 access, every SFTP user\n   can access every bucket. ALWAYS attach a session policy that scopes\n   the user to their home directory.\n\n2. **NEVER use a PUBLIC endpoint for internal file transfers.** PUBLIC\n   endpoints expose the SFTP server to the entire internet. For\n   internal transfers, use VPC_ENDPOINT (PrivateLink, recommended) or\n   VPC (NLB-based).\n\n3. **NEVER assume the IAM role alone provides per-user scoping.** The\n   IAM role defines MAXIMUM permissions. The session policy provides\n   EFFECTIVE per-user scoping. Both are required.\n\n4. **NEVER deploy an SFTP server without a server host key strategy.**\n   SSH clients will see a host key warning on first connection if the\n   key is not distributed via a trusted channel. Upload a custom host\n   key for brand consistency and distribute it to clients.\n\n5. **NEVER forget the IAM role trust policy.** The role assumed by\n   Transfer Family on behalf of users MUST have a trust policy allowing\n   `transfer.amazonaws.com`. Without it, the role cannot be assumed and\n   users cannot connect.\n\n6. **NEVER create a managed workflow without on-exception steps.** If a\n   workflow step fails and there are no on-exception steps, the file is\n   left in an indeterminate state. Always define cleanup or notification\n   steps for exceptions.\n\n7. **NEVER use FTP on a PUBLIC endpoint.** FTP sends credentials in\n   plaintext. FTP is ONLY available on VPC and VPC_ENDPOINT types. For\n   external partners, use SFTP or FTPS.\n\n8. **NEVER assume logical home directory mapping is chroot.** Logical\n   mapping provides virtual paths but does NOT prevent a user from\n   navigating to other paths if the session policy permits. The session\n   policy is the security boundary, not the home directory mapping.\n\n9. **NEVER deploy AS2 connectors without certificate verification.** AS2\n   requires mutual certificate exchange. Verify the trading partner's\n   certificate fingerprint before configuring the connector.\n\n10. **NEVER ignore Transfer Family CloudWatch metrics.** Monitor\n    `FilesIn`, `FilesOut`, `BytesIn`, `BytesOut`, and authentication\n    failure rates. Sudden spikes or drops indicate issues with partner\n    connectivity or automated processes.\n\n## Output format\n\n```text\nTRANSFER_FAMILY: \u003Cserver-id> (\u003Cprotocols>) — \u003Cendpoint-type>\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Server: \u003Cserver-id> (\u003Cprotocol: SFTP|FTPS|FTP>)\n  [✓|✗] Endpoint type: PUBLIC | VPC | VPC_ENDPOINT\n  [✓|✗] Identity provider: Service-managed | Directory Service | Custom Lambda\n  [✓|✗] VPC: \u003Cvpc-id> (subnets: \u003Csubnet-list>) | N\u002FA (PUBLIC)\n  [✓|✗] Security groups: \u003Csg-list> | N\u002FA (PUBLIC)\n  [✓|✗] Route 53: \u003Chostname> → \u003Cendpoint> | N\u002FA\n  [✓|✗] S3 bucket: \u003Cbucket-name>\n  [✓|✗] Users: \u003Cuser-list> (home directory: \u003Cmapping-type>)\n  [✓|✗] IAM role: \u003Crole-name> (trust: transfer.amazonaws.com)\n  [✓|✗] Session policy: attached per-user (S3 scoped) | MISSING (RISK)\n  [✓|✗] Server host key: custom | auto-generated\n  [✓|✗] Managed workflow: \u003Cworkflow-id> (\u003Csteps>) | none\n  [✓|✗] AS2 connector: \u003Cconnector-id> (\u003Cpartner>) | N\u002FA\n  [✓|✗] Structured logging: CloudWatch \u003Clog-group> | disabled\n  [✓|✗] Tags: \u003Ckey=value list>\nVERIFICATION_COMMANDS:\n  aws transfer describe-server --server-id \u003Cserver-id>\n  aws transfer list-users --server-id \u003Cserver-id>\n  aws transfer describe-workflow --workflow-id \u003Cworkflow-id>\n```\n\n### Worked example — SFTP with VPC_ENDPOINT, custom Lambda, and managed workflow\n\n```text\nTRANSFER_FAMILY: s-abc123 (SFTP) — VPC_ENDPOINT\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Server: s-abc123 (SFTP)\n  [✓] Endpoint type: VPC_ENDPOINT (PrivateLink)\n  [✓] Identity provider: Custom Lambda (transfer-idp-auth)\n  [✓] VPC: vpc-aaa11122 (subnets: subnet-aaa, subnet-bbb)\n  [✓] Security groups: sg-sftp-internal\n  [✓] Route 53: sftp.internal.example.com → vpce-xxx\n  [✓] S3 bucket: file-landing-zone\n  [✓] Users: alice, bob, carol (home directory: LOGICAL)\n  [✓] IAM role: TransferFamilyS3Access (trust: transfer.amazonaws.com)\n  [✓] Session policy: attached per-user (scoped to \u002Fhome\u002F\u003Cuser>\u002F*)\n  [✓] Server host key: custom (RSA 4096)\n  [✓] Managed workflow: w-def456 (COPY → TAG → CUSTOM Lambda scan)\n  [✓] AS2 connector: N\u002FA\n  [✓] Structured logging: CloudWatch \u002Faws\u002Ftransfer\u002Fsftp\n  [✓] Tags: Environment=production, App=file-landing-zone\nVERIFICATION_COMMANDS:\n  aws transfer describe-server --server-id s-abc123\n  aws transfer list-users --server-id s-abc123\n  aws transfer describe-workflow --workflow-id w-def456\n```\n\n## Error handling\n\nAll five failure-mode playbooks moved verbatim to [references\u002Ferror-handling.md](references\u002Ferror-handling.md).\n\n## References (load on demand)\n\n- [references\u002Fworked-examples.md](references\u002Fworked-examples.md) — per-step CLI sequences (Steps 4-11) plus session-policy and managed-workflow heuristic walkthroughs\n- [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) — 2023-2026 recent-feature timeline\n- [references\u002Ferror-handling.md](references\u002Ferror-handling.md) — five failure-mode playbooks (auth\u002Fno-file-access, VPC_ENDPOINT timeout, workflow not triggering, AS2 delivery, Lambda auth)\n- [references\u002Fidentity-providers-and-endpoints.md](references\u002Fidentity-providers-and-endpoints.md) — identity provider and endpoint detail\n- [references\u002Fmanaged-workflows-and-as2.md](references\u002Fmanaged-workflows-and-as2.md) — managed workflow and AS2 detail\n\n## Domain\n\nAWS CloudOps \u002F AWS Transfer Family Managed File Transfer & Automation.\n\n## AWS documentation\n\n- **Transfer Family User Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Ftransfer\u002Flatest\u002Fuserguide\u002Fwhat-is-aws-transfer.html\n- **Creating a server** — https:\u002F\u002Fdocs.aws.amazon.com\u002Ftransfer\u002Flatest\u002Fuserguide\u002Fcreate-server.html\n- **Identity providers** — https:\u002F\u002Fdocs.aws.amazon.com\u002Ftransfer\u002Flatest\u002Fuserguide\u002Fauthenticating-users.html\n- **Custom Lambda IDP** — https:\u002F\u002Fdocs.aws.amazon.com\u002Ftransfer\u002Flatest\u002Fuserguide\u002Fconfiguring-custom-idp.html\n- **Session policies** — https:\u002F\u002Fdocs.aws.amazon.com\u002Ftransfer\u002Flatest\u002Fuserguide\u002Fsession-policy.html\n- **Managed workflows** — https:\u002F\u002Fdocs.aws.amazon.com\u002Ftransfer\u002Flatest\u002Fuserguide\u002Fcreate-workflow.html\n- **AS2 connectors** — https:\u002F\u002Fdocs.aws.amazon.com\u002Ftransfer\u002Flatest\u002Fuserguide\u002Fas2.html\n- **VPC endpoints** — https:\u002F\u002Fdocs.aws.amazon.com\u002Ftransfer\u002Flatest\u002Fuserguide\u002Fconfiguring-endpoints.html\n- **Structured logging** — https:\u002F\u002Fdocs.aws.amazon.com\u002Ftransfer\u002Flatest\u002Fuserguide\u002Fstructured-logging.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, transfer-family, sftp, cloudops, deploy, storage, provisioning, managed-file-transfer, session-policy, as2, managed-workflow, vpc-endpoint","1","Jacky Chan — AWS Community Builder","aws-cloudops","Storage","0.1.0","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","deploy","high","false","capability","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.","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 transfer access, plus iam, s3, ec2, route53, and lambda access for custom identity providers and VPC endpoints. Works with Terraform aws_transfer_server \u002F aws_transfer_user \u002F aws_transfer_workflow resources and CloudFormation AWS::Transfer::Server \u002F AWS::Transfer::User \u002F AWS::Transfer::Workflow templates.","main","eeace51bd5dd1db2030729d83eeab988861553aa","skills\u002Ftransfer-family-workflow-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 transfer-family-workflow-deployer",{"tool":56,"command":57},"bunx","bunx skills add jhkchan\u002Faws-agent-skills --skill transfer-family-workflow-deployer",{"tool":59,"command":60},"pnpm","pnpm dlx skills add jhkchan\u002Faws-agent-skills --skill transfer-family-workflow-deployer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftransfer-family-workflow-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","参考文档",6321,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftransfer-family-workflow-deployer\u002Feval\u002Ftest-cases.yaml",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"evals\u002Fbaselines\u002Fas2-connector-trading-partner.md",522,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftransfer-family-workflow-deployer\u002Fevals\u002Fbaselines\u002Fas2-connector-trading-partner.md",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"evals\u002Fbaselines\u002Fmanaged-workflow-file-processing.md",519,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftransfer-family-workflow-deployer\u002Fevals\u002Fbaselines\u002Fmanaged-workflow-file-processing.md",{"path":79,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":80,"sourceHtmlUrl":81},"evals\u002Fbaselines\u002Fmissing-iam-role.md",527,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftransfer-family-workflow-deployer\u002Fevals\u002Fbaselines\u002Fmissing-iam-role.md",{"path":83,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":84,"sourceHtmlUrl":85},"evals\u002Fbaselines\u002Fsftp-custom-lambda-vpc.md",718,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftransfer-family-workflow-deployer\u002Fevals\u002Fbaselines\u002Fsftp-custom-lambda-vpc.md",{"path":87,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":88,"sourceHtmlUrl":89},"evals\u002Fbaselines\u002Fsftp-service-managed-public.md",562,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftransfer-family-workflow-deployer\u002Fevals\u002Fbaselines\u002Fsftp-service-managed-public.md",{"path":91,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":92,"sourceHtmlUrl":93},"evals\u002Feval_config.yaml",1815,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftransfer-family-workflow-deployer\u002Fevals\u002Feval_config.yaml",{"path":95,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":96,"sourceHtmlUrl":97},"evals\u002Fevals.json",9215,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftransfer-family-workflow-deployer\u002Fevals\u002Fevals.json",{"path":99,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":100,"sourceHtmlUrl":101},"evals\u002Fprompts\u002Fas2-connector-trading-partner.md",546,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftransfer-family-workflow-deployer\u002Fevals\u002Fprompts\u002Fas2-connector-trading-partner.md",{"path":103,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":104,"sourceHtmlUrl":105},"evals\u002Fprompts\u002Fmanaged-workflow-file-processing.md",584,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftransfer-family-workflow-deployer\u002Fevals\u002Fprompts\u002Fmanaged-workflow-file-processing.md",{"path":107,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":108,"sourceHtmlUrl":109},"evals\u002Fprompts\u002Fmissing-iam-role.md",421,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftransfer-family-workflow-deployer\u002Fevals\u002Fprompts\u002Fmissing-iam-role.md",{"path":111,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":112,"sourceHtmlUrl":113},"evals\u002Fprompts\u002Fsftp-custom-lambda-vpc.md",772,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftransfer-family-workflow-deployer\u002Fevals\u002Fprompts\u002Fsftp-custom-lambda-vpc.md",{"path":115,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":116,"sourceHtmlUrl":117},"evals\u002Fprompts\u002Fsftp-service-managed-public.md",706,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftransfer-family-workflow-deployer\u002Fevals\u002Fprompts\u002Fsftp-service-managed-public.md",{"path":119,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":120,"sourceHtmlUrl":121},"examples\u002FREADME.md",6096,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftransfer-family-workflow-deployer\u002Fexamples\u002FREADME.md",{"path":123,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Fadvanced-patterns.md",1510,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftransfer-family-workflow-deployer\u002Freferences\u002Fadvanced-patterns.md",{"path":127,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":128,"sourceHtmlUrl":129},"references\u002Ferror-handling.md",773,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftransfer-family-workflow-deployer\u002Freferences\u002Ferror-handling.md",{"path":131,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":132,"sourceHtmlUrl":133},"references\u002Fidentity-providers-and-endpoints.md",6947,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftransfer-family-workflow-deployer\u002Freferences\u002Fidentity-providers-and-endpoints.md",{"path":135,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":136,"sourceHtmlUrl":137},"references\u002Fmanaged-workflows-and-as2.md",7412,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftransfer-family-workflow-deployer\u002Freferences\u002Fmanaged-workflows-and-as2.md",{"path":139,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":140,"sourceHtmlUrl":141},"references\u002Fworked-examples.md",6245,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftransfer-family-workflow-deployer\u002Freferences\u002Fworked-examples.md",{"path":143,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":144,"sourceHtmlUrl":145},"skill.usf.yaml",4509,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftransfer-family-workflow-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",[],[]]