aws-samples / aws-samples/lambda-refarch-mobilebackend

Unable to Create AWS CloudFormation Stack with Template Two

未关闭
#5 8 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
Objective-C
星标
587
派生
108
PR 合并指标
30 天内没有已合并 PR

描述

The example doesn't generate Cloud Formation Stack and give the errors described below :
(Thank for the response in advance)

Location : US East
Template Two : https://s3.amazonaws.com/awslambda-reference-architectures/mobile-backend/lambdafunctions.template

Reported Errors : LambdaDynamoStreamsApiFunction Error occurred while getting the object from S3. S3 Error Code: NoSuchKey. S3 Error Message: The specified key does not exist.

LambdaMobileSearchApiFunction Error occurred while getting the object from S3. S3 Error Code: NoSuchKey. S3 Error Message: The specified key does not exist.

LambdaMobileCoreApiFunction Error occurred while getting the object from S3. S3 Error Code: NoSuchKey. S3 Error Message: The specified key does not exist.

Used Keys :
"LambdaSourceBucket": {
"Type": "String",
"Description": "Name of S3 bucket where Lambda function packages are stored.",
"Default": "awslambda-reference-architectures"
},

```
"LambdaMobileSearchS3Key": {
"Type": "String",
"Default": "mobile-backend/cloudsearchapi.zip",
"Description": "Name of S3 key for ZIP with Lambda function package for querying CloudSearch."
},
"LambdaNotesApiS3Key": {
"Type": "String",
"Default": "mobile-backend/photonotesapi.zip",
"Description": "Name of S3 key for ZIP with Lambda function package for sending mobile data to DDB."
},
"LambdaDynamoStreamsS3Key": {
"Type": "String",
"Default": "mobile-backend/searchstreams.zip",
"Description": "Name of S3 key for ZIP with Lambda function package for sending data to CloudSearch."
}
```

贡献指南

打开贡献指南

调研方向

从链接的 S3 URL 中的 Template Two 开始,检查 Lambda 函数包引用,尤其是 LambdaMobileSearchS3Key、LambdaNotesApiS3Key 和 LambdaDynamoStreamsS3Key 的值。验证所引用的对象是否存在于已配置的 bucket 中,并确定 CloudFormation 报告 NoSuchKey 的原因;完成的标准是 template 可以在 US East 中创建 stack,且不会出现这些错误。

由索引模型根据 Issue 内容生成。

评估

技术栈
aws
领域
cloud, infrastructure
Issue 类型
缺陷
难度
4/5
预计耗时
3-5 天
活跃度
停滞
描述清晰度
需要澄清
新手友好度
25/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。