AWS S3 data tranfer usage too high

[rico-c]

Bug report

Describe the bug

I just deployed my medusa app backend on railway, and I have create a AWS S3 bucket and used it for coupe of days, only four images were putted on the bucket, and each one is around 200kb, when I check the billing, I found out that AWS charge me $2 per day for data transfer fee of 250GB, I am just want to know is this meeting expectations?

System information

Medusa version (including plugins):
Node.js version:
Database:
Operating system:
Browser (if relevant):

Steps to reproduce the behavior

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior

A clear and concise description of what you expected to happen

Screenshots

If applicable, add screenshots to help explain your problem

Code snippets

If applicable, add code samples to help explain your problem

Additional context

Add any other context about the problem here

[pevey]

That's extremely unusual. Medusa itself doesn't transfer data to and from s3, so you won't be able to troubleshoot without looking at the s3 logs, which are kind of a pain:

https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-s3-access-logs-to-identify-requests.html#using-s3-access-logs-to-identify-objects-access

Medusa stores the url, but calls to the url only happen from client browsers. Is this a test instance or a live store?
If it's a test instance, you should only see your IP. If it's a live store, maybe look for a stranger referrer, or maybe a mass number of requests from particular machines or regions, or other indications of hotlinking or abuse.

[ShivamJoker]

@rico-c someone must be dosing your S3 bucket, it's not a good idea to store images the way medusa suggests.

See more at #3938

[SGFGOV]

You can use a cdn service to kinikise hits yo the s3 bucket

…

On Sun, 28 May, 2023, 17:14 Shivam, ***@***.***> wrote: @rico-c <https://github.com/rico-c> someone must be dosing your S3 bucket, it's not a good idea to store images the way medusa suggests. See more at #3938 <#3938> — Reply to this email directly, view it on GitHub <#4188 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXEQJHEBFZTSVRTHMHJ2WIDXIM3CDANCNFSM6AAAAAAYRSJHIM> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- This message (including any attachments) may contain confidential, proprietary, privileged and/or private information. The information is intended to be for the use of the individual or entity designated above. If you are not the intended recipient of this message, please notify the sender immediately, and delete the message and any attachments. Any disclosure, reproduction, distribution or other use of this message or any attachments by an individual or entity other than the intended recipient is prohibited.   

[rico-c]

I found out the reason, because I used Microtica to deploy my backend and Microtica create some service automaticlly, and I close the project on Microtica but they did not terminate the resource on my AWS, so they still charging me.