I imagined that the tools were there for people with terabytes or petabytes of archives, not for me with just 60GB. The problem was that since my mental model had the maximum cost at less than a dollar, I didn't pay attention. During my investigation and even my visits to the AWS console, I saw plenty of tools and options for limiting retrieval rates and costs. Unfortunately for me, those options didn't exist when I first uploaded the archives, and switching to them would have involved the same sort of retrieval process I described in the post. Using Arq or S3's lifecycle policies would have made a huge difference in my retrieval experience. That said, here are some comments on specific issues raised in this thread: ![]() And getting them quickly was what I was paying the huge premium for. Even though it didn't increase my bill, it stopped me from getting my files quickly. The only angle I considered pursuing was the boto bug. I didn't request a refund because I frankly didn't think I had a case. ![]() It continues to be up to us to fully understand the products and associated liabilities we sign up for. This obviously makes me happy, but I would caution against taking this as a signal that Amazon will bail you out in case you mess up like I did. They also acknowledged the need to clarify the charges on their product pages. Some updates and clarifications are in order!įirst of all, I just woke up (it’s morning here in Helsinki) and found a nice email from Amazon letting me know that they had refunded the retrieval cost to my account.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |