Granting someone or something that isn’t the senior admin permission to delete a volume is irresponsible.
Correct. Like I said this was the job of a senior admin.
They gave the AI the job of managing IaC for their environment. Then were shocked when the AI managed the environment incorrectly. This is absolutely not something you let a junior engineer anywhere near.
You seem to be suggesting that the AI should be able to do the job they gave it without being given the permission required for it to do. The thing about doing things in IT, is you need to have permissions to do the things you’re asked to do. So you have to make sure the person you give permissions to is reliable and knows what they’re doing. The AI did not.
They gave the AI the job of managing IaC for their environment. Then were shocked when the AI managed the environment incorrectly. This is absolutely not something you let a junior engineer anywhere near.
See, this is the piece of information I was missing. When the article says “routine tasks”, I didn’t think it meant “manage environment”.
In that case, I agree that it is an issue of trusting AI with something that it shouldn’t have been.
You seem to be suggesting that the AI should be able to do the job they gave it without being given the permission required for it to do.
No, I was simply mistaken about the job it was given. Like I said, all I had to work with was the tomshardware article, which doesn’t go into much detail. I didn’t know that the “routine task in staging” required permission to delete entire cloud volumes across all environments instead of just specific environment-scoped project tokens.
Obviously, if it’s tasked with managing all project environments and given the access to do so, that’s a timebomb. In this case, it was, until it blew up.
The thing about doing things in IT, is you need to have permissions to do the things you’re asked to do.
The thing about conversations on the Internet is you need to actually read the whole comment and realise that there may be some misunderstanding if the other party says things like “I can’t read the twitter link” and assumes it’s a junior dev job when you know it’s not. Then you could just point out the part they didn’t know without being condescending and assuming a fundamental lack of understanding of how IT works.
I’ve had more than enough instances of troubleshooting just which scopes my access token needs to be intimately familiar with the way permissions work. I personally tend to request the least amount required for a given task and only expand when needed and reasonable. It is my understanding that this is the best practice. It was my assumption that they had assigned permissions their agent didn’t need, because you generally don’t hand out “fuck up my prod system” rights.
Correct. Like I said this was the job of a senior admin.
They gave the AI the job of managing IaC for their environment. Then were shocked when the AI managed the environment incorrectly. This is absolutely not something you let a junior engineer anywhere near.
You seem to be suggesting that the AI should be able to do the job they gave it without being given the permission required for it to do. The thing about doing things in IT, is you need to have permissions to do the things you’re asked to do. So you have to make sure the person you give permissions to is reliable and knows what they’re doing. The AI did not.
See, this is the piece of information I was missing. When the article says “routine tasks”, I didn’t think it meant “manage environment”.
In that case, I agree that it is an issue of trusting AI with something that it shouldn’t have been.
No, I was simply mistaken about the job it was given. Like I said, all I had to work with was the tomshardware article, which doesn’t go into much detail. I didn’t know that the “routine task in staging” required permission to delete entire cloud volumes across all environments instead of just specific environment-scoped project tokens.
Obviously, if it’s tasked with managing all project environments and given the access to do so, that’s a timebomb. In this case, it was, until it blew up.
The thing about conversations on the Internet is you need to actually read the whole comment and realise that there may be some misunderstanding if the other party says things like “I can’t read the twitter link” and assumes it’s a junior dev job when you know it’s not. Then you could just point out the part they didn’t know without being condescending and assuming a fundamental lack of understanding of how IT works.
I’ve had more than enough instances of troubleshooting just which scopes my access token needs to be intimately familiar with the way permissions work. I personally tend to request the least amount required for a given task and only expand when needed and reasonable. It is my understanding that this is the best practice. It was my assumption that they had assigned permissions their agent didn’t need, because you generally don’t hand out “fuck up my prod system” rights.