Unexpected Usage Increase Despite No Running Instances(작동하는 인스턴스가 없음에도 불구하고 사용량이 늘어나고 있습니다.)

Question

작동하는 인스턴스가 없음에도 불구하고 사용량이 늘어나고 있습니다.

안녕하세요. 저는 aws 서비스를 시작한지 얼마 되지 않았고 현재 프리티어를 사용중입니다.
몇달전, ec2에 인스턴스 한개를 생성했습니다. 그 인스턴스를 잠시 사용하던 중 비활성화(stopped) 상태로 변경했습니다.
해당 인스턴스에는 작은 py파일 두개만 포함되어 있습니다.
그럼에도 허용 사용량을 거의 다 사용했다는 메일이 왔습니다. 아무리 제 ec2를 뒤지고 찾아봐도 어디서 스토리지를 사용하고 있는 것인지 모르겠습니다. 
제 사용량을 더 자세히 확인할 수 있는 방법이나, 완전히 사용을 0으로 만드는 방법을 알고 싶습니다.
+ 이미지를 첨부합니다. 리소스 리전은 싱가폴 한곳만 사용하고 있으며, 그 안에서 인스턴스를 하나만 생성하여 사용했고, 해당 인스턴스는 (stopped)상태입니다.
다른 질문글을 보니 인스턴스를 삭제해야 완전히 사용량이 0이 된다고하는데, 그럼 인스턴스가 중지상태에서 하나만 있어도 이렇게 계속 사용량이 늘어나고 나중에는 요금이 부과될 수도 있나요?

Hello,

I’m fairly new to using AWS services and am currently on the Free Tier plan. A few months ago, I created a single EC2 instance, which I used briefly before stopping it. The instance only contains two small Python files.

However, I recently received an email stating that I have nearly reached my usage limit. Despite checking my EC2 instance thoroughly, I cannot figure out where the storage usage is coming from, especially since no instances are currently running.

I have attached an image for reference. I’m only using the Singapore region, and I’ve created and used only one instance within that region. That instance is currently in the "stopped" state.

Could you please help me understand what might be consuming my usage quota?

Thank you.
![Enter image description here](/media/postImages/original/IMh0O5heVxQ36zBA_aEuwvuQ)
![Enter image description here](/media/postImages/original/IMHXvz1e55QsiGG8B7194Ymg)
![Enter image description here](/media/postImages/original/IMT2Km2NOXRoesX7bkFI0gSw)
![Enter image description here](/media/postImages/original/IMneet00jxRuu2Bssx-n54bA)
![Enter image description here](/media/postImages/original/IMbBFopW1-S0SWvO7ZOL76CQ)

froguin · Answer

안녕하세요.

EC2 인스턴스를 띄우면, 디스크가 연결되는데 이것이 EBS입니다. EBS는 프리 티어로 30GB 까지 사용할 수 있으며, 캡쳐 이미지로 봤을 때는 약 85% 사용 중입니다.

EBS 볼륨 사용량은 연결된 볼륨의 크기여서 OS에서 사용하는 사용량과 다르며, EBS 볼륨을 수정해서 확장/추가 할당을 하지 않으면 현재 상태가 유지되므로 과금 걱정을 하지 않아도 됩니다.

인스턴스가 정지 상태더라도, 볼륨은 할당되어 연결되어 있는 상태이기 때문에 사용량은 유지됩니다. 볼륨 할당 정보는 EC2콘솔 -> Elastic block store -> Volumes 에서 볼 수 있습니다.

re:Post Agent · Answer

Thank you for providing detailed information about your AWS usage situation. I understand your concern about unexpected usage increases despite having no running instances. Let me explain what's likely happening and provide some guidance.

Even when an EC2 instance is stopped, certain associated resources continue to consume your Free Tier allocation or potentially incur charges. The main culprit in your case is likely the Elastic Block Store (EBS) volume attached to your stopped EC2 instance.

EBS volumes, which act as the virtual hard disk for your EC2 instance, continue to exist and consume storage even when the instance is stopped. This means you're still using up your Free Tier storage allocation, which is typically 30 GB per month for EBS.

In your case, the usage you're seeing (25.6 GB-Mo) is approaching the Free Tier limit for EBS storage. This usage accumulates over time, even if your instance is stopped, as long as the EBS volume exists.

To completely stop all usage and charges:

1. Terminate (not just stop) your EC2 instance if you don't plan to use it soon.
2. Delete any associated EBS volumes after terminating the instance.
3. Check for and release any Elastic IP addresses if you've allocated any.
4. Review your EC2 dashboard to ensure you don't have any resources in other regions.

To monitor your usage more closely:

1. Use the AWS Billing Dashboard to track your consumption.
2. Set up AWS Budgets or Free Tier usage alerts to notify you when you're approaching limits.
3. Regularly check the Free Tier usage page in your AWS console.

Remember, while AWS offers a generous Free Tier, it's crucial to understand which resources continue to consume your allocation even when not actively used. In the future, if you're done with an instance and don't plan to use it soon, it's best to terminate it and delete associated resources rather than just stopping it.

Regarding your question about charges: Yes, even with just one stopped instance, you can continue to accumulate usage, and potentially incur charges once you exceed the Free Tier limits. This is primarily due to the persistent EBS volumes and any other associated resources that continue to exist.  
**Sources**  
[Why has an inactive EC2 instance exceeded 85% of the monthly usage limit? | AWS re:Post](https://repost.aws/questions/QUsdsRTXHQQv6o629-aSR12g/why-has-an-inactive-ec2-instance-exceeded-85-of-the-monthly-usage-limit)  
[About free tiel ec2 instance | AWS re:Post](https://repost.aws/questions/QU7lcVvuSCTJ6avv91UGwPIg/about-free-tiel-ec2-instance)  
[AWS Free Usage Tier (Global-DataTransfer-Regional-Bytes) | AWS re:Post](https://repost.aws/questions/QULFb-bctlRAiyDewiqQ639w/aws-free-usage-tier-global-datatransfer-regional-bytes)

Unexpected Usage Increase Despite No Running Instances(작동하는 인스턴스가 없음에도 불구하고 사용량이 늘어나고 있습니다.)

답변 추가

관련 콘텐츠