2 Answers
- Newest
- Most votes
- Most comments
0
Hi,
the simplest way is to use a naming convention like https://cjrequena.com/2020-06-05/aws-naming-conventions-en but where you would call $Environment to first position in the name and give it a different value for each of your developers.
Then, you will authorize in IAM policies with Resource:"service: DevPrefix*" to allow your devs to do what they want on their resources (i.e. those whose names start with their prefix)
AWS Iam Identity Center and AWS Organizations are the next step but they are more involving but go much further (multi-account)
Best,
Didier
Relevant content
- asked 8 months ago
- asked 8 months ago
- asked 3 months ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 days ago
Thanks. Can you share some good blog post on these as I didnt understand fully what you tried to say as I am not that advanced in IAM.