원클릭으로 Manus에서 모든 스킬 실행

directconnect

스타2,048

포크190

업데이트2026년 7월 21일 14:48

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).

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

aws

aws/agent-toolkit-for-aws

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

AWS Direct Connect

Overview

Domain expertise for configuring AWS Direct Connect, the service that gives a customer a private, consistent network link between their own data center or colocation and AWS instead of routing over the public internet. Covers choosing a connection model and completing the cross connect, creating virtual interfaces and bringing up Border Gateway Protocol (BGP), reaching many VPCs through a Direct Connect gateway, encrypting traffic in transit, making the connection resilient, managing link aggregation groups, SiteLink, and migrating from a virtual private gateway to a transit gateway.

This skill is a router. Each customer task maps to a procedure file under references/. Read the matching reference in full before acting, then follow its constraints and steps. The reference files are self-contained: each carries its own decision tables, constraints, procedure, and troubleshooting.

Execute commands using the AWS MCP server when connected (sandboxed execution, audit logging, observability). Fall back to the AWS CLI otherwise. The Direct Connect console is regional, so pass the customer's working --region on aws directconnect commands; a Direct Connect gateway is a global resource but is reached through a regional console view.

Which Direct Connect task do you need?

Goal	Reference
Choose dedicated vs hosted vs a link aggregation group, then complete the cross connect	choosing a Direct Connect connection type
Create a private, public, or transit virtual interface and bring up BGP	creating a virtual interface and configuring BGP
Reach many VPCs over one connection through a Direct Connect gateway	connecting many VPCs through a Direct Connect gateway
Encrypt traffic in transit with MACsec or a private IP Site-to-Site VPN	encrypting traffic over Direct Connect
Make the connection survive a failure and tune failover speed	making a Direct Connect connection resilient
Bundle connections into one logical link and manage members	managing link aggregation groups
Connect on-premises sites to each other over the AWS backbone	setting up SiteLink
Move from a virtual private gateway to a transit gateway without dropping traffic	migrating from a virtual private gateway to a transit gateway

Routing notes

Connection model comes first. The choosing-a-connection-type reference is the entry point for a customer with no link yet. It settles dedicated vs hosted vs a link aggregation group, checks location support for the chosen speed, and separates a hosted connection from a hosted virtual interface, a distinction customers confuse constantly. Run it before any cross connect is ordered, since port speed cannot change after the connection is created.
A connection carries no traffic until a virtual interface exists. After the cross connect is live, the creating-a-virtual-interface reference is the required next step. The virtual interface type (private, public, or transit) decides what the connection can reach and is fixed at creation. The jumbo-frame maximum transmission unit (MTU) should be set at creation but, on a private or transit virtual interface, can be changed later with a brief connectivity disruption.
One VPC vs many VPCs. A single VPC in one Region can be reached over a private virtual interface to a virtual private gateway. Reaching many VPCs, crossing accounts, or crossing Regions is the Direct Connect gateway reference, which also owns the cross-account transit gateway proposal-and-acceptance handshake.
Encryption is a separate, deliberate step. Direct Connect is not encrypted in transit by default. The encrypting-traffic reference compares MACsec (Layer 2, over the cross connect) against a private IP Site-to-Site VPN over a transit virtual interface (the recommended IPsec path). Route here whenever the customer mentions regulated data or encryption.
Resiliency model vs failover speed are two different questions. The resiliency reference covers both: the Resiliency Toolkit sets the topology and service level target, while BGP hold-timer tuning and Bidirectional Forwarding Detection (BFD) set how fast failover actually converges.
Link aggregation group as a model vs as ongoing management. The connection-type reference introduces the link aggregation group as a model choice at order time. The managing-link-aggregation-groups reference owns ongoing member add/remove and minimum-links behavior, where removing a member can take the whole group down.
Migration is order-dependent. The virtual-private-gateway-to-transit-gateway migration reference exists because doing the cutover steps out of order drops production traffic. Route any "we outgrew the single-VPC model" request here rather than to the plain Direct Connect gateway reference.

