aws-sam-cli

I have a new project that requires a relatively small amount of services, maybe 10 or less (and therefore it is not economical to place each in a separate project repository). Each service will be defined as an AWS::Serverless::Function via SAM Template. My question is: what is the recommended way to organize or structure such a project? Currently the structure is: |- src |- lambdas |- service-one |- stuff |- package.json |- service-two |- stuff |- package.json |- other-stuff |- test |- package.json Is there a way to avoid having each lambda act as its own sub-project with unique package.json

I am trying to run an AWS Lambda project locally on Ubuntu. When I run the project with AWS SAM Local it shows me this error: Error: Running AWS SAM projects locally requires Docker. Have you got it installed? I had trouble installing it on Fedora. When I followed the Docker postinstall instructions I managed to get past this issue. https://docs.docker.com/install/linux/linux-postinstall/ I had to: Delete the ~/.docker directory; Create the "docker" group; Add my user to the "docker" group; Logout and back in again; Restart the "docker" daemon. I was then able to run the command: sam local

In cloudformation, AWS::ApiGateway::Method has a boolean property ApiKeyRequired . How can i achieve the same in SAM ? I know that we can enable using explicit swagger Configuration. which is like this { "swagger": "2.0", "info": { "version": "1.0", "title": { "Ref": "AWS::StackName" } }, "x-amazon-apigateway-api-key-source": "HEADER", "paths": { "/": { "get": { "x-amazon-apigateway-integration": { "httpMethod": "POST", "type": "aws_proxy", "uri": { "Fn::Sub": "arn:aws:apigateway:${AWS::Region}:lambda:path/2015-03-31/functions/${GetHelloWorld.Arn}/invocations" } }, "responses": {}, "security":

I am trying to execute a couple of async requests from a lambda function. The first call resolveEndpoints() succeeds and the second fails with 2017/11/03 17:13:27 Function oauth.callbackHandler timed out after 3 seconds 2017/11/03 17:13:27 Error invoking nodejs6.10 runtime: io: read/write on closed pipe The handler is: exports.callbackHandler = async (event, context, callback) => { context.callbackWaitsForEmptyEventLoop = false; let endpoints: any = await resolveEnpoints(); config.accessTokenUri = endpoints.token_endpoint; let tokenRequestPath = `http://localhost:7001${event.path}?code=${event

I've set up an api gateway/aws lambda pair using AWS sam local and confirmed I can call it successfully after running sam local start-api I've then added a local dynamodb instance in a docker container and created a table on it using the aws cli But, having added the code to the lambda to write to the dynamodb instance I receive: 2018-02-22T11:13:16.172Z ed9ab38e-fb54-18a4-0852-db7e5b56c8cd error: could not write to table: {"message":"connect ECONNREFUSED 0.0.0.0:8000","code":"NetworkingError","errno":"ECONNREFUSED","syscall":"connect","address":"0.0.0.0","port":8000,"region":"eu-west-2",