1 Answer
- Newest
- Most votes
- Most comments
0
This is unintuitive but happend to me in the past. Most probably you are missing permissions to the Lambda that creates the SignedUrl... I know... AWS should throw an error when we are creating it, not when we are consuming it... but this fixed my problem then...
In the template, go to the Lambda that creates the SignedUrl and in the properties, add the following Policies:
- AWSLambdaVPCAccesExecutionRole
- AWSLambdaBasicExecutionRole
- S3CrudPolicy: BucketName: my-bucket-unique-name
I hope it helps!
answered a year ago
Relevant content
- asked 8 months ago
- asked a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 3 months ago