AWS DevOps Engineer – Professional | Salesforce Admin (4x certified) | Writing about Kubernetes, Terraform & CI/CD
I moved from 4+ years in operations into Salesforce administration and AWS Cloud/DevOps, and I write about what I learn while building things. I hold 11 certifications, including AWS Certified DevOps Engineer – Professional, Salesforce Platform Administrator I & II, Platform App Builder, Agentforce Specialist, and GitHub Actions. I'm a Trailhead Double Star Ranger with 250+ badges. Here I post practical guides on Kubernetes, Docker, Terraform, CI/CD and DevSecOps, plus Salesforce DevOps with Copado and GitHub Actions. I'm open to Salesforce Admin, CRM support and DevOps/Cloud roles and can join immediately.
Markdown supported · ⌘↵ to post
OneLifeVibe
The distinction between the key policy and IAM policies is the part that deserves more attention. Many teams assume an IAM allow is enough, then spend time troubleshooting a denied decrypt that was actually blocked at the key policy. The envelope encryption note is also useful, because the 4 KB direct encrypt limit is easy to miss until a larger file fails. One addition that would help readers is a short note on testing key rotation and deletion in a non-production account first, since a scheduled deletion can still affect data that depends on the key.