Open levgorbunov1 opened 9 months ago
We should stick to IAM resource naming convention:
For simpler stacks we should separate resource relating to different AWS components into different tf files.
For more complex stacks, separation should be done by functionality groupings.
Can make a module for state management infrastructure so we don't keep repeating ourselves.
User Need
As a developer I want to better understand weaknesses of our cloud platform terraform so that it can be improved
Acceptance Criteria: