G2

Atharva P.

Cloud BI Engineer

Enterprise (> 1000 emp.)

7/24/2026

"Standardized, Self-Service AWS Provisioning with Strong Governance"

4/5

What do you like best about AWS Service Catalog?

What I like most about AWS Service Catalog is how it helps organizations standardize and govern infrastructure provisioning across teams, while still giving developers a self-service way to request approved resources. Platform teams can publish pre-approved products—such as VPCs, EC2 instances, RDS databases, or even complete application stacks—which helps maintain consistency and supports security and compliance.

I also appreciate its seamless integration with Infrastructure as Code, since it makes it easier to enforce organizational standards without slowing down development teams. Review collected by and hosted on G2.com.

What do you dislike about AWS Service Catalog?

The initial setup requires careful planning around portfolios, products, launch constraints, IAM permissions, and version management. For smaller organizations, this can feel more complex than necessary—especially if you only have a few AWS users or limited governance requirements. Review collected by and hosted on G2.com.

What problems is AWS Service Catalog solving and how is that benefiting you?

AWS Service Catalog helps address infrastructure governance and standardization challenges.

For example, our platform team created approved infrastructure templates for VPCs, ECS services, RDS databases, and EC2 environments using CloudFormation. Rather than provisioning resources manually each time, developers could launch these standardized products through Service Catalog with predefined configurations and built-in security controls.

As a result, we reduced configuration drift, sped up environment provisioning, and ensured that every deployment stayed compliant with our organizational policies. Review collected by and hosted on G2.com.