>I just don't see a scenario where I say I'm just going to move from EFS to EBS or such. I chose EFS for a reason in the first place. How about when your team

>I just don't see a scenario where I say I'm just going to move from EFS to EBS or such. I chose EFS for a reason in the first place. How about when your team has terabytes of data stored in EFS that is only used sporadically and now you want to move it off? (maybe you started with EFS because it makes the most sense for your application but now you have a lot of older data that you still want to keep but don't necessarily need it to be accessed by the application anymore). Something like this helps justify how much you could save by starting that migration project. I do see your point though. IME, calculators like this are used more for management who are trying to estimate their budget for planning purposes (as in, I have a team that tells me they will need 5 TB of S3 storage, how much is that going to cost me?), not necessarily by devs making architecture decisions.