AWS: The Pain Points

one way or the other you know aws aren't going to tell you when the service is ready for you um you know it will it will be released and it will evolve over time and it will get it'll accrue what you need it to or it {ts:393919} won't and then you'll find another way to deal with … easier but if your requirements are too specific not supported unlikely to be supported within the time frame that you need maybe you need to compose your own service not for everything but for this particular thing and to sort of illustrate that i'm going to borrow and adapt some slides that adrian cockcroft presented a couple of years ago when … heavy-handed and it just doesn't it's not consistent with the promise of elasticity in the cloud it is a it is an outlier which is why with so many of these things go looking it's not hard right if you uh read the fine print here if you choose to create a nat gateway in your vpc you were charged for … if you're paying for support trusted advisor it gives you a few tips around how to optimize cost but that assumes your workload's already already live as does cost explorer which will use past information to um to determine a sort of a three-month forecast but again that's lagging lagging information and what happens this month might not be what what happened last month and probably just a final piece of advice for me is if you are doing this profiling to focus on the big ticket items um the things that you know will drive higher cost um trying to get you know something that is three percent of your estimate to a 90 accuracy is probably not not time well spent