I Configure Cloud. But I’m Called an Architect

My title says Architect. My work says something else.

I configure cloud services. I set up IAM, networking, scaling, environments.

This is critical work. But is this architecture?

Why Do I Believe I’m an Architect?

There are familiar reasons.

1. I’m certified by cloud vendors

AWS, Azure, GCP — I’ve cleared the exams.

What this actually means:

I understand cloud capabilities and configurations. This is P5 execution capability.

2. I design cloud landscapes

VPCs, subnets, security groups, load balancers.

What this actually means:

I’m defining infrastructure setup. Not system behavior.

3. I work with microservices and APIs

I deploy services, configure gateways, manage scaling.

What this actually means:

I’m enabling execution. Not defining interaction logic across the enterprise.

4. My role is titled “Cloud Architect”

The organization recognizes the responsibility.

What this actually means:

The title reflects scope of delivery. It does not confirm the presence of architecture.

Want to read more?

Subscribe to architecturerating.com to keep reading this exclusive post.

Subscribe Now