How to add SES permission to LambdaExecutionRole
See original GitHub issueI want to add SES permission to the LambdaExecutionRole so that I can send emails. I want to allow my Lambda Function to be able to use SES.
I also think it would make sense to have a feature like amplify [add|update|remove] ses
Issue Analytics
- State:
- Created 3 years ago
- Reactions:6
- Comments:14 (5 by maintainers)
Top Results From Across the Web
Lambda execution role - AWS Documentation
Add permissions for any services that your function calls with the AWS SDK, and for services ... Grant least privilege access to your...
Read more >Lambda using assumed-role instead of execution role
This IAM policy is only allowing ses:SendTemplatedEmail access for the resource arn:aws:ses:region:xxxx:identity/email .
Read more >Build Serverless Contact Forms for Amazon S3 Static ... - Secnix
1. Setup Amazon Simple Email Service (SES) for sending email 2. Create IAM role (AWS Lambda execution role) to allow access to AWS...
Read more >aws_lambda_permission | Resources | hashicorp/aws
Specify Lambda permissions for API Gateway REST API ... (Optional) This parameter is used when allowing cross-account access, or for S3 and SES....
Read more >How do I allow my Lambda execution role to ... - YouTube
How do I allow my Lambda execution role to access my Amazon S3 bucket?
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Not sure if it’s relevant to others but I think the current facility we have is pretty decent for me, for this use case, making SES work from lambda. Just edit the function/name/src/custom-policies.json and add:
(Obviously have something better than * as resource). Make sure that this file is in version control so that you can manually revert it back in case something overwrites it. I don’t think basic
amplify function update
touches this file though?I’m marking this as an enhancement for the CLI to provide a way to specify custom policies for a function so that it doesn’t get overwritten on a next
amplify update function
.