Where to save images within AWS? [closed]
I was discussing with friends about the best way to store files in amazon.
I believed that an s3 bucket was the best way to save static files as images from a website.
But friends said that it is not the best way to work with s3 because of the high cost of having this image requested many times.
I need to know the best place to save images that will be rendered inside my site (which is inside an EC2 instance).
Could someone clarify this doubt? Saving images inside the S3 in sites that have many requests is expensive?
amazon-web-services amazon-s3 amazon-ec2
closed as primarily opinion-based by AdrianHHH, greg-449, Kaushik Nayak, pirho, EdChum Nov 18 '18 at 9:38
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
I was discussing with friends about the best way to store files in amazon.
I believed that an s3 bucket was the best way to save static files as images from a website.
But friends said that it is not the best way to work with s3 because of the high cost of having this image requested many times.
I need to know the best place to save images that will be rendered inside my site (which is inside an EC2 instance).
Could someone clarify this doubt? Saving images inside the S3 in sites that have many requests is expensive?
amazon-web-services amazon-s3 amazon-ec2
closed as primarily opinion-based by AdrianHHH, greg-449, Kaushik Nayak, pirho, EdChum Nov 18 '18 at 9:38
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
I was discussing with friends about the best way to store files in amazon.
I believed that an s3 bucket was the best way to save static files as images from a website.
But friends said that it is not the best way to work with s3 because of the high cost of having this image requested many times.
I need to know the best place to save images that will be rendered inside my site (which is inside an EC2 instance).
Could someone clarify this doubt? Saving images inside the S3 in sites that have many requests is expensive?
amazon-web-services amazon-s3 amazon-ec2
I was discussing with friends about the best way to store files in amazon.
I believed that an s3 bucket was the best way to save static files as images from a website.
But friends said that it is not the best way to work with s3 because of the high cost of having this image requested many times.
I need to know the best place to save images that will be rendered inside my site (which is inside an EC2 instance).
Could someone clarify this doubt? Saving images inside the S3 in sites that have many requests is expensive?
amazon-web-services amazon-s3 amazon-ec2
amazon-web-services amazon-s3 amazon-ec2
asked Nov 18 '18 at 6:16
Renato Souza de OliveiraRenato Souza de Oliveira
5772816
5772816
closed as primarily opinion-based by AdrianHHH, greg-449, Kaushik Nayak, pirho, EdChum Nov 18 '18 at 9:38
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as primarily opinion-based by AdrianHHH, greg-449, Kaushik Nayak, pirho, EdChum Nov 18 '18 at 9:38
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
For storing static files like images AWS S3 is one of the best option.
S3 is one of the cheapest cloud storage, you won't be charged for the number of times it's read, only amount of outbound traffic will bbe charged. For get requuest/put request there is also a charge, but you shouldn't need it as per my understanding, you can clarify your use case more precisely. You can also calculate the price here.
Find all the storage services AWS offers here: https://aws.amazon.com/products/storage/
Glacier is not at all appropriate for serving static content -- it's intended for cold storage (hence the name), and allows for neither public nor real-time access to stored data. I've removed it from your answer, as the rest of your answer is largely correct.
– duskwuff
Nov 18 '18 at 7:01
yeah, Glacier is more appropriate for data archive, not useful for this use case.
– Mostafiz Rahman
Nov 18 '18 at 7:09
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
For storing static files like images AWS S3 is one of the best option.
S3 is one of the cheapest cloud storage, you won't be charged for the number of times it's read, only amount of outbound traffic will bbe charged. For get requuest/put request there is also a charge, but you shouldn't need it as per my understanding, you can clarify your use case more precisely. You can also calculate the price here.
Find all the storage services AWS offers here: https://aws.amazon.com/products/storage/
Glacier is not at all appropriate for serving static content -- it's intended for cold storage (hence the name), and allows for neither public nor real-time access to stored data. I've removed it from your answer, as the rest of your answer is largely correct.
– duskwuff
Nov 18 '18 at 7:01
yeah, Glacier is more appropriate for data archive, not useful for this use case.
– Mostafiz Rahman
Nov 18 '18 at 7:09
add a comment |
For storing static files like images AWS S3 is one of the best option.
S3 is one of the cheapest cloud storage, you won't be charged for the number of times it's read, only amount of outbound traffic will bbe charged. For get requuest/put request there is also a charge, but you shouldn't need it as per my understanding, you can clarify your use case more precisely. You can also calculate the price here.
Find all the storage services AWS offers here: https://aws.amazon.com/products/storage/
Glacier is not at all appropriate for serving static content -- it's intended for cold storage (hence the name), and allows for neither public nor real-time access to stored data. I've removed it from your answer, as the rest of your answer is largely correct.
– duskwuff
Nov 18 '18 at 7:01
yeah, Glacier is more appropriate for data archive, not useful for this use case.
– Mostafiz Rahman
Nov 18 '18 at 7:09
add a comment |
For storing static files like images AWS S3 is one of the best option.
S3 is one of the cheapest cloud storage, you won't be charged for the number of times it's read, only amount of outbound traffic will bbe charged. For get requuest/put request there is also a charge, but you shouldn't need it as per my understanding, you can clarify your use case more precisely. You can also calculate the price here.
Find all the storage services AWS offers here: https://aws.amazon.com/products/storage/
For storing static files like images AWS S3 is one of the best option.
S3 is one of the cheapest cloud storage, you won't be charged for the number of times it's read, only amount of outbound traffic will bbe charged. For get requuest/put request there is also a charge, but you shouldn't need it as per my understanding, you can clarify your use case more precisely. You can also calculate the price here.
Find all the storage services AWS offers here: https://aws.amazon.com/products/storage/
edited Nov 18 '18 at 7:01
duskwuff
147k19177233
147k19177233
answered Nov 18 '18 at 6:38
Mostafiz RahmanMostafiz Rahman
5,64333654
5,64333654
Glacier is not at all appropriate for serving static content -- it's intended for cold storage (hence the name), and allows for neither public nor real-time access to stored data. I've removed it from your answer, as the rest of your answer is largely correct.
– duskwuff
Nov 18 '18 at 7:01
yeah, Glacier is more appropriate for data archive, not useful for this use case.
– Mostafiz Rahman
Nov 18 '18 at 7:09
add a comment |
Glacier is not at all appropriate for serving static content -- it's intended for cold storage (hence the name), and allows for neither public nor real-time access to stored data. I've removed it from your answer, as the rest of your answer is largely correct.
– duskwuff
Nov 18 '18 at 7:01
yeah, Glacier is more appropriate for data archive, not useful for this use case.
– Mostafiz Rahman
Nov 18 '18 at 7:09
Glacier is not at all appropriate for serving static content -- it's intended for cold storage (hence the name), and allows for neither public nor real-time access to stored data. I've removed it from your answer, as the rest of your answer is largely correct.
– duskwuff
Nov 18 '18 at 7:01
Glacier is not at all appropriate for serving static content -- it's intended for cold storage (hence the name), and allows for neither public nor real-time access to stored data. I've removed it from your answer, as the rest of your answer is largely correct.
– duskwuff
Nov 18 '18 at 7:01
yeah, Glacier is more appropriate for data archive, not useful for this use case.
– Mostafiz Rahman
Nov 18 '18 at 7:09
yeah, Glacier is more appropriate for data archive, not useful for this use case.
– Mostafiz Rahman
Nov 18 '18 at 7:09
add a comment |