Lu Hong

Not sure if it is the same issue for you. But I found it confusing when using secrets manager console. The console defaults the secrets to be either a key-value...

Used the provided template to reproduce the issue. The Lambda permissions created by SAM looks like this: ``` { "Version": "2012-10-17", "Id": "default", "Statement": [ { "Sid": "LogToWatchS3CreateObjectPermission-F3WNVM1OUAMX", "Effect": "Allow",...

You can use CloudFormation export and import to pass the parameters from one stack to a different stack: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-stack-exports.html To deal with resource limit issue, CloudFormation recommends to use nested...

### AWS CodeBuild CI Report * Result: SUCCEEDED * [Build Logs](https://ii24ukr9o4.execute-api.us-east-1.amazonaws.com/Prod/buildlogs?key=47cd762a-fcfd-4148-a42e-c5610b4931bb%2Fbuild.log) (available for 30 days) *Powered by [github-codebuild-logs](https://serverlessrepo.aws.amazon.com/applications/arn:aws:serverlessrepo:us-east-1:277187709615:applications~github-codebuild-logs), available on the [AWS Serverless Application Repository](https://aws.amazon.com/serverless/serverlessrepo/)*