Security Considerations

Direct Connect provides a private link into VPC resources, so the security posture differs from the public internet path. Carry these into every task:

Not encrypted by default. Direct Connect does not encrypt traffic in transit. You MUST treat encryption as a separate, deliberate step (MACsec or a private IP Site-to-Site VPN) before regulated or sensitive data crosses the link. See the encrypting-traffic reference.
Physical and colocation security. The link terminates on customer equipment at a Direct Connect location or partner colocation. You SHOULD remind the customer that physical access control and partner trust at that facility are part of the connection's security boundary.
Monitoring and alerting. You SHOULD recommend CloudWatch alarms on connection state and virtual interface BGP status so connection-state changes and failures trigger alerts rather than relying on manual detection.
Audit logging. You SHOULD confirm CloudTrail is enabled and logging directconnect API calls (connection, virtual interface, and gateway-association changes) so all configuration changes are captured for audit and compliance.
CloudWatch Logs encryption. You SHOULD encrypt CloudWatch Logs log groups that receive Direct Connect-related logs or alarm state data with a KMS key, so sensitive connection metadata is protected at rest.
Least-privilege IAM. You MUST scope IAM permissions for directconnect API actions to the specific actions and resources each principal needs, and prefer ephemeral IAM credentials over long-lived IAM user access keys. You MUST NOT grant directconnect:* on resource * or attach any *FullAccess managed policy; instead scope actions to specific resource ARNs, e.g. arn:aws:directconnect:*:*:dxcon/{connection_id} for a connection, so a compromised principal cannot touch every Direct Connect resource in the account.
Route leaks between VPCs. You SHOULD warn that advertising a supernet that overlaps VPC CIDRs can cause unintended VPC-to-VPC traffic over a shared Direct Connect gateway; mitigate with specific prefixes, separate gateways, or transit gateway blackhole routes.

Additional Resources

이 저장소의 다른 Skills

같은 저장소

route53

aws/agent-toolkit-for-aws

Configures Amazon Route 53 DNS: public and private records, traffic-steering routing policies, health checks, DNS Firewall, Route 53 Profiles, VPC Resolver (also known as Route 53 Resolver) for hybrid and Outposts networks, and Global Resolver. Applicable when the customer wants to point a hostname at a target, split or fail over traffic across endpoints, monitor an endpoint, block malicious domains, centralize DNS across accounts, or resolve private DNS across a hybrid network. Routes to the right per-task procedure in references. Does not cover CloudFront-specific setup (see the route53-cloudfront skill) or non-DNS networking.

2026-07-212.0k

shieldadvanced

aws/agent-toolkit-for-aws

Configures AWS Shield Advanced for enhanced Distributed Denial of Service (DDoS) protection: subscribing accounts and adding resource protections, enabling automatic application layer (layer 7) mitigation through AWS WAF, configuring health-based detection with Route 53 health checks, setting up Shield Response Team (SRT) access and proactive engagement, reviewing DDoS events and requesting cost protection credits, and aggregating resources into protection groups. Applicable when the user wants stronger DDoS protection for internet-facing resources (CloudFront, Application or Network Load Balancers, Elastic IP addresses, Global Accelerator, or Route 53 hosted zones), wants expert help during an attack, or wants to recover attack-driven scaling charges. Routes to the right per-task procedure in references. Not applicable for authoring AWS WAF rules (waf skill), creating Route 53 health checks (route53 skill), or org-wide Shield Advanced rollout with Firewall Manager (firewallmanager skill).

2026-07-212.0k

transitgateway

aws/agent-toolkit-for-aws

Configures AWS Transit Gateway: creating a hub and attaching VPCs, segmenting traffic with route tables, centralizing egress and inspection through a hub (appliances or a Gateway Load Balancer endpoint), forcing east-west traffic between VPCs through AWS Network Firewall, connecting on-premises networks over the transit-gateway side of a Site-to-Site VPN or Direct Connect attachment (including ECMP to aggregate bandwidth across multiple VPN tunnels), peering transit gateways across Regions, migrating from a VPC peering mesh, and routing IP multicast. Applicable when connecting many VPCs through one router, isolating environments, forcing VPC-to-VPC traffic through a central Network Firewall, reaching on-premises over the hub, linking Regions, or moving off a peering mesh. Not applicable for single-VPC routing, VPC peering between two VPCs (vpcpeering skill), Direct Connect gateway or virtual interface setup (directconnect skill), or Route 53 DNS work.

