Your company currently has 5 EC2 Instances that use Instance store volumes. The Instances have been placed in the stopped state for a week now. But you notice that you are still being charged for AWS EC2 service. Which of the following could be a possible reason for this?

Answer options:

A.Instances in stopped state still incur a charge within AWS.
B.Instance store Instances incur a charge no matter which state they are in
C.You are being charged for the EBS volumes.
D.You have Elastic IPs associated with those instances.

Answer – D
The AWS documentation mentions the following on Elastic IP addresses
An Elastic IP address doesn’t incur charges as long as the following conditions are true:
· The Elastic IP address is associated with an Amazon EC2 instance.
· The instance associated with the Elastic IP address is running.
· The instance has only one Elastic IP address attached to it.
If you’ve stopped or terminated an EC2 instance with an associated Elastic IP address and you don’t need that Elastic IP address any more, consider disassociating or releasing the Elastic IP address
Hence the most feasible reason will be that there were Elastic IP’s associated with these instances.
For more information, please visit the below URL:
https://aws.amazon.com/premiumsupport/knowledge-center/elastic-ip-charges/