News for hackers. Stuff that matters.
Re:AWS Purity Test by jackson1442 on Friday January 27, 2023 @01:17PM (#34549628)
> Don't get me started on the API.

At least it's not the GCP API. Had to use that for some compliance automation once and still have nightmares about it.

Re:AWS Purity Test by kccqzy on Friday January 27, 2023 @01:28PM (#34549756)
Why not use the CLI though? The aws and gcloud CLI tools seem fine when I occasionally use them.
Re:AWS Purity Test by jackson1442 on Friday January 27, 2023 @01:57PM (#34550159)
Ah, read API as CLI (with AWS they're essentially the same).

The biggest problem with GCP's api/cli/sdk/console is they're not the same. There are things you can only do in the console, or have different grammars across CLI/SDK, or have different permission schemes across them. Add to that the intermixing of "IT Admin" and "Cloud Admin" roles due to all of your Google Groups also being IAM groups, and IAM being somehow tied into your G Suite admin area, it's just a confusing mess.

With AWS, the CLI is the API is the SDK. So if you can use one, you can use all of them very easily.

Re:AWS Purity Test by scarface74 on Friday January 27, 2023 @02:21PM (#34550479)
It’s all based on the same specification and all of the SDKs and the CLI are autogenerated.
Re:AWS Purity Test by ahtihn on Friday January 27, 2023 @03:26PM (#34551355)
CLIs are not great at showing you the operations that are available to you. Exploring what's possible is much easier with a GUI in my experience.