AWS Ecs Service Connect Ipv6

Use when ECS Service Connect の DNS alias が IPv6 アドレスを返し、 IPv4-only の Fargate task から `network is unreachable` / `EAI_AGAIN` 等で接続できない問題に遭遇したとき。 OTel Collector → Tempo の OTLP gRPC、 Fargate → Service Connect の HTTP/gRPC 通信が突然失敗する症状が典型。 ECS / Fargate / Service Connect / OTLP / IPv6 dual-stack 関連の接続障害から起動して良い (user が原因を IPv6 と特定していなくても OK)。

423 stars 6 forksDevOps & Cloud

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add mizchi/skills --skill aws-ecs-service-connect-ipv6
Manual install
git clone --depth 1 https://github.com/mizchi/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/aws-ecs-service-connect-ipv6 ~/.claude/skills/aws-ecs-service-connect-ipv6

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# ECS Service Connect の IPv6 alias で詰まったとき

## 症状

Fargate task の中から Service Connect alias (`<service>.<namespace>.local:<port>`) に接続しようとして次のエラー:

```
dial tcp [2600:f0f0::3]:<port>: connect: network is unreachable
```

`2600:f0f0::3` は AWS Service Connect Envoy proxy が listen する IPv6 アドレス。

## 原因

ECS Service Connect は service alias に **IPv4 + IPv6** の両方を登録する (Envoy proxy が dual-stack listen)。一方 Fargate awsvpc task は **IPv4 only** がデフォルト。grpc-go や他の dual-stack client が DNS の最初に返ってきた IPv6 を選ぶと、IPv6 outbound 経路が無いので unreachable。

## 回避策(楽な順)

### A. プロトコルを HTTP に切り替える

OTLP gRPC (4317) の代わりに **OTLP HTTP** (4318) を使う。HTTP client (Go の `net/http` 等) は IPv4 を試行することが多く、dual-stack dial の問題を踏みにくい。

OpenTelemetry Collector の例:

```yaml
exporters:
  # 旧: otlp (gRPC) で IPv6 で詰まる
  # otlp/tempo:
  #   endpoint: tempo.study-aws.local:4317
  # 新: otlphttp で OK
  otlphttp/tempo:
    endpoint: http://tempo.study-aws.local:4318
    tls:
      insecure: true

service:
  pipelines:
    traces:
      exporters: [otlphttp/tempo]
```

target 側の Service Connect 設定は HTTP port (4318) も alias にしておく:

```hcl
service_connect_configuration {
  service {
    port_name      = "otlp-grpc"
    discovery_name = "tempo"
    client_alias { port = 4317; dns_name = "tempo.study-aws.local" }
  }
  service {
    port_name      = "otlp-http"
    discovery_name = "tempo-http"
    client_alias { port = 4318; dns_name = "tempo.study-aws.local" }
  }
}
```

### B. Cloud Map private DNS namespace + A record (IPv4 only)
Read the full skill on GitHub

Details

Skill name
aws-ecs-service-connect-ipv6
Repository
mizchi/skills
Path
aws-ecs-service-connect-ipv6/SKILL.md
Repo updated
18 November 2026

FAQ

What does the AWS Ecs Service Connect Ipv6 skill do?

Use when ECS Service Connect の DNS alias が IPv6 アドレスを返し、 IPv4-only の Fargate task から `network is unreachable` / `EAI_AGAIN` 等で接続できない問題に遭遇したとき。 OTel Collector → Tempo の OTLP gRPC、 Fargate → Service Connect の HTTP/gRPC 通信が突然失敗する症状が典型。 ECS / Fargate / Service Connect / OTLP / IPv6 dual-stack 関連の接続障害から起動して良い (user が原因を IPv6 と特定していなくても OK)。

How do I install the AWS Ecs Service Connect Ipv6 skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add mizchi/skills --skill aws-ecs-service-connect-ipv6. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is AWS Ecs Service Connect Ipv6 popular?

It lives in mizchi/skills, which has 423 GitHub stars and 6 forks.

Related skills

Actions CI Tuning

423

mizchi/skills

Use when auditing or improving GitHub Actions workflows for a project. Covers cache setup (npm/pnpm/yarn), job parallelism, shard-based test splitting, artifact handling pitfalls, and Playwright-specific patterns. Trigger on: slow CI, cache miss, flaky shard jobs, merge-reports failures, or an explicit 'tune CI' request.

Testing & QA

AI Index

423

mizchi/skills

Method and tooling for measuring how AI-generated a piece of prose reads, in Japanese or English. Two layers — a deterministic lint for removable surface tells (scripts/slopscore.py, no API) and a judgment layer of typed probabilistic questions (Jev noul/score) for the tells that survive editing. Includes measured human/AI baselines, a gap-first calibration procedure, and labeled fixtures. Use when building or calibrating an AI-likeness score, or when a draft needs a defensible number rather than a vibe. For writing guidance use natural-writing-ja / natural-writing-en instead.

AI, LLMs & Agents

Apm Usage

423

mizchi/skills

Reference for APM manifests, installation, targeted updates, deployment paths and lockfiles. Invoke when the user explicitly asks about APM or apm.yml, or an unfamiliar APM command/error needs exact CLI details. Do not automatically invoke for every project that happens to have installed skills.

DevOps & Cloud

AWS Github Oidc Scoped Role

423

mizchi/skills

Configure GitHub Actions OIDC trust in AWS IAM using audience and exact subject conditions, including custom subjects for reusable workflows, Bedrock inference-profile permissions and explicit Deny guardrails. Use when designing or reviewing AWS roles assumed by GitHub Actions.

DevOps & Cloud

AWS Ecs Codedeploy Blue Green

423

mizchi/skills

ECS blue/green deployment patterns. Recommends ALB-native weighted target groups as the simpler default; covers CodeDeploy as a reference for teams that already use it or need pipeline-integrated rollback. Use when choosing or debugging ECS blue/green infrastructure.

DevOps & Cloud

AWS Vault Mfa Iam

423

mizchi/skills

Use when AWS account の IAM API が MFA 必須 policy で弾かれて、 `sts:GetCallerIdentity` は通るのに `iam:*` が `InvalidClientTokenId` で拒否されるとき、 または FIDO2 passkey で MFA が CLI から使えないとき。 aws-vault / aws-cli / MFA / passkey 関連で「アクセス拒否」 「token expired」 「IAM 操作のみ失敗」 等の症状から起動 (user が aws-vault を名指しでなくても OK)。

DevOps & Cloud

Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.