91–100 of 355 posts
How to waste money in just one line each... Simplifying AWS like this only serves to normalize wasteful spending on the "cloud". This works when the economy is great....not so much when businesses are looking to trim costs.
Earlier quoted context omitted.
> Heck, at any given moment it's unexplainably hard to tell exactly which AWS services are you actually using, and being billed for. Did you actually look at the billing page? Here's a screenshot of my billing page: https://imgur.com/a/DQAxgRY It meticulously breaks out per-service costs across whatever dimension you want. "EC2-Other" is rolled up in the chart, but it's broken out by each individual item further down…
Isn’t that exactly what the person you replied to said? You’re showing what you’ve been charged for previously. That part works, at a certain level of detail. That doesn’t show what you are being charged for right now , nor does it help you predict what your total costs will be at the end of the month.
Similar to https://expeditedsecurity.com/aws-in-plain-english/ Why does AWS use such convoluted language? Is it because they're dominant and it adds friction to moving to another provider?
Useful and interesting but some of them are either blank or, well: > After reading it over and over again, i still have no idea what it does. > Some quantum thing. It’s in preview so I have no idea what it is. > in preview so no idea.
Yes.. some of them I have absolutely no clue on what it does. They might serve some edgecase specific for that domain. There are a few services in preview which I cannot see for myself what it does. I will try to update and correct services as soon as I have more info (or somebody can provide it to me)
The main feature is the on-demand cloud hosted version of the robotics simulator gazebo ( http://gazebosim.org/ ) that allows you to run your robot's code in a 3d physics environment. You can then take that tested/verified code and deploy it over the air via our fleet management features to your actual robot.
Earlier quoted context omitted.
Isn’t that exactly what the person you replied to said? You’re showing what you’ve been charged for previously. That part works, at a certain level of detail. That doesn’t show what you are being charged for right now , nor does it help you predict what your total costs will be at the end of the month.
I'm not sure why that would be terribly important though? A month of delay in optimizing your services isn't going to make or break an average company.
Earlier quoted context omitted.
You can get cost breakdown on a more granular level by taking advantage of tagging. You can tag your resources logically and get a break down by tag. The biggest mistake I see is that people jump into AWS whole hog without doing the research or if they are large enough, hiring someone who knows what they are doing. https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2...
I don't understand why I even need to do manual things such as "tagging" (besides learning what that even means in AWS) to find out something as simple as why I'm being charged as much as I'm being charged. I'm sorry. It's inexcusable.
Just like AWS is not understandable to someone new, I feel the modern front end ecosystem is royal cluster but yet and still thousands of people understand it after a 12 week boot camp.
Earlier quoted context omitted.
> Heck, at any given moment it's unexplainably hard to tell exactly which AWS services are you actually using, and being billed for. Did you actually look at the billing page? Here's a screenshot of my billing page: https://imgur.com/a/DQAxgRY It meticulously breaks out per-service costs across whatever dimension you want. "EC2-Other" is rolled up in the chart, but it's broken out by each individual item further down…
Isn’t that exactly what the person you replied to said? You’re showing what you’ve been charged for previously. That part works, at a certain level of detail. That doesn’t show what you are being charged for right now , nor does it help you predict what your total costs will be at the end of the month.
Earlier quoted context omitted.
Isn’t that exactly what the person you replied to said? You’re showing what you’ve been charged for previously. That part works, at a certain level of detail. That doesn’t show what you are being charged for right now , nor does it help you predict what your total costs will be at the end of the month.
You bring up a good point - it would be a good idea for AWS to set some sensible max budget defaults for new accounts to prevent surprises. Since they don't, if you are literally so concerned with your current costs for this month, you can set a budget and alerts for whatever you want, so that you don't exceed some cost. Also, they show you your current cost for this month, up until the moment, as well as a daily bre…
I didn’t say anything about this at all. It would certainly be a nice feature, and one people have asked for since the very beginning of AWS.
> Since they don't, if you are literally so concerned with your current costs for this month, you can set a budget and alerts for whatever you want, so that you don't exceed some cost.
Again, this is a strawman. This isn’t a response to anything I said.
If you’re trying to understand how much a new deployment on AWS is costing you, and find ways to optimize that, you don’t care about the total budget of the account, or having some auto shutoff. You need detailed, real-time information from Amazon, which I’ve never seen in the console.
It’s been several years since I’ve had to be digging around in the billing console, so I have no stake in this discussion and things might have changed. Based on other comments being made around here, I really doubt anything significant has changed.
I was just trying to clarify a comment you completely misunderstood.