- 최신
- 최다 투표
- 가장 많은 댓글
Effective February 1, 2024, there is a charge of $0.005 per IP per hour for all public IPv4 addresses, whether attached to a service or not (there was already a charge for public IPv4 addresses you allocate in your account but don’t attach to an EC2 instance).
This change applies to all AWS services, including Amazon Elastic Compute Cloud (Amazon EC2), Amazon Relational Database Service (RDS) database instances, Amazon Elastic Kubernetes Service (Amazon EKS) nodes, and other AWS services that can have a public IPv4 address allocated and attached, in all AWS regions (commercial, AWS China, and GovCloud). https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/
Here are some resources to show you how to use IPv6 with widely used services https://d1.awsstatic.com/architecture-diagrams/ArchitectureDiagrams/IPv6-reference-architectures-for-AWS-and-hybrid-networks-ra.pdf
Thanks for the information.
I'm not sure if I understand it correctly, dual stack doesn't mean I have to have both IPV4 and IPV6 address. Is it ok just keep IPV6 and it is ok to use IPV6 only for public RDS service?
Thanks!
I checked the documents again. Seems RDS doesn't support IPV6 only.
https://aws.amazon.com/cn/blogs/database/ipv6-addressing-with-amazon-rds/ https://repost.aws/knowledge-center/rds-ipv6
Hope it can develop the function soon.
We can create a VPC subnet with IPv6 only, but we can NOT create an RDS subnet group if we don't have IPv4 allocated to VPC subnets, unfortunately
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_VPC.WorkingWithRDSInstanceinaVPC.html#USER_VPC.IP_addressing
By default, Amazon RDS and Amazon VPC use the IPv4 addressing protocol. You can't turn off this behavior. When you create a VPC, make sure to specify an IPv4 CIDR block (a range of private IPv4 addresses). You can optionally assign an IPv6 CIDR block to your VPC and subnets, and assign IPv6 addresses from that block to DB instances in your subnet.