2026-07-212.0k

waf

aws/agent-toolkit-for-aws

Configures AWS WAF to filter web traffic: creating web access control lists (web ACLs) on CloudFront, Application Load Balancers, API Gateway, and AppSync; AWS Managed Rules tuned in Count mode; rate-based rules for HTTP floods; IP set and geographic match rules; Bot Control (Common and Targeted); turning bot labels into a confidence signal; stripping spoofed inbound x-amzn-waf-* headers; recovering the real client IP behind a CDN; Fraud Control (account takeover and account creation fraud prevention); and logging and request sampling. Use when the user wants to protect a web application or API from common exploits, bots, credential stuffing, fake-account creation, or HTTP floods at the application layer (layer 7). Routes to the right per-task procedure in references. Do NOT use for L3/L4 DDoS protection (shieldadvanced skill), multi-account WAF rollout (firewallmanager skill), CloudFront configuration (cloudfront skill), or Route 53 health checks or records (route53 skill).

2026-07-212.0k

aws-observability

aws/agent-toolkit-for-aws

Builds, configures, debugs, and optimizes AWS observability with CloudWatch (Log Insights, Metrics, Alarms, Dashboards, EMF), X-Ray, CloudTrail, and ADOT (AWS Distro for OpenTelemetry), AND enables/onboards services to Application Signals using ADOT auto-instrumentation SDKs. Covers Log Insights queries, alarms (metric, composite, anomaly), dashboards, custom metrics/EMF, X-Ray tracing and sampling, ADOT collector config, CloudTrail auditing, and end-to-end Application Signals enablement via ADOT SDKs (CloudWatch Observability EKS add-on, CloudWatch Agent IAM, OTLP endpoints, ServiceEvents, Dynamic Instrumentation), breakpoint and snapshot in Dynamic Instrumentation, live data capture in running service, debug without redeploying. Applies to CloudWatch, alarms, dashboards, EMF, X-Ray, traces, CloudTrail, ADOT, monitoring, synthetics/canaries, OR enabling/onboarding/instrumenting a service for Application Signals. Not for app logging or security threat detection.

2026-07-202.0k

aws-serverless

aws/agent-toolkit-for-aws

Builds, deploys, manages, debugs, configures, and optimizes serverless applications on AWS using Lambda, API Gateway, Step Functions, EventBridge, and SAM/CDK. Covers cold starts, CORS debugging, event source mappings, troubleshooting, concurrency, SnapStart, Powertools, function URLs, EventBridge Scheduler, Lambda layers, and production readiness. Triggers on mentions of Lambda, API Gateway, Step Functions, SAM templates, CDK serverless stacks, DynamoDB stream triggers, SQS event sources, cold starts, timeouts, 502/504 errors, throttling, concurrency, CORS, Powertools, or any event-driven architecture on AWS, even without the word "serverless." Does not apply to EC2, ECS/Fargate containers, or Amplify hosting.

2026-07-202.0k

name	directconnect
description	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).
version	1

AWS Direct Connect

Overview

Which Direct Connect task do you need?

Goal	Reference
Choose dedicated vs hosted vs a link aggregation group, then complete the cross connect	choosing a Direct Connect connection type
Create a private, public, or transit virtual interface and bring up BGP	creating a virtual interface and configuring BGP
Reach many VPCs over one connection through a Direct Connect gateway	connecting many VPCs through a Direct Connect gateway
Encrypt traffic in transit with MACsec or a private IP Site-to-Site VPN	encrypting traffic over Direct Connect
Make the connection survive a failure and tune failover speed	making a Direct Connect connection resilient
Bundle connections into one logical link and manage members	managing link aggregation groups
Connect on-premises sites to each other over the AWS backbone	setting up SiteLink
Move from a virtual private gateway to a transit gateway without dropping traffic	migrating from a virtual private gateway to a transit gateway

