Its 2025, why the clickops?

Amazon Web Services (AWS) Why does ClickOps Still Haunt us in 2025?

Ive been setting up Amazon QuickSight Spaces. I’ve got 13 groups synced via SCIM, IAM Identity Center configured, and a beautiful infrastructure-as-code setup ready to go.

Then I discover: QuickSight Spaces have *no API*.
Zero. Nada. Console-only.

So after automating user provisioning, group sync, and role assignments, I now have to manually click through the console to create 7 Spaces and configure their permissions. One. By. One.

This is the opposite of the famous 2002 Bezos API Mandate that made AWS what it is today. Remember rule #5? “All service interfaces must be designed from the ground up to be externalizable.”

Why does this matter?
• No repeatability - Can’t recreate in another region/account
• No version control - Configuration lives in screenshots
• No testing - Can’t validate in dev before prod
• No automation - Manual process every time
• No disaster recovery - Hope you documented everything

Everything-as-code isn’t just a buzzword. It’s about reliability, repeatability, and reducing human error. When we’re forced back into ClickOps for critical configuration, we lose all of that.
AWS: Please eat your own dogfood. Your customers are trying to follow your own best practices.

Hi @mrpackethead,
Thank you for your feedback; you are correct in that currently API’s are not available for the new Agentic AI features that have recently been introduced to the platform. To my understanding; this will not be a permanent limitation and is on their roadmap for future updates.
Either way, I’ll go ahead and tag this as a feature request to promote visibility to the AWS support team!

This shoudl be a day one thing.