Ashishkumar Pandey
08/18/2021, 7:45 AMFrank
[logs:*, lambda:*, iam:*, api-gateway:*, sns:*, …]
actions on *
resources - use this strategy if you have ur own AWS account for development and don’t want to mistakenly create irrelevant resources (ie. EC2, RDS, NAT Gateway, etc)
3. Grant relaxed permissions upfront, and use the Access Analyzer to narrow down the policy.
4. Move the policies to a separate IAM role for CloudFormation to assume. You can pass that role to SST CLI via --role-arn
Frank
Ashishkumar Pandey
08/18/2021, 3:19 PMFrank