Routing notes

Connection model comes first. The choosing-a-connection-type reference is the entry point for a customer with no link yet. It settles dedicated vs hosted vs a link aggregation group, checks location support for the chosen speed, and separates a hosted connection from a hosted virtual interface, a distinction customers confuse constantly. Run it before any cross connect is ordered, since port speed cannot change after the connection is created.
A connection carries no traffic until a virtual interface exists. After the cross connect is live, the creating-a-virtual-interface reference is the required next step. The virtual interface type (private, public, or transit) decides what the connection can reach and is fixed at creation. The jumbo-frame maximum transmission unit (MTU) should be set at creation but, on a private or transit virtual interface, can be changed later with a brief connectivity disruption.
One VPC vs many VPCs. A single VPC in one Region can be reached over a private virtual interface to a virtual private gateway. Reaching many VPCs, crossing accounts, or crossing Regions is the Direct Connect gateway reference, which also owns the cross-account transit gateway proposal-and-acceptance handshake.
Encryption is a separate, deliberate step. Direct Connect is not encrypted in transit by default. The encrypting-traffic reference compares MACsec (Layer 2, over the cross connect) against a private IP Site-to-Site VPN over a transit virtual interface (the recommended IPsec path). Route here whenever the customer mentions regulated data or encryption.
Resiliency model vs failover speed are two different questions. The resiliency reference covers both: the Resiliency Toolkit sets the topology and service level target, while BGP hold-timer tuning and Bidirectional Forwarding Detection (BFD) set how fast failover actually converges.
Link aggregation group as a model vs as ongoing management. The connection-type reference introduces the link aggregation group as a model choice at order time. The managing-link-aggregation-groups reference owns ongoing member add/remove and minimum-links behavior, where removing a member can take the whole group down.
Migration is order-dependent. The virtual-private-gateway-to-transit-gateway migration reference exists because doing the cutover steps out of order drops production traffic. Route any "we outgrew the single-VPC model" request here rather than to the plain Direct Connect gateway reference.

Security Considerations

Direct Connect provides a private link into VPC resources, so the security posture differs from the public internet path. Carry these into every task:

Not encrypted by default. Direct Connect does not encrypt traffic in transit. You MUST treat encryption as a separate, deliberate step (MACsec or a private IP Site-to-Site VPN) before regulated or sensitive data crosses the link. See the encrypting-traffic reference.
Physical and colocation security. The link terminates on customer equipment at a Direct Connect location or partner colocation. You SHOULD remind the customer that physical access control and partner trust at that facility are part of the connection's security boundary.
Monitoring and alerting. You SHOULD recommend CloudWatch alarms on connection state and virtual interface BGP status so connection-state changes and failures trigger alerts rather than relying on manual detection.
Audit logging. You SHOULD confirm CloudTrail is enabled and logging directconnect API calls (connection, virtual interface, and gateway-association changes) so all configuration changes are captured for audit and compliance.
CloudWatch Logs encryption. You SHOULD encrypt CloudWatch Logs log groups that receive Direct Connect-related logs or alarm state data with a KMS key, so sensitive connection metadata is protected at rest.
Least-privilege IAM. You MUST scope IAM permissions for directconnect API actions to the specific actions and resources each principal needs, and prefer ephemeral IAM credentials over long-lived IAM user access keys. You MUST NOT grant directconnect:* on resource * or attach any *FullAccess managed policy; instead scope actions to specific resource ARNs, e.g. arn:aws:directconnect:*:*:dxcon/{connection_id} for a connection, so a compromised principal cannot touch every Direct Connect resource in the account.
Route leaks between VPCs. You SHOULD warn that advertising a supernet that overlaps VPC CIDRs can cause unintended VPC-to-VPC traffic over a shared Direct Connect gateway; mitigate with specific prefixes, separate gateways, or transit gateway blackhole routes.