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!
回答済み 1年前
関連するコンテンツ
- AWS公式更新しました 1年前
- AWS公式更新しました 1年前