Hands-on guides on AWS, Kubernetes, Docker, Terraform, CI/CD and Salesforce DevOps by Robin Sishodia, AWS DevOps Professional and certified Salesforce Admin.
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
Get Records is how a Flow reads data. Admin II interviews ask about its filters, sort order and null checks because a badly built one is the most common cause of slow or broken Flows. The 4 Settings
Yesterday I locked down the root account and noted "keep billing alerts up to date". Today is the other half of the front door: making sure a forgotten resource never turns into a surprise bill. AWS B
Decisions send a flow down the right path. Assignments change values along the way. Admin II interviews ask about both because almost every real Flow uses them. The 2 Elements Element What it does
Every AWS account starts with one identity that can do everything: the root user. IAM policies cannot restrict it, so if someone gets in, there is no safety net. Before building anything else, lock it
On Day 2 I wrote a least-privilege policy for one S3 bucket. The next question is who gets to use it. For people, that's a user or group. For servers and apps, it should be a role, so nothing long-liv