- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
Open the EC2 Console in the correct region which looks like us-east-1
Goto Elastic IPs
Here you will be able to see the Elastic IPs you are being charged for. They can be assigned to the likes of an EC2, ECS Task, RDS, NAT Gateway etc etc.
you should see the public IPv4 address associated with the instance. It will typically be listed under the "IPv4 Public IP" or "Public IP" section. Once you've located the public IPv4 address associated with your EC2 instance, you can determine if it's necessary for your use case. If you're not actively using the public IP address, you can consider disassociating it from your instance to avoid incurring additional charges, and also please refer this link https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/
Select the Instance: In the EC2 dashboard, select the EC2 instance -> Networking ->"Network Interfaces" section and click on the network interface associated with the instance -> Disassociate the IPv4 Address-> In the network interface details pane, locate the public IPv4 address and click on "Actions" > "Disassociate address." Confirm the disassociation when prompted.
Thanks a lot for replying but it shows there are no Elastic IP addresses found in that Region, Even I have no EC2 instance there.
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 8 mesi fa
Thanks a lot for replying but it shows there are no Elastic IP addresses found in that Region, Even I have no EC2 instance there.