使用 AWS re:Post 即表示您同意 AWS re:Post 使用條款

I want to disable IPv4 address allocation for load balancer subnet and stop charging.

0

I disabled IPv4 address auto allocation and flexible IPv4 address auto allocation on the subnet because of the recently changed rate policy, so why are IP addresses being allocated by Amazon VPC IP Address Manager? I changed multiple address allocations including RDS due to the change in the IPv4 rate policy, but it is not reflected.

Will I still be charged if I disable automatic allocation of public ip addresses in vpc subnet management?

Is there any way to use load balancer and not charge for IPv4 address allocation?

已提問 9 個月前檢視次數 1873 次
3 個答案
2
已接受的答案

For a load balancer to be provisioned without public IP addresses, its scheme needs to be set to internal, and not internet-facing https://docs.aws.amazon.com/elasticloadbalancing/latest/userguide/how-elastic-load-balancing-works.html#load-balancer-scheme

When you create a load balancer, you must choose whether to make it an internal load balancer or an internet-facing load balancer.

The nodes of an internet-facing load balancer have public IP addresses.

The nodes of an internal load balancer have only private IP addresses.

I don't think it's possible to make the change to an existing load balancer on-the-fly, I think a replacement load-balancer would have to be provisioned with the scheme set at creation time.

profile picture
專家
已回答 9 個月前
profile picture
專家
已審閱 5 個月前
profile picture
專家
已審閱 9 個月前
  • Thank you! I'll try this way again.

    But what is the difference between an internal load balancer and an internal face load balancer? Is there no significant difference in traffic requests from clients?

  • Internal load balancer can only be reached by clients inside the same VPC (or peered VPCs, or across Direct Connect etc.), subject to security group rules & NACLs allowing it.

    Internet-facing load balancer has a publicly routable IP address which can be reached over the internet, again subject to security groups and NACLs.

0

Hello.

As of March 2024, I think ALB can only be configured as IPv4-only or dual stack using IPv4 and IPv6, so I don't think you can delete public IPv4 even if you change the settings on the subnet.
https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-ip-address-type.html
https://docs.aws.amazon.com/vpc/latest/userguide/aws-ipv6-support.html

profile picture
專家
已回答 9 個月前
profile picture
專家
已審閱 9 個月前
0

It’s only PUBLIC IPv4 that’s being charged now not private IPV4.

https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/

profile picture
專家
已回答 9 個月前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南