11–20 of 152 posts
All this automation is very well but this illustrates the dangers of running stuff on other's machines of unknown complexity and out of your own control, while having to pay for whatever may happen. Not for me, thanks.
Can you limit bandwidth with AWS? Also, why would the spreadsheet be calling these images every hour. Did you have the spreadsheet open? Does google do this call even when no one is viewing the spreadsheet?
That such a simple thing on your part could result in such an extreme and expensive result implies something is wrong with the design of the system you're using.
This was an extremely interesting article. I hope Google rectifies this type of behavior. This is actually pretty scary.
Can you limit bandwidth with AWS? Also, why would the spreadsheet be calling these images every hour. Did you have the spreadsheet open? Does google do this call even when no one is viewing the spreadsheet?
You can put a robots.txt in the bucket.
Plus you cannot put a robots.txt at s3.amazonaws.com so if the url is accessed through the https://s3.amazonaws.com/.... url, the robots.txt will not work.
This is the main reason I'd never use AWS to host anything public.
Can you limit bandwidth with AWS? Also, why would the spreadsheet be calling these images every hour. Did you have the spreadsheet open? Does google do this call even when no one is viewing the spreadsheet?
You can put a robots.txt in the bucket.
This is mentioned specifically in the article, in fact.
Can you limit bandwidth with AWS? Also, why would the spreadsheet be calling these images every hour. Did you have the spreadsheet open? Does google do this call even when no one is viewing the spreadsheet?
You can put a robots.txt in the bucket.
Can you limit bandwidth with AWS? Also, why would the spreadsheet be calling these images every hour. Did you have the spreadsheet open? Does google do this call even when no one is viewing the spreadsheet?
Not on S3, no.