Hands-on guides on AWS, Kubernetes, Docker, Terraform, CI/CD and Salesforce DevOps by Robin Sishodia, AWS DevOps Professional and certified Salesforce Admin.
So far I have secured root, set a budget, turned on CloudTrail and CloudWatch, and added tags. All of that sits in one account. The next step is the structure around it: AWS Organizations. Why more th
Screens are how a Flow talks to the user. Admin II interviews ask about them because input, validation and navigation decide whether a Screen Flow is easy to use and safe to trust. The 4 Building Blo
Just shipped repo-health-report: a tiny, dependency-free Python tool that audits your GitHub repos through the REST API. It flags missing licenses, descriptions, topics and READMEs, plus pull requests
A Flow formula calculates a value from your data and variables, so you can skip extra Decision and Assignment elements. Admin II interviews ask about them because formulas keep Flows small, readable a
By now I have IAM, a budget, CloudTrail and CloudWatch. One more habit makes all of them easier to use: tags. When the bill rises or something looks odd, tags tell you what the resource is, who owns i
The Loop element lets a Flow work through a collection one record at a time. Admin II interviews ask about it because loops are where Flows either stay bulk-safe or hit governor limits. The 4 Loop Pi
Last time I looked at who changed things with CloudTrail. The next question is different: what is happening inside my resources right now? That is Amazon CloudWatch. What CloudWatch does Metrics: num
Create Records, Update Records and Delete Records are how a Flow changes data. Admin II interviews ask about them because small choices here decide whether a Flow is safe, fast and bulk-ready. The 3
This week I locked the root account and set a budget. Now the question that comes after both: when something changes in the account, how do I find out who did it, what they did and when? That is AWS C