1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
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!
답변함 일 년 전
관련 콘텐츠
- AWS 공식업데이트됨 7달 전
- AWS 공식업데이트됨 일 년 전
- AWS 공식업데이트됨 일 년 전