Is there a list of all the AWS services and what the counterpart it may be for a self hosted open source solution?
Seems many of the actual services may have one.
AWS services explained in one line each
151–160 of 355 posts
Re: AWS services explained in one line each
#152> Lightsail: Amazon’s hosting provider (vps, dns, storage) Doesn't feel like accurate description for Lightsail, nor a useful one. Maybe something like "simplified deployment and billing for some AWS resources, including VPS, databases, DNS, and load balancers" (listing "storage" as something Lightsail does is kind of weird; of course, it does instance-attached block storage, you couldn't have a VPS without that. cri…
Sometimes I feel it is easier described by saying what its main competitor is.
Lightsail is basically AWS' version of Heroku and App Engine.
(i.e. a PAAS)
I wish Google would also do this. Many times on GCP's website or at Google Next you try to decipher what the product is that they are talking about, then you realise "ah, it is their version of S3, CloudFormation etc". If they just had said that at the start...
Of course, no company will do this, unfortunately.
Re: AWS services explained in one line each
#153Earlier 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…
You're absolutely right, and also absolutely missing his point. As a massive user of AWS for a long time, yes you can know exactly to the sub-detail line what you pay for, no you can absolutely not have an overview or good estimation of mapping what a change in your software stack / setup will cost or save you. Unless we're talking "remove an entire service" and then duh, yeah.
How is that different from if you ran all this stuff on prem?
Re: AWS services explained in one line each
#154Most sound about right except for Global Accelerator, which isn’t a way to run your apps on edges, it’s a way to route all your network traffic through the AWS edges. Make it a bit more reliable and faster, and has really cool load balancing and routing options.
Re: AWS services explained in one line each
#155Earlier 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.
If you set up your infrastructure with CloudFormation (as you should), you can get a cost estimation of how much your solution would cost. https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGui...
This is really terrible blanket advice, CF is one of AWS' worst products in my extensive experience with it (My team manages a ~$4 million monthly bill and locked into CF well before I joined). It has a number of significant limitations that aren't applied to terraform, it's pretty important to understand those tradeoffs if you're buying in.
Given that AWS supports terraform, it's really on them to provide a calculator for it as well. We're large enough that we just spent an obscene amount of money on employee time and effort to track our billing (lots of automated tagging), but until we did that it wasn't uncommon for a couple hundred thousand dollars of unnecessary charges to hit our bill every month.
Re: AWS services explained in one line each
#156Similar 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?
> Why does AWS use such convoluted language?
Because it's run by engineers (not a bad thing).
Re: AWS services explained in one line each
#157Earlier quoted context omitted.
If you set up your infrastructure with CloudFormation (as you should), you can get a cost estimation of how much your solution would cost. https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGui...
This is really terrible blanket advice, CF is one of AWS' worst products in my extensive experience with it (My team manages a ~$4 million monthly bill and locked into CF well before I joined). It has a number of significant limitations that aren't applied to terraform, it's pretty important to understand those tradeoffs if you're buying in. Given that AWS supports terraform, it's really on them to provide a calculat…
How is Terraform better than CF for AWS? What are these significant limitations? I also know of plenty of large enterprises that use CF.
Re: AWS services explained in one line each
#158Earlier quoted context omitted.
How is that a factual error? It didn't say that mounting was impossible, just that it isn't directly used for mounting. How did you conclude that it's done frequently throughout the industry? What percentage of S3 customers do you think does this? If I would have to guess I'd say less than 1%. But I am happy to learn I am wrong.
You are totally right, and your explanation is perfect. No need to bother. You could also mount gmail accounts as a filesystem.
I beg to differ.
I have already argumented against it, and provided evidence for my statement [0].
My argument is logically airtight.
Re: AWS services explained in one line each
#159Earlier quoted context omitted.
> CloudFormation (as you should) A lot of people use Terraform (my shop does) and I've found a good terraform setup way better than CF templates. You can do tags in Terraform too. You should be forced to use their already bad tooling just to get correct cost estimates.
Yet another reason to use native tooling. If you want to take advantage of AWS features - you have to use AWS features. Blame Hashicorp if they don’t have a similar feature.
Moving from Terraform to CloudForm is as pleasant as chewing glass, and the last thing we need is more AWS lock-in unless you're running an AWS consultancy.
Re: AWS services explained in one line each
#160Earlier quoted context omitted.
> CloudFormation (as you should) A lot of people use Terraform (my shop does) and I've found a good terraform setup way better than CF templates. You can do tags in Terraform too. You should be forced to use their already bad tooling just to get correct cost estimates.
Yet another reason to use native tooling. If you want to take advantage of AWS features - you have to use AWS features. Blame Hashicorp if they don’t have a similar feature.
I'm training on AWS and part of an AWS infra team - but we use Terraform partially because we intend to have production support at our company for all three big US clouds, and want the IaC layer to be uniform.
I get that there are times to dive all the way in, but there is still a part of me that says "Is this what the Internet is now?"