top of page

I Configure AWS. But I’m Called an Architect.

What I Actually Do

I configure AWS.


I configure VPCs. I configure subnets. I configure security groups. I configure IAM roles.


I configure EC2. I configure S3. I configure RDS. I configure Lambda. I configure ECS or EKS. I configure API Gateway. I configure load balancers.


I configure monitoring, logging, backup, scaling, and deployment pipelines.


I define environments. I set cloud policies. I design network zones. I configure access. I select managed services. I create infrastructure templates.


I coordinate with developers, DevOps teams, security teams, database teams, testing teams, and operations teams.


This is important work. But important work is not the same as architecture.


                Want to read more?

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

                Enterprise Intelligence

                Transforming Strategy into Execution with Precision and Real Intelligence

                bottom of page