Usando AWS re:Post, accetti AWS re:Post Termini di utilizzo
AWS re:Postre:Post

ECS support for IPv6-only

6

Hi,

I'm trying to set up ECS services in an environment where the only public Internet connectivity is via IPv6. The ecs agent is unable to talk to e.g. ecs.us-east-1.amazonaws.com and I notice it has no AAAA record.

Is this by design? As public IPv4 addresses become costly in a few months, it would be very desirable to be able to use ECS without them (or gateways etc.).

Thank you

  • surendra
    3 mesi fa

    This is such an important feature which is missing. We are being billed $$$ because of this.

  • otottkovacstibor
    2 mesi fa

    It is still not possible to create ECS services with IPv6 only and still need to pay for the allocated IPv4 addresses.

Argomenti
Container
Tag
Servizio container Amazon Elastic
Lingua
English
Jon
posta 7 mesi fa1350 visualizzazioni
5 Risposte
5

Why has this not been answered? Since this month we're charged for having IPv4 public addresses, but it seems AWS has not done their effort to provide proper IPv6 support on widely used services like ECS.

Foo
con risposta 3 mesi fa
2

Any Solution for this problem

Jagrit Nokwal
con risposta 3 mesi fa
1

Agent not able to resolve the ipv6 address Same issue here. We can clearly see that the issue is resolving the ecs endpoint b/c the there's no AAAA record on them. I was able to get the agent to connect when I followed the instructions here by adding a NAT Gateway and making a subnet route for it.

works after attaching nat

H_Proppy
con risposta 3 mesi fa
1

This is the kind of thing I would expect from Microsoft, rather than AWS.

I understand IPv4 addresses are scarce, and encouraging a transition to IPv6 is a good thing, but surely it's a no-brainer to make your own services IPv6 compatible before forcing your customers to adopt it.

bgre033
con risposta un mese fa
-7

The VPC needs to be in dual-stack mode. ECS supports IPv6 for EC2 and Fargate launch types.

AWS
Rajarshi_D
con risposta 7 mesi fa
  • Jon
    7 mesi fa

    Thank you for the answer! Specifically this is what I would like to support:

    VPC subnets have private IPv4 addresses only, and public IPv6 addresses There is no Internet Gateway or NAT gateway anywhere Instances have public IPv6 addresses. They have connectivity to the Internet via IPv6 which works well. The public ECS APIs do not support IPv6, so these instances cannot talk to ECS.

    What are the options here? Since AWS is encouraging customers to stop using public IPv4 addresses by charging for them, when will ECS support public IPv6 connectivity?

  • Lucas
    3 mesi fa

    The VPC is already in Dual Stack mode and I've already updated the account settings in ECS to enable dual-stack as well. Still, the task cannot communicate with the container via IPv6, only when using public IPv4. Also, Load Balancer has dual-stack enabled, but the public IPv4 can't be disabled. How do we handle these problems? :(

Accesso non effettuato. Accedi per postare una risposta.

Una buona risposta soddisfa chiaramente la domanda, fornisce un feedback costruttivo e incoraggia la crescita professionale del richiedente.

Linee guida per rispondere alle domande

Contenuto pertinente