- 新しい順
- 投票が多い順
- コメントが多い順
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.
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.
The VPC needs to be in dual-stack mode. ECS supports IPv6 for EC2 and Fargate launch types.
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?
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? :(
関連するコンテンツ
AWS公式更新しました 2年前
This is such an important feature which is missing. We are being billed $$$ because of this.
It is still not possible to create ECS services with IPv6 only and still need to pay for the allocated IPv4 addresses.