这通常是由于Lambda函数的执行角色权限不正确导致的。您可以确保Lambda函数的执行角色具有所需的AWS服务和API的访问权限。代码示例:
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "Stmt1516358518000",
"Effect": "Allow",
"Action": [
"logs:CreateLogGroup",
"logs:CreateLogStream",
"logs:PutLogEvents"
],
"Resource": "arn:aws:logs:*:*:*"
},
{
"Sid": "Stmt1516358555000",
"Effect": "Allow",
"Action": [
"s3:GetObject"
],
"Resource": "arn:aws:s3:::example-bucket/*"
}
]
}
在此示例中,我们向执行角色添加了logs:CreateLogGroup、logs:CreateLogStream、logs:PutLogEvents和s3:GetObject访问权限。您可以根据实际情况修改此示例以添加所需的其他权限。