Greetings!
We are implementing foreman in EC2 for one of our environments. Due to the
compliance we have for internal policy, our two environments cannot have
ANYTHING to do with one another. In tinkering with the EC2 integration,
foreman works fine wide open, however this breaks company policy…
Can someone please share the least required permissions for foreman to
function properly? For some reason when we lock, by policy, to a region,
foreman errors…
Any help is appreciated!
Thanks,
Austin