[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-aws-directconnect":3,"mdc--9xktrt-key":32,"related-org-aws-directconnect":528,"related-repo-aws-directconnect":701},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":21,"repoUrl":22,"updatedAt":23,"license":24,"forks":25,"topics":26,"repo":27,"sourceUrl":30,"mdContent":31},"directconnect","configure AWS Direct Connect","Configures AWS Direct Connect: choosing a connection model (dedicated, hosted, or a link aggregation group) and completing the cross connect; creating private, public, and transit virtual interfaces and bringing up BGP; reaching many VPCs through a Direct Connect gateway including cross-account transit gateway associations; encrypting traffic with MACsec or a private IP Site-to-Site VPN; making the connection resilient and tuning failover; managing link aggregation groups; SiteLink; and migrating from a virtual private gateway to a transit gateway. Use when the user wants a private, consistent network link between a data center and AWS, or operates an existing Direct Connect setup and needs to extend, encrypt, or harden it. Routes to the right per-task procedure in references. Do NOT use for transit gateway route tables and attachments (transitgateway skill), Site-to-Site VPN without Direct Connect (sitetositevpn skill), or Route 53 DNS routing (route53 skill).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"aws","AWS (Amazon)","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Faws.png",[12,16,19],{"name":13,"slug":14,"type":15},"Networking","networking","tag",{"name":17,"slug":18,"type":15},"Infrastructure","infrastructure",{"name":20,"slug":8,"type":15},"AWS",1822,"https:\u002F\u002Fgithub.com\u002Faws\u002Fagent-toolkit-for-aws","2026-07-22T06:00:40.512522",null,157,[],{"repoUrl":22,"stars":21,"forks":25,"topics":28,"description":29},[],"Official, AWS-supported MCP servers, skills, and plugins to help AI agents build on AWS","https:\u002F\u002Fgithub.com\u002Faws\u002Fagent-toolkit-for-aws\u002Ftree\u002FHEAD\u002Fskills\u002Fspecialized-skills\u002Fnetworking-and-content-delivery-skills\u002Fdirectconnect","---\nname: directconnect\ndescription: >-\n  Configures AWS Direct Connect: choosing a connection model (dedicated, hosted, or a link\n  aggregation group) and completing the cross connect; creating private, public, and transit virtual\n  interfaces and bringing up BGP; reaching many VPCs through a Direct Connect gateway including\n  cross-account transit gateway associations; encrypting traffic with MACsec or a private IP\n  Site-to-Site VPN; making the connection resilient and tuning failover; managing link aggregation\n  groups; SiteLink; and migrating from a virtual private gateway to a transit gateway. Use when the\n  user wants a private, consistent network link between a data center and AWS, or operates an\n  existing Direct Connect setup and needs to extend, encrypt, or harden it. Routes to the right\n  per-task procedure in references. Do NOT use for transit gateway route tables and attachments\n  (transitgateway skill), Site-to-Site VPN without Direct Connect (sitetositevpn skill), or Route 53\n  DNS routing (route53 skill).\nversion: 1\n---\n\n# AWS Direct Connect\n\n## Overview\n\nDomain expertise for configuring AWS Direct Connect, the service that gives a customer a private,\nconsistent network link between their own data center or colocation and AWS instead of routing over\nthe public internet. Covers choosing a connection model and completing the cross connect, creating\nvirtual interfaces and bringing up Border Gateway Protocol (BGP), reaching many VPCs through a\nDirect Connect gateway, encrypting traffic in transit, making the connection resilient, managing\nlink aggregation groups, SiteLink, and migrating from a virtual private gateway to a transit\ngateway.\n\nThis skill is a router. Each customer task maps to a procedure file under `references\u002F`. Read the\nmatching reference in full before acting, then follow its constraints and steps. The reference\nfiles are self-contained: each carries its own decision tables, constraints, procedure, and\ntroubleshooting.\n\nExecute commands using the AWS MCP server when connected (sandboxed execution, audit logging,\nobservability). Fall back to the AWS CLI otherwise. The Direct Connect console is regional, so pass\nthe customer's working `--region` on `aws directconnect` commands; a Direct Connect gateway is a\nglobal resource but is reached through a regional console view.\n\n## Which Direct Connect task do you need?\n\n| Goal | Reference |\n| --- | --- |\n| Choose dedicated vs hosted vs a link aggregation group, then complete the cross connect | [choosing a Direct Connect connection type](references\u002Fchoosing-a-direct-connect-connection-type.md) |\n| Create a private, public, or transit virtual interface and bring up BGP | [creating a virtual interface and configuring BGP](references\u002Fcreating-a-direct-connect-virtual-interface-and-configuring-bgp.md) |\n| Reach many VPCs over one connection through a Direct Connect gateway | [connecting many VPCs through a Direct Connect gateway](references\u002Fconnecting-many-vpcs-through-a-direct-connect-gateway.md) |\n| Encrypt traffic in transit with MACsec or a private IP Site-to-Site VPN | [encrypting traffic over Direct Connect](references\u002Fencrypting-traffic-over-direct-connect.md) |\n| Make the connection survive a failure and tune failover speed | [making a Direct Connect connection resilient](references\u002Fmaking-a-direct-connect-connection-resilient.md) |\n| Bundle connections into one logical link and manage members | [managing link aggregation groups](references\u002Fmanaging-direct-connect-link-aggregation-groups.md) |\n| Connect on-premises sites to each other over the AWS backbone | [setting up SiteLink](references\u002Fsetting-up-direct-connect-sitelink.md) |\n| Move from a virtual private gateway to a transit gateway without dropping traffic | [migrating from a virtual private gateway to a transit gateway](references\u002Fmigrating-direct-connect-from-a-virtual-private-gateway-to-a-transit-gateway.md) |\n\n## Routing notes\n\n- **Connection model comes first.** The choosing-a-connection-type reference is the entry point for\n  a customer with no link yet. It settles dedicated vs hosted vs a link aggregation group, checks\n  location support for the chosen speed, and separates a hosted connection from a hosted virtual\n  interface, a distinction customers confuse constantly. Run it before any cross connect is ordered,\n  since port speed cannot change after the connection is created.\n- **A connection carries no traffic until a virtual interface exists.** After the cross connect is\n  live, the creating-a-virtual-interface reference is the required next step. The virtual interface\n  type (private, public, or transit) decides what the connection can reach and is fixed at creation.\n  The jumbo-frame maximum transmission unit (MTU) should be set at creation but, on a private or\n  transit virtual interface, can be changed later with a brief connectivity disruption.\n- **One VPC vs many VPCs.** A single VPC in one Region can be reached over a private virtual\n  interface to a virtual private gateway. Reaching many VPCs, crossing accounts, or crossing Regions\n  is the Direct Connect gateway reference, which also owns the cross-account transit gateway\n  proposal-and-acceptance handshake.\n- **Encryption is a separate, deliberate step.** Direct Connect is not encrypted in transit by\n  default. The encrypting-traffic reference compares MACsec (Layer 2, over the cross connect) against\n  a private IP Site-to-Site VPN over a transit virtual interface (the recommended IPsec path). Route\n  here whenever the customer mentions regulated data or encryption.\n- **Resiliency model vs failover speed are two different questions.** The resiliency reference covers\n  both: the Resiliency Toolkit sets the topology and service level target, while BGP hold-timer\n  tuning and Bidirectional Forwarding Detection (BFD) set how fast failover actually converges.\n- **Link aggregation group as a model vs as ongoing management.** The connection-type reference\n  introduces the link aggregation group as a model choice at order time. The managing-link-aggregation-groups\n  reference owns ongoing member add\u002Fremove and minimum-links behavior, where removing a member can\n  take the whole group down.\n- **Migration is order-dependent.** The virtual-private-gateway-to-transit-gateway migration\n  reference exists because doing the cutover steps out of order drops production traffic. Route any\n  \"we outgrew the single-VPC model\" request here rather than to the plain Direct Connect gateway\n  reference.\n\n## Security Considerations\n\nDirect Connect provides a private link into VPC resources, so the security posture differs from the\npublic internet path. Carry these into every task:\n\n- **Not encrypted by default.** Direct Connect does not encrypt traffic in transit. You MUST treat\n  encryption as a separate, deliberate step (MACsec or a private IP Site-to-Site VPN) before\n  regulated or sensitive data crosses the link. See the encrypting-traffic reference.\n- **Physical and colocation security.** The link terminates on customer equipment at a Direct Connect\n  location or partner colocation. You SHOULD remind the customer that physical access control and\n  partner trust at that facility are part of the connection's security boundary.\n- **Monitoring and alerting.** You SHOULD recommend CloudWatch alarms on connection state and virtual\n  interface BGP status so connection-state changes and failures trigger alerts rather than relying on\n  manual detection.\n- **Audit logging.** You SHOULD confirm CloudTrail is enabled and logging `directconnect` API calls\n  (connection, virtual interface, and gateway-association changes) so all configuration changes are\n  captured for audit and compliance.\n- **CloudWatch Logs encryption.** You SHOULD encrypt CloudWatch Logs log groups that receive Direct\n  Connect-related logs or alarm state data with a KMS key, so sensitive connection metadata is\n  protected at rest.\n- **Least-privilege IAM.** You MUST scope IAM permissions for `directconnect` API actions to the\n  specific actions and resources each principal needs, and prefer ephemeral IAM credentials\n  over long-lived IAM user access keys. You MUST NOT grant `directconnect:*` on resource `*` or attach\n  any `*FullAccess` managed policy; instead scope actions to specific resource ARNs, e.g.\n  `arn:aws:directconnect:*:*:dxcon\u002F{connection_id}` for a connection, so a compromised principal cannot\n  touch every Direct Connect resource in the account.\n- **Route leaks between VPCs.** You SHOULD warn that advertising a supernet that overlaps VPC CIDRs\n  can cause unintended VPC-to-VPC traffic over a shared Direct Connect gateway; mitigate with specific\n  prefixes, separate gateways, or transit gateway blackhole routes.\n\n## Additional Resources\n\n- [AWS Direct Connect User Guide](https:\u002F\u002Fdocs.aws.amazon.com\u002Fdirectconnect\u002Flatest\u002FUserGuide\u002FWelcome.html)\n- [Security in AWS Direct Connect (AWS Direct Connect User Guide)](https:\u002F\u002Fdocs.aws.amazon.com\u002Fdirectconnect\u002Flatest\u002FUserGuide\u002Fsecurity.html)\n- [AWS Direct Connect product page](https:\u002F\u002Faws.amazon.com\u002Fdirectconnect\u002F)\n- [AWS Direct Connect pricing](https:\u002F\u002Faws.amazon.com\u002Fdirectconnect\u002Fpricing\u002F)\n",{"data":33,"body":35},{"name":4,"description":6,"version":34},1,{"type":36,"children":37},"root",[38,47,54,60,74,95,101,266,272,348,354,359,478,484],{"type":39,"tag":40,"props":41,"children":43},"element","h1",{"id":42},"aws-direct-connect",[44],{"type":45,"value":46},"text","AWS Direct Connect",{"type":39,"tag":48,"props":49,"children":51},"h2",{"id":50},"overview",[52],{"type":45,"value":53},"Overview",{"type":39,"tag":55,"props":56,"children":57},"p",{},[58],{"type":45,"value":59},"Domain expertise for configuring AWS Direct Connect, the service that gives a customer a private,\nconsistent network link between their own data center or colocation and AWS instead of routing over\nthe public internet. Covers choosing a connection model and completing the cross connect, creating\nvirtual interfaces and bringing up Border Gateway Protocol (BGP), reaching many VPCs through a\nDirect Connect gateway, encrypting traffic in transit, making the connection resilient, managing\nlink aggregation groups, SiteLink, and migrating from a virtual private gateway to a transit\ngateway.",{"type":39,"tag":55,"props":61,"children":62},{},[63,65,72],{"type":45,"value":64},"This skill is a router. Each customer task maps to a procedure file under ",{"type":39,"tag":66,"props":67,"children":69},"code",{"className":68},[],[70],{"type":45,"value":71},"references\u002F",{"type":45,"value":73},". Read the\nmatching reference in full before acting, then follow its constraints and steps. The reference\nfiles are self-contained: each carries its own decision tables, constraints, procedure, and\ntroubleshooting.",{"type":39,"tag":55,"props":75,"children":76},{},[77,79,85,87,93],{"type":45,"value":78},"Execute commands using the AWS MCP server when connected (sandboxed execution, audit logging,\nobservability). Fall back to the AWS CLI otherwise. The Direct Connect console is regional, so pass\nthe customer's working ",{"type":39,"tag":66,"props":80,"children":82},{"className":81},[],[83],{"type":45,"value":84},"--region",{"type":45,"value":86}," on ",{"type":39,"tag":66,"props":88,"children":90},{"className":89},[],[91],{"type":45,"value":92},"aws directconnect",{"type":45,"value":94}," commands; a Direct Connect gateway is a\nglobal resource but is reached through a regional console view.",{"type":39,"tag":48,"props":96,"children":98},{"id":97},"which-direct-connect-task-do-you-need",[99],{"type":45,"value":100},"Which Direct Connect task do you need?",{"type":39,"tag":102,"props":103,"children":104},"table",{},[105,124],{"type":39,"tag":106,"props":107,"children":108},"thead",{},[109],{"type":39,"tag":110,"props":111,"children":112},"tr",{},[113,119],{"type":39,"tag":114,"props":115,"children":116},"th",{},[117],{"type":45,"value":118},"Goal",{"type":39,"tag":114,"props":120,"children":121},{},[122],{"type":45,"value":123},"Reference",{"type":39,"tag":125,"props":126,"children":127},"tbody",{},[128,147,164,181,198,215,232,249],{"type":39,"tag":110,"props":129,"children":130},{},[131,137],{"type":39,"tag":132,"props":133,"children":134},"td",{},[135],{"type":45,"value":136},"Choose dedicated vs hosted vs a link aggregation group, then complete the cross connect",{"type":39,"tag":132,"props":138,"children":139},{},[140],{"type":39,"tag":141,"props":142,"children":144},"a",{"href":143},"references\u002Fchoosing-a-direct-connect-connection-type.md",[145],{"type":45,"value":146},"choosing a Direct Connect connection type",{"type":39,"tag":110,"props":148,"children":149},{},[150,155],{"type":39,"tag":132,"props":151,"children":152},{},[153],{"type":45,"value":154},"Create a private, public, or transit virtual interface and bring up BGP",{"type":39,"tag":132,"props":156,"children":157},{},[158],{"type":39,"tag":141,"props":159,"children":161},{"href":160},"references\u002Fcreating-a-direct-connect-virtual-interface-and-configuring-bgp.md",[162],{"type":45,"value":163},"creating a virtual interface and configuring BGP",{"type":39,"tag":110,"props":165,"children":166},{},[167,172],{"type":39,"tag":132,"props":168,"children":169},{},[170],{"type":45,"value":171},"Reach many VPCs over one connection through a Direct Connect gateway",{"type":39,"tag":132,"props":173,"children":174},{},[175],{"type":39,"tag":141,"props":176,"children":178},{"href":177},"references\u002Fconnecting-many-vpcs-through-a-direct-connect-gateway.md",[179],{"type":45,"value":180},"connecting many VPCs through a Direct Connect gateway",{"type":39,"tag":110,"props":182,"children":183},{},[184,189],{"type":39,"tag":132,"props":185,"children":186},{},[187],{"type":45,"value":188},"Encrypt traffic in transit with MACsec or a private IP Site-to-Site VPN",{"type":39,"tag":132,"props":190,"children":191},{},[192],{"type":39,"tag":141,"props":193,"children":195},{"href":194},"references\u002Fencrypting-traffic-over-direct-connect.md",[196],{"type":45,"value":197},"encrypting traffic over Direct Connect",{"type":39,"tag":110,"props":199,"children":200},{},[201,206],{"type":39,"tag":132,"props":202,"children":203},{},[204],{"type":45,"value":205},"Make the connection survive a failure and tune failover speed",{"type":39,"tag":132,"props":207,"children":208},{},[209],{"type":39,"tag":141,"props":210,"children":212},{"href":211},"references\u002Fmaking-a-direct-connect-connection-resilient.md",[213],{"type":45,"value":214},"making a Direct Connect connection resilient",{"type":39,"tag":110,"props":216,"children":217},{},[218,223],{"type":39,"tag":132,"props":219,"children":220},{},[221],{"type":45,"value":222},"Bundle connections into one logical link and manage members",{"type":39,"tag":132,"props":224,"children":225},{},[226],{"type":39,"tag":141,"props":227,"children":229},{"href":228},"references\u002Fmanaging-direct-connect-link-aggregation-groups.md",[230],{"type":45,"value":231},"managing link aggregation groups",{"type":39,"tag":110,"props":233,"children":234},{},[235,240],{"type":39,"tag":132,"props":236,"children":237},{},[238],{"type":45,"value":239},"Connect on-premises sites to each other over the AWS backbone",{"type":39,"tag":132,"props":241,"children":242},{},[243],{"type":39,"tag":141,"props":244,"children":246},{"href":245},"references\u002Fsetting-up-direct-connect-sitelink.md",[247],{"type":45,"value":248},"setting up SiteLink",{"type":39,"tag":110,"props":250,"children":251},{},[252,257],{"type":39,"tag":132,"props":253,"children":254},{},[255],{"type":45,"value":256},"Move from a virtual private gateway to a transit gateway without dropping traffic",{"type":39,"tag":132,"props":258,"children":259},{},[260],{"type":39,"tag":141,"props":261,"children":263},{"href":262},"references\u002Fmigrating-direct-connect-from-a-virtual-private-gateway-to-a-transit-gateway.md",[264],{"type":45,"value":265},"migrating from a virtual private gateway to a transit gateway",{"type":39,"tag":48,"props":267,"children":269},{"id":268},"routing-notes",[270],{"type":45,"value":271},"Routing notes",{"type":39,"tag":273,"props":274,"children":275},"ul",{},[276,288,298,308,318,328,338],{"type":39,"tag":277,"props":278,"children":279},"li",{},[280,286],{"type":39,"tag":281,"props":282,"children":283},"strong",{},[284],{"type":45,"value":285},"Connection model comes first.",{"type":45,"value":287}," The choosing-a-connection-type reference is the entry point for\na customer with no link yet. It settles dedicated vs hosted vs a link aggregation group, checks\nlocation support for the chosen speed, and separates a hosted connection from a hosted virtual\ninterface, a distinction customers confuse constantly. Run it before any cross connect is ordered,\nsince port speed cannot change after the connection is created.",{"type":39,"tag":277,"props":289,"children":290},{},[291,296],{"type":39,"tag":281,"props":292,"children":293},{},[294],{"type":45,"value":295},"A connection carries no traffic until a virtual interface exists.",{"type":45,"value":297}," After the cross connect is\nlive, the creating-a-virtual-interface reference is the required next step. The virtual interface\ntype (private, public, or transit) decides what the connection can reach and is fixed at creation.\nThe jumbo-frame maximum transmission unit (MTU) should be set at creation but, on a private or\ntransit virtual interface, can be changed later with a brief connectivity disruption.",{"type":39,"tag":277,"props":299,"children":300},{},[301,306],{"type":39,"tag":281,"props":302,"children":303},{},[304],{"type":45,"value":305},"One VPC vs many VPCs.",{"type":45,"value":307}," A single VPC in one Region can be reached over a private virtual\ninterface to a virtual private gateway. Reaching many VPCs, crossing accounts, or crossing Regions\nis the Direct Connect gateway reference, which also owns the cross-account transit gateway\nproposal-and-acceptance handshake.",{"type":39,"tag":277,"props":309,"children":310},{},[311,316],{"type":39,"tag":281,"props":312,"children":313},{},[314],{"type":45,"value":315},"Encryption is a separate, deliberate step.",{"type":45,"value":317}," Direct Connect is not encrypted in transit by\ndefault. The encrypting-traffic reference compares MACsec (Layer 2, over the cross connect) against\na private IP Site-to-Site VPN over a transit virtual interface (the recommended IPsec path). Route\nhere whenever the customer mentions regulated data or encryption.",{"type":39,"tag":277,"props":319,"children":320},{},[321,326],{"type":39,"tag":281,"props":322,"children":323},{},[324],{"type":45,"value":325},"Resiliency model vs failover speed are two different questions.",{"type":45,"value":327}," The resiliency reference covers\nboth: the Resiliency Toolkit sets the topology and service level target, while BGP hold-timer\ntuning and Bidirectional Forwarding Detection (BFD) set how fast failover actually converges.",{"type":39,"tag":277,"props":329,"children":330},{},[331,336],{"type":39,"tag":281,"props":332,"children":333},{},[334],{"type":45,"value":335},"Link aggregation group as a model vs as ongoing management.",{"type":45,"value":337}," The connection-type reference\nintroduces the link aggregation group as a model choice at order time. The managing-link-aggregation-groups\nreference owns ongoing member add\u002Fremove and minimum-links behavior, where removing a member can\ntake the whole group down.",{"type":39,"tag":277,"props":339,"children":340},{},[341,346],{"type":39,"tag":281,"props":342,"children":343},{},[344],{"type":45,"value":345},"Migration is order-dependent.",{"type":45,"value":347}," The virtual-private-gateway-to-transit-gateway migration\nreference exists because doing the cutover steps out of order drops production traffic. Route any\n\"we outgrew the single-VPC model\" request here rather than to the plain Direct Connect gateway\nreference.",{"type":39,"tag":48,"props":349,"children":351},{"id":350},"security-considerations",[352],{"type":45,"value":353},"Security Considerations",{"type":39,"tag":55,"props":355,"children":356},{},[357],{"type":45,"value":358},"Direct Connect provides a private link into VPC resources, so the security posture differs from the\npublic internet path. Carry these into every task:",{"type":39,"tag":273,"props":360,"children":361},{},[362,372,382,392,409,419,468],{"type":39,"tag":277,"props":363,"children":364},{},[365,370],{"type":39,"tag":281,"props":366,"children":367},{},[368],{"type":45,"value":369},"Not encrypted by default.",{"type":45,"value":371}," Direct Connect does not encrypt traffic in transit. You MUST treat\nencryption as a separate, deliberate step (MACsec or a private IP Site-to-Site VPN) before\nregulated or sensitive data crosses the link. See the encrypting-traffic reference.",{"type":39,"tag":277,"props":373,"children":374},{},[375,380],{"type":39,"tag":281,"props":376,"children":377},{},[378],{"type":45,"value":379},"Physical and colocation security.",{"type":45,"value":381}," The link terminates on customer equipment at a Direct Connect\nlocation or partner colocation. You SHOULD remind the customer that physical access control and\npartner trust at that facility are part of the connection's security boundary.",{"type":39,"tag":277,"props":383,"children":384},{},[385,390],{"type":39,"tag":281,"props":386,"children":387},{},[388],{"type":45,"value":389},"Monitoring and alerting.",{"type":45,"value":391}," You SHOULD recommend CloudWatch alarms on connection state and virtual\ninterface BGP status so connection-state changes and failures trigger alerts rather than relying on\nmanual detection.",{"type":39,"tag":277,"props":393,"children":394},{},[395,400,402,407],{"type":39,"tag":281,"props":396,"children":397},{},[398],{"type":45,"value":399},"Audit logging.",{"type":45,"value":401}," You SHOULD confirm CloudTrail is enabled and logging ",{"type":39,"tag":66,"props":403,"children":405},{"className":404},[],[406],{"type":45,"value":4},{"type":45,"value":408}," API calls\n(connection, virtual interface, and gateway-association changes) so all configuration changes are\ncaptured for audit and compliance.",{"type":39,"tag":277,"props":410,"children":411},{},[412,417],{"type":39,"tag":281,"props":413,"children":414},{},[415],{"type":45,"value":416},"CloudWatch Logs encryption.",{"type":45,"value":418}," You SHOULD encrypt CloudWatch Logs log groups that receive Direct\nConnect-related logs or alarm state data with a KMS key, so sensitive connection metadata is\nprotected at rest.",{"type":39,"tag":277,"props":420,"children":421},{},[422,427,429,434,436,442,444,450,452,458,460,466],{"type":39,"tag":281,"props":423,"children":424},{},[425],{"type":45,"value":426},"Least-privilege IAM.",{"type":45,"value":428}," You MUST scope IAM permissions for ",{"type":39,"tag":66,"props":430,"children":432},{"className":431},[],[433],{"type":45,"value":4},{"type":45,"value":435}," API actions to the\nspecific actions and resources each principal needs, and prefer ephemeral IAM credentials\nover long-lived IAM user access keys. You MUST NOT grant ",{"type":39,"tag":66,"props":437,"children":439},{"className":438},[],[440],{"type":45,"value":441},"directconnect:*",{"type":45,"value":443}," on resource ",{"type":39,"tag":66,"props":445,"children":447},{"className":446},[],[448],{"type":45,"value":449},"*",{"type":45,"value":451}," or attach\nany ",{"type":39,"tag":66,"props":453,"children":455},{"className":454},[],[456],{"type":45,"value":457},"*FullAccess",{"type":45,"value":459}," managed policy; instead scope actions to specific resource ARNs, e.g.\n",{"type":39,"tag":66,"props":461,"children":463},{"className":462},[],[464],{"type":45,"value":465},"arn:aws:directconnect:*:*:dxcon\u002F{connection_id}",{"type":45,"value":467}," for a connection, so a compromised principal cannot\ntouch every Direct Connect resource in the account.",{"type":39,"tag":277,"props":469,"children":470},{},[471,476],{"type":39,"tag":281,"props":472,"children":473},{},[474],{"type":45,"value":475},"Route leaks between VPCs.",{"type":45,"value":477}," You SHOULD warn that advertising a supernet that overlaps VPC CIDRs\ncan cause unintended VPC-to-VPC traffic over a shared Direct Connect gateway; mitigate with specific\nprefixes, separate gateways, or transit gateway blackhole routes.",{"type":39,"tag":48,"props":479,"children":481},{"id":480},"additional-resources",[482],{"type":45,"value":483},"Additional Resources",{"type":39,"tag":273,"props":485,"children":486},{},[487,498,508,518],{"type":39,"tag":277,"props":488,"children":489},{},[490],{"type":39,"tag":141,"props":491,"children":495},{"href":492,"rel":493},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fdirectconnect\u002Flatest\u002FUserGuide\u002FWelcome.html",[494],"nofollow",[496],{"type":45,"value":497},"AWS Direct Connect User Guide",{"type":39,"tag":277,"props":499,"children":500},{},[501],{"type":39,"tag":141,"props":502,"children":505},{"href":503,"rel":504},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fdirectconnect\u002Flatest\u002FUserGuide\u002Fsecurity.html",[494],[506],{"type":45,"value":507},"Security in AWS Direct Connect (AWS Direct Connect User Guide)",{"type":39,"tag":277,"props":509,"children":510},{},[511],{"type":39,"tag":141,"props":512,"children":515},{"href":513,"rel":514},"https:\u002F\u002Faws.amazon.com\u002Fdirectconnect\u002F",[494],[516],{"type":45,"value":517},"AWS Direct Connect product page",{"type":39,"tag":277,"props":519,"children":520},{},[521],{"type":39,"tag":141,"props":522,"children":525},{"href":523,"rel":524},"https:\u002F\u002Faws.amazon.com\u002Fdirectconnect\u002Fpricing\u002F",[494],[526],{"type":45,"value":527},"AWS Direct Connect pricing",{"items":529,"total":700},[530,547,562,577,592,602,617,633,650,663,675,690],{"slug":531,"name":531,"fn":532,"description":533,"org":534,"tags":535,"stars":21,"repoUrl":22,"updatedAt":546},"agents-build","add capabilities to existing agent projects","Use when adding capabilities to an existing agent project — memory, app integration, VPC, multi-agent, migration, model changes, browser, code interpreter, or resource removal. Triggers on: \"add memory\", \"remember across sessions\", \"call agent from app\", \"invoke agent from code\", \"auth to call agent\", \"streaming responses\", \"VPC\", \"VPC connectivity\", \"VPC error\", \"can't reach from VPC\", \"multi-agent\", \"A2A\", \"A2A auth\", \"orchestrator not delegating\", \"specialist not called\", \"migrate Bedrock Agent\", \"after import\", \"migration issue\", \"framework for migration\", \"change model\", \"browser tool\", \"code interpreter\", \"delete agent\", \"tear down\", \"agentcore remove\", \"cross-account memory\", \"resource-based policy on memory\", \"pay for x402 content\", \"402 Payment Required\", \"microtransactions\", \"paid API or tool\". Not for connecting to external APIs via Gateway — use agents-connect. Not for scaffolding a new project — use agents-get-started. Not for CLI\u002Fdev server errors — use agents-debug. Strands vs LangGraph in a migration context routes here.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[536,539,542,543],{"name":537,"slug":538,"type":15},"Agents","agents",{"name":540,"slug":541,"type":15},"Automation","automation",{"name":20,"slug":8,"type":15},{"name":544,"slug":545,"type":15},"Engineering","engineering","2026-07-12T08:42:53.812877",{"slug":548,"name":548,"fn":549,"description":550,"org":551,"tags":552,"stars":21,"repoUrl":22,"updatedAt":561},"agents-connect","connect agents to external services","Use when connecting your agent to external APIs, tools, or services via Gateway, or restricting tool access with Cedar policies. Handles gateway setup, target types, outbound auth (OAuth, API key, IAM), credentials, and Cedar policy authoring. Triggers on: \"connect to API\", \"add gateway\", \"connect to MCP server\", \"Lambda tools\", \"OpenAPI\", \"gateway target\", \"Cedar policy\", \"restrict tools\", \"policy engine\", \"gateway auth error\", \"store API key\", \"outbound credential\", \"env var API key\", \"API key None after deploy\", \"credential not available after deploy\", \"should this be a gateway target\", \"give my agent tools\", \"add tools to agent\". Not for inbound auth (who can call your agent) — use agents-harden. Not for debugging agent behavior — use agents-debug. Not for VPC networking errors (agent can't reach APIs due to VPC) — use agents-build. Not for creating or hosting a new MCP server project — use agents-get-started.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[553,554,557,560],{"name":537,"slug":538,"type":15},{"name":555,"slug":556,"type":15},"API Development","api-development",{"name":558,"slug":559,"type":15},"Authentication","authentication",{"name":20,"slug":8,"type":15},"2026-07-16T06:00:38.866147",{"slug":563,"name":563,"fn":564,"description":565,"org":566,"tags":567,"stars":21,"repoUrl":22,"updatedAt":576},"agents-debug","debug agent and environment issues","Use when your agent or environment is broken — wrong answers, errors, timeouts, tool failures, or CLI issues. Reads traces and logs to diagnose root causes. Also checks prerequisites when the CLI itself isn't working. Triggers on: \"agent not working\", \"wrong answer\", \"agent error\", \"tool call failing\", \"debug agent\", \"check logs\", \"read traces\", \"broken\", \"500 error\", \"424 error\", \"model access denied\", \"command not found\", \"stuck in DELETING\", \"maxVms exceeded\", \"cold start diagnosis\", \"cold start slow\", \"agentcore create error\", \"create failed\", \"exit code 7\", \"connection refused local dev\". Not for deploy failures — use agents-deploy. Not for performance tuning without errors — use agents-optimize. Not for VPC configuration — use agents-build. Not for observability setup or missing logs — use agents-optimize.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[568,569,570,573],{"name":537,"slug":538,"type":15},{"name":20,"slug":8,"type":15},{"name":571,"slug":572,"type":15},"Debugging","debugging",{"name":574,"slug":575,"type":15},"Observability","observability","2026-07-16T06:00:44.679093",{"slug":578,"name":578,"fn":579,"description":580,"org":581,"tags":582,"stars":21,"repoUrl":22,"updatedAt":591},"agents-deploy","deploy AI agents to AWS","Use when deploying your agent to AWS, or when a deploy has failed. Handles pre-flight validation, CDK\u002FIAM\u002Fquota error diagnosis, version management, rollback, and canary deployments. Triggers on: \"deploy my agent\", \"agentcore deploy\", \"deploy failed\", \"CDK error\", \"rollback\", \"canary deploy\", \"pin version\", \"redeploy\", \"deploy stuck\". Not for production hardening — use agents-harden. Not for adding capabilities before deploy — use agents-build or agents-connect. Not for VPC configuration errors — use agents-build.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[583,584,585,588],{"name":537,"slug":538,"type":15},{"name":20,"slug":8,"type":15},{"name":586,"slug":587,"type":15},"CI\u002FCD","ci-cd",{"name":589,"slug":590,"type":15},"Deployment","deployment","2026-07-12T08:42:55.059577",{"slug":593,"name":593,"fn":594,"description":595,"org":596,"tags":597,"stars":21,"repoUrl":22,"updatedAt":601},"agents-get-started","scaffold and deploy new agent projects","Use when a developer wants to create a new agent project or get started with AgentCore. Handles framework selection, project scaffolding, first deploy, and first invocation. Triggers on: \"build an agent\", \"create an agent\", \"get started\", \"new project\", \"agentcore create\", \"which framework\", \"Strands vs LangGraph\", \"hello world agent\", \"first agent\", \"create MCP server\", \"host MCP server\", \"agentcore dev\", \"dev server\", \"what port\", \"local development\". Not for adding capabilities to existing projects — use agents-build or agents-connect. Strands vs LangGraph in a migration context routes to agents-build, not here. Connecting to an existing MCP server routes to agents-connect, not here.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[598,599,600],{"name":537,"slug":538,"type":15},{"name":20,"slug":8,"type":15},{"name":589,"slug":590,"type":15},"2026-07-12T08:42:51.963247",{"slug":603,"name":603,"fn":604,"description":605,"org":606,"tags":607,"stars":21,"repoUrl":22,"updatedAt":616},"agents-harden","harden agents for production","Use when preparing your agent for production — IAM scoping, inbound auth (JWT, SigV4), secrets management, cold start optimization, session lifecycle, rate limiting, input validation, and quota guidance. Triggers on: \"production checklist\", \"harden agent\", \"production ready\", \"secure agent\", \"inbound auth\", \"going live\", \"cold start optimization\", \"session lifecycle\", \"StopRuntimeSession\", \"quota\", \"throttling\", \"maxVms\", \"rate limit\", \"security audit of outbound API calls\", \"gateway target audit for production\", \"restrict who can call\", \"lock down endpoint\", \"only our app can call\". Not for Cedar tool-restriction policies — use agents-connect. Not for quality measurement — use agents-optimize. Not for outbound credential storage or API key wiring — use agents-connect. Not for A2A agent-to-agent auth — use agents-build. Cold start observation and diagnosis (not optimization) routes to agents-debug.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[608,609,610,613],{"name":537,"slug":538,"type":15},{"name":20,"slug":8,"type":15},{"name":611,"slug":612,"type":15},"Best Practices","best-practices",{"name":614,"slug":615,"type":15},"Security","security","2026-07-16T06:00:42.174705",{"slug":618,"name":618,"fn":619,"description":620,"org":621,"tags":622,"stars":21,"repoUrl":22,"updatedAt":632},"agents-optimize","optimize agent quality and performance","Use when measuring or improving agent quality and performance — set up evaluators, online monitoring, CI\u002FCD quality gates, observability, or cost optimization. Triggers on: \"evaluate my agent\", \"add evaluator\", \"measure quality\", \"quality gate\", \"run evals\", \"agent too slow\", \"why is it slow\", \"reduce latency\", \"set up observability\", \"CloudWatch dashboard\", \"how much does my agent cost\", \"cost optimization\", \"logs not showing up\", \"logs missing\", \"spans not found\", \"eval failing\", \"eval error\", \"dev traces\", \"local traces\", \"agentcore dev traces\", \"traces to CloudWatch\". Not for debugging errors or crashes — use agents-debug. Slow but correct routes here; broken routes to debug.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[623,624,625,628,629],{"name":537,"slug":538,"type":15},{"name":20,"slug":8,"type":15},{"name":626,"slug":627,"type":15},"Evals","evals",{"name":574,"slug":575,"type":15},{"name":630,"slug":631,"type":15},"Performance","performance","2026-07-12T08:42:56.488105",{"slug":634,"name":634,"fn":635,"description":636,"org":637,"tags":638,"stars":21,"repoUrl":22,"updatedAt":649},"amazon-aurora-mysql","manage Amazon Aurora MySQL clusters","Amazon Aurora MySQL — creates, modifies, and advises on Aurora MySQL clusters specifically (MySQL-compatible engine, Aurora serverless, parallel query). Trigger for Aurora MySQL cluster operations, ACU sizing, I\u002FO-Optimized storage, commitment pricing, or MySQL upgrade planning. Aurora MySQL uses full (VPC-based) configuration — express configuration is PostgreSQL-only. For Aurora PostgreSQL, use amazon-aurora-postgresql instead. Contains safety guardrails and response templates that override defaults.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[639,640,643,646],{"name":20,"slug":8,"type":15},{"name":641,"slug":642,"type":15},"Database","database",{"name":644,"slug":645,"type":15},"MySQL","mysql",{"name":647,"slug":648,"type":15},"Serverless","serverless","2026-07-12T08:43:13.27939",{"slug":651,"name":651,"fn":652,"description":653,"org":654,"tags":655,"stars":21,"repoUrl":22,"updatedAt":662},"amazon-aurora-postgresql","configure Amazon Aurora PostgreSQL clusters","Amazon Aurora PostgreSQL — creates, modifies, and advises on Aurora PostgreSQL clusters specifically (PostgreSQL-compatible engine, Aurora serverless, express configuration, pgvector, Babelfish). Trigger for Aurora PostgreSQL cluster operations, express-configuration quick-start, ACU sizing, I\u002FO-Optimized storage, commitment pricing, or PostgreSQL upgrade planning. For Aurora MySQL, use amazon-aurora-mysql instead. Contains safety guardrails, express-first routing, and response templates that override defaults.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[656,657,658,661],{"name":20,"slug":8,"type":15},{"name":641,"slug":642,"type":15},{"name":659,"slug":660,"type":15},"PostgreSQL","postgresql",{"name":647,"slug":648,"type":15},"2026-07-16T06:00:34.789624",{"slug":664,"name":664,"fn":665,"description":666,"org":667,"tags":668,"stars":21,"repoUrl":22,"updatedAt":674},"amazon-bedrock","build generative AI apps with Amazon Bedrock","Builds generative AI applications on Amazon Bedrock. Covers model invocation (Converse API, InvokeModel), RAG with Knowledge Bases, Bedrock Agents, Guardrails, and AgentCore. Use when invoking models, setting up Knowledge Bases, creating agents, applying guardrails, deploying to AgentCore, migrating\u002Fporting\u002Fconverting a Bedrock Agent (including inline agents) to an AgentCore Harness, troubleshooting Bedrock errors (ThrottlingException, AccessDeniedException), or choosing models (Claude, Llama, Nova, Titan). ALSO USE for prompt caching setup and debugging, quota health checks and throttling diagnosis, cost attribution and tracking, migrating between Claude model generations (4.5 to 4.6 to 4.7), chunking strategies, API selection (Converse vs InvokeModel), guardrail capabilities, and model selection. Also covers AgentCore Payments setup (x402, microtransactions, Payment Manager, Connector, Instrument, Coinbase CDP, Stripe Privy, 402 Payment Required, pay for content, paid endpoint, agent payments). NOT for custom model training, Rekognition, or Comprehend.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[669,670,671],{"name":537,"slug":538,"type":15},{"name":20,"slug":8,"type":15},{"name":672,"slug":673,"type":15},"LLM","llm","2026-07-25T05:30:35.20899",{"slug":676,"name":676,"fn":677,"description":678,"org":679,"tags":680,"stars":21,"repoUrl":22,"updatedAt":689},"amazon-documentdb","manage Amazon DocumentDB clusters","Manages Amazon DocumentDB end-to-end — serverless-on-8.0 cluster setup, TLS\u002FVPC\u002Fdriver config, flexible-schema and vector-search data modeling, MongoDB compatibility assessment, DMS-based migration, slow-query diagnosis, major version upgrades (4.0→5.0→8.0), Well-Architected reviews (41-check wa_review.py), cost estimation, and security hardening. Retrieve for every DocumentDB question and when the user asks to set up or migrate MongoDB to AWS — DocumentDB is AWS's MongoDB-compatible managed database. Triggers: JSON document store, document database, MongoDB on AWS, Nested fields, Lambda cannot connect, TLS handshake, VPC port 27017, IAM auth, Secrets Manager, encryption at rest, $graphLookup, flexible schema, COLLSCAN, compound index, DMS migration, CDC cutover, $vectorSearch, RAG, Global Clusters, DR replication, cost sizing, audit, health check, production-readiness.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[681,682,683,686],{"name":20,"slug":8,"type":15},{"name":641,"slug":642,"type":15},{"name":684,"slug":685,"type":15},"MongoDB","mongodb",{"name":687,"slug":688,"type":15},"NoSQL","nosql","2026-07-12T08:43:00.455878",{"slug":691,"name":691,"fn":692,"description":693,"org":694,"tags":695,"stars":21,"repoUrl":22,"updatedAt":699},"amazon-dynamodb","design and debug DynamoDB data layers","Designs, reviews, and debugs DynamoDB data layers from design axioms — enumerates access patterns, chooses partition\u002Fsort keys and GSIs, decides single-table vs. multi-table, configures Streams, Global Tables, TTL, and zero-ETL integrations to OpenSearch\u002FRedshift\u002FSageMaker Lakehouse, and produces a defensible data-layer design with a monthly cost estimate and optional live validation. Applies whenever a user is designing, reviewing, or refactoring anything backed by DynamoDB — schemas, access patterns, GSIs, single- vs. multi-table choices, Streams consumers, transactional outboxes, Global Tables, zero-ETL pipelines — even when they don't say \"axioms\" or \"design review.\" Also applies when debugging hot partitions, throttling, unbounded Scans, LWW conflicts, or surprise bills on DynamoDB workloads.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[696,697,698],{"name":20,"slug":8,"type":15},{"name":641,"slug":642,"type":15},{"name":687,"slug":688,"type":15},"2026-07-16T06:00:37.690386",115,{"items":702,"total":752},[703,710,717,724,731,737,744],{"slug":531,"name":531,"fn":532,"description":533,"org":704,"tags":705,"stars":21,"repoUrl":22,"updatedAt":546},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[706,707,708,709],{"name":537,"slug":538,"type":15},{"name":540,"slug":541,"type":15},{"name":20,"slug":8,"type":15},{"name":544,"slug":545,"type":15},{"slug":548,"name":548,"fn":549,"description":550,"org":711,"tags":712,"stars":21,"repoUrl":22,"updatedAt":561},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[713,714,715,716],{"name":537,"slug":538,"type":15},{"name":555,"slug":556,"type":15},{"name":558,"slug":559,"type":15},{"name":20,"slug":8,"type":15},{"slug":563,"name":563,"fn":564,"description":565,"org":718,"tags":719,"stars":21,"repoUrl":22,"updatedAt":576},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[720,721,722,723],{"name":537,"slug":538,"type":15},{"name":20,"slug":8,"type":15},{"name":571,"slug":572,"type":15},{"name":574,"slug":575,"type":15},{"slug":578,"name":578,"fn":579,"description":580,"org":725,"tags":726,"stars":21,"repoUrl":22,"updatedAt":591},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[727,728,729,730],{"name":537,"slug":538,"type":15},{"name":20,"slug":8,"type":15},{"name":586,"slug":587,"type":15},{"name":589,"slug":590,"type":15},{"slug":593,"name":593,"fn":594,"description":595,"org":732,"tags":733,"stars":21,"repoUrl":22,"updatedAt":601},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[734,735,736],{"name":537,"slug":538,"type":15},{"name":20,"slug":8,"type":15},{"name":589,"slug":590,"type":15},{"slug":603,"name":603,"fn":604,"description":605,"org":738,"tags":739,"stars":21,"repoUrl":22,"updatedAt":616},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[740,741,742,743],{"name":537,"slug":538,"type":15},{"name":20,"slug":8,"type":15},{"name":611,"slug":612,"type":15},{"name":614,"slug":615,"type":15},{"slug":618,"name":618,"fn":619,"description":620,"org":745,"tags":746,"stars":21,"repoUrl":22,"updatedAt":632},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[747,748,749,750,751],{"name":537,"slug":538,"type":15},{"name":20,"slug":8,"type":15},{"name":626,"slug":627,"type":15},{"name":574,"slug":575,"type":15},{"name":630,"slug":631,"type":15},114]