Live data from Hacker News

AI for AWS Documentation

awsdocsgpt.com

101–110 of 134 posts

Re: AI for AWS Documentation

#101
post #96

It doesn’t distinguish between HTTP api gateway and REST api gateway. When asked how to create a private HTTP gateway it happily tells you how to do it , but it’s actually impossible.

Dumb embedded cave man here… I thought those two things were basically the same but REST had an idea of statelessness. They are different how?

Re: AI for AWS Documentation

#102
post #93

Asked it whether you should use a shared vpc: Made this up as reason for dedicated vpc: “Better performance: By using dedicated hardware, you have better control over the performance of your instances in the VPC. This can be beneficial for applications that have stringent performance requirements.”

I think ChatGPT and LLM models in general are more suited for "What is xyz" or "How is xyz done" family of questions. Basically a smart search engine. Beyond that it will simply have the output/personality of a person with rote-memory.

Even though it has better access to AWS Docs…

Still a language model and not a facts model.

Re: AI for AWS Documentation

#103
post #13

It invented an answer for something that AWS actually can't do right now. https://imgur.com/a/0IYZ2WV

That is basically status quo for LLMs right now.

They're all so eager to please they will basically never say "that's actually not possible", and invent some plausibly sounding bullshit.

For beginners who are struggling to tell the difference between 1/ how to do something that's possible, 2/ how to do something that SHOULD be possible but just currently isn't, and 3/ how to do something that is RIDICULOUS and shouldn't even ever be possible, ChatGPT is worse than nothing :(

Re: AI for AWS Documentation

#104

This is exactly the kind of software that people should be making. Even if this one is bad, the concept is very sound. I want to have a specialist AI that is trained to help me learn how to use the software. 100% what should be happening. General AI should know how to do stuff too but having an specialist AI implies that the company/group of people/person is making sure to tune the model. Just an IMO.

MDN implemented an "AI explains" feature, and the reception is extremely negative.

https://github.com/mdn/yari/issues/9208

Re: AI for AWS Documentation

#106
post #34
post #12

Well, I'll pass. Prompt: how to connect a lambda function to an RDS instance and query it safely? 1. Configure your RDS instance for outbound connections to AWS Lambda. This step involves ensuring that your DB instance is in a public subnet on your VPC and that the instance's "PubliclyAccessible" property is set to true.

Lol yeah no thanks. This is one of things that makes me nervous about using LLMs. If the internet contains shitty solutions for solving a problem, it’s going to recommend shitty solutions. Inexperienced folks won’t know better. There’s also the thing where that’s a positive feedback look and we overflow the worlds corpus with garbage.

> If the internet contains shitty solutions for solving a problem, it’s going to recommend shitty solutions.

Have you ever noticed how the dumbest people tend be be the loudest, most confident, and most eager to share their opinions? Those are the voices that trained ChatGPT.

It’s a hard pass for me, but I fear I’m going to be forced to used it because the dumbest half of humanity will view it as a peer and use it for everything.

Re: AI for AWS Documentation

#107
post #54

Earlier quoted context omitted.

Asking the same question to Chatgpt To connect a Lambda function to an RDS (Relational Database Service) instance and query it safely, you can follow these general steps: 1. Configure your Lambda function's execution role: Ensure that your Lambda function has the necessary permissions to access the RDS instance. The role should include the `AWSLambdaVPCAccessExecutionRole` and the appropriate RDS permissions. 2. Plac…

This all looks about right, but how would somebody without aws experience be able to validate it without making a mess?

ChatGPT doesn't need to provide perfect AWS solutions for people without AWS experience; the onus is on the human to do the work necessary on their side to be sure of the solution it produces.

It should be thought of as a time saving tool for experts (and people willing to put the work in), not a magic button for lazy people.

Re: AI for AWS Documentation

#108
post #54

Earlier quoted context omitted.

This all looks about right, but how would somebody without aws experience be able to validate it without making a mess?

It still isn't tho, this will work for testing, maybe, but each lambda will be it's own connection and that will exhaust db resources real fast, you're supposed to have a pooling proxy between lambdas and RDS.

And it's in the docs, RDS Proxy, launched in 2020, before GPT training cut-off

https://aws.amazon.com/about-aws/whats-new/2020/06/amazon-rd...

Re: AI for AWS Documentation

#109
post #97

Earlier quoted context omitted.

This to me is why I don't use ChatGPT. Every time I use it I get answers that are questionable in validity. I'd say that 3/4 of my questions have returned incorrect answers at least partially. Maybe 10% are wildly incorrect with the remainder being partially incorrect. So if it is wrong with MOST of the questions that I am able to validate myself, then how can I trust it on the questions that I am unable to validate…

Why’d he be so reluctant to confess to using ChatGPT? And why would he continue using it despite constant feedback that his performance was getting so much worse?

It's like gambling for some people... No self control.
Post reply on HN