Q. Size/shape of AWS you owned (accounts, regions, scale, on-call) ================================================================== Across my experience at IBM, Xebia, OpenText, and Diehl Metering, I have worked on AWS environments from both a platform engineering and security architecture perspective, covering design, operations, and governance. My role was not limited to provisioning — I owned the reliability, security, and operational behaviour of production systems. Overall Environment Shape ------------------------- - Multi-account AWS environments using landing zone concepts - Multi-region deployments for high availability and resilience - Mix of cloud-native and hybrid (AWS + datacenter) architectures - Enterprise workloads across banking, retail, and industrial platforms IBM – Hybrid and DR Foundations ------------------------------- At IBM, I worked in hybrid environments integrating AWS with on-premise datacenters. - Supported disaster recovery between AWS and datacenter - Worked closely with on-ground teams for recovery execution - Part of a 2-week rotational on-call model handling production issues This gave me strong exposure to real incident handling and recovery scenarios. Xebia – Architecture and Scale ------------------------------ At Xebia, I worked on designing and delivering AWS platforms for enterprise customers. - Built multi-region architectures for high availability - Supported retail platforms handling millions of transactions per day - Created reusable infrastructure patterns for multiple regions The focus here was on scalability and consistent architecture design. OpenText – Production Operations -------------------------------- At OpenText, I owned production AWS environments for enterprise customers. - Managed EC2, RDS, S3, IAM, and networking services - Responsible for platform stability, scaling, and issue resolution - Focused on reducing incidents and improving operational reliability Diehl Metering – Governance and Security ---------------------------------------- At Diehl Metering, I worked on structured multi-account AWS environments. - Landing zone setup with guardrails and governance controls - IAM role-based access and least-privilege enforcement - Centralised logging and monitoring - Part of a 1-week per month on-call rotation supporting production systems This role focused more on governance, compliance, and secure platform operations. Operational Ownership --------------------- Across these roles, I was responsible for: - Infrastructure provisioning using Terraform - CI/CD-driven deployments - IAM and security controls - Monitoring and alerting - Backup and disaster recovery - On-call support and incident handling Architectural Perspective ------------------------- From a solutions and security perspective, I focus on: - Designing for failure (multi-region, DR readiness) - Enforcing least privilege - Ensuring infrastructure is reproducible - Embedding security into delivery workflows Summary ------- I have worked across hybrid and cloud-native AWS environments, operating at enterprise scale with strong requirements for reliability, security, and compliance. My approach is to build and operate systems that are: - resilient - secure - and operationally predictable