A library IT team wants permissions that start from AWS-authored baselines and then tailor narrower access when those baselines are too broad, while still aiming for least privilege. How should they think about managed versus custom policies?
Select an answer to reveal the explanation.
Short Explanation
AWS managed policies are ready-made permission packs; custom policies are ones you write when you need a tighter fit. Start with managed when it is close enough, then craft custom JSON when you must lock actions and resources down — least privilege still wins either way.
Full Explanation
AWS managed policies are created and maintained by AWS; customer managed (custom) policies are created by the account owner for specific needs. Practitioners often begin with managed policies for common job functions, then use custom policies to restrict actions and resources further. Least privilege applies regardless of policy type.