AWS & Cloud Infrastructure
Cloud architecture, IAM, CloudWatch, EC2, S3, VPC, CloudFormation, operations and cost awareness.
CLOUD ENGINEERING / SECURITY / AUTOMATION
I build cloud systems that are secure by design.
I'm Clyde Bunyan, a cloud and security professional with 10+ years in IT. My work spans AWS, Microsoft Azure, identity, cloud observability and intelligent automation.
Practical engineering.
Thoughtful security.
Thoughtful security.
Clyde Bunyan ↗Cloud & Security
01 / A LITTLE ABOUT ME
Curious about how things work.
Committed to making them better.
My career has taken me from infrastructure support and enterprise administration to cloud security and engineering. I focus on turning technical requirements into reliable systems, clear documentation and actionable security improvements.
Alongside professional engineering work, I develop independent cloud and security demonstrations and contribute to BunyanMatrix , a separate cloud consulting initiative.
02 / WHAT I WORK WITH
A versatile toolkit.
One engineering mindset.
Microsoft Cloud & Identity
Azure infrastructure, Microsoft Entra ID, Microsoft 365, access governance and security assessments.
Security & Threat Modeling
Security requirements, identity controls, threat-informed implementation guidance and remediation.
Automation & DevOps
Agentic documentation, Python workflows, CI/CD, APIs and repeatable infrastructure processes.
03 / SELECTED WORK
Projects where ideas
turn into systems.
Selected professional and independent technical work. Professional examples are intentionally generalized to protect internal details.
Agentic Documentation Automation
A documentation workflow combining Bitbucket Pipelines, Python and Claude AI. It analyzes repository changes, generates technical documentation and routes updates through a reviewable pull request.
- Baseline documentation across five source repositories
- Jira-linked change documentation workflow
- SHA-based change detection to avoid unnecessary AI calls
Read project overview
Challenge. Keep developer documentation aligned with a changing codebase without relying on manual updates.
Approach. Two complementary pipelines generate baseline system documents and feature-specific documentation. Generated changes land in a separate documentation repository for human review.
Evidence. Controlled proof-of-concept pipeline tests passed. This is not a claim of production rollout.
Approach. Two complementary pipelines generate baseline system documents and feature-specific documentation. Generated changes land in a separate documentation repository for human review.
Evidence. Controlled proof-of-concept pipeline tests passed. This is not a claim of production rollout.
AWS CloudWatch Omni & Cost Visibility
Cloud observability and cost visibility work focused on understanding application health, spotting operational anomalies and establishing clearer investigation paths in AWS.
- CloudWatch observability for application behavior
- Cost Explorer, Budgets and anomaly detection approach
- Dev environment scope and cost guardrails
Read project overview
Focus. Operational visibility and cost investigation are related but distinct concerns.
Approach. Use AWS billing tools to identify service-level spend and CloudWatch observability to investigate application behavior. Keep the trial scoped to a development environment.
Disclosure. The available written artifact is an implementation blueprint; production rollout details and measured outcomes are not publicly asserted.
Approach. Use AWS billing tools to identify service-level spend and CloudWatch observability to investigate application behavior. Keep the trial scoped to a development environment.
Disclosure. The available written artifact is an implementation blueprint; production rollout details and measured outcomes are not publicly asserted.
Microsoft 365 Security Assessment
A structured, read-only Microsoft 365 security review with a written assessment and an Excel remediation tracker. A separate fictional case study demonstrates the reporting format.
- Identity and tenant security review
- Prioritized findings and remediation steps
- Sanitized demonstration material only
Read project overview
Purpose. Translate configuration observations into clear security findings and an actionable improvement plan.
Deliverables. A private assessment report and an Excel remediation tracker were prepared. A fictional customer scenario was created separately for public demonstration.
Privacy. No actual tenant settings, customer identity or sensitive findings are published here.
Deliverables. A private assessment report and an Excel remediation tracker were prepared. A fictional customer scenario was created separately for public demonstration.
Privacy. No actual tenant settings, customer identity or sensitive findings are published here.
ServiceNow & Azure Machine-to-Machine Integration
Implemented and documented application-to-application OAuth flows between ServiceNow and Azure, with client credentials, token validation and machine identity mapping for authenticated API access.
- Azure-issued token validation and JWT claim checks in ServiceNow
- Outbound ServiceNow OAuth client credentials flow to Azure
- Machine-user mapping and permission-aware REST API access
Read project overview
Challenge. Enable application-to-application access between two enterprise platforms without relying on interactive user login.
Approach. Configure separate inbound token validation and outbound client-credentials paths, including OIDC metadata, JWT claim checks, machine-user mapping and API authorization.
Validation. The implementation guide defines token acquisition and authenticated API test cases. Specific production results are not publicly asserted.
Scope. Client-secret OAuth is documented. A separate custom CA certificate or mutual TLS implementation is not claimed.
Approach. Configure separate inbound token validation and outbound client-credentials paths, including OIDC metadata, JWT claim checks, machine-user mapping and API authorization.
Validation. The implementation guide defines token acquisition and authenticated API test cases. Specific production results are not publicly asserted.
Scope. Client-secret OAuth is documented. A separate custom CA certificate or mutual TLS implementation is not claimed.
04 / FOUNDATION
Built on experience.
Strengthened by learning.
10+
Years of experience across infrastructure, technical operations, cloud and security.
EDUCATION
MSc, Computer Science / IT
Gujarat University · 2017
Bachelor of Computer Applications
Xavier Institute · 2014
CERTIFICATIONS
Credentials listed from my career records. Current validity can be verified with the issuing organizations.
AWS Certified Solutions Architect – AssociateAWS / SAA-C03
Microsoft Azure Solutions Architect ExpertMicrosoft / AZ-305
Microsoft Azure Administrator AssociateMicrosoft / AZ-104
Oracle Cloud Infrastructure Architect AssociateOracle / 2023
Fortinet NSE 1 & NSE 2Security fundamentals
CyberArk Trustee & IBM Cybersecurity FundamentalsIdentity and security
05 / LET'S CONNECT
Have something
interesting in mind?
Open to conversations about cloud engineering, identity, security and thoughtful automation.