Internal Server Error on deployed app

[INRIX-Joshua-Kidd]

I have managed to deploy a simple hello world app with zappa, however when I visit the URL the app is deployed to all I get is:

{"message": "Internal server error"}

When I tried to run zappa tail I receive the error:

botocore.errorfactory.ResourceNotFoundException: An error occurred (ResourceNotFoundException) when calling the DescribeLogStreams operation: The specified log group does not exist.

Context

I am using a manually created AWS role to handle the zappa application.

My app.py looks like:

import logging
from flask import Flask

app = Flask(__name__)
logging.basicConfig()
logger = logging.getLogger(__name__)
logger.setLevel(logging.DEBUG)

@app.route('/', methods=['GET'])
def lambdahandler(event=None, context=None):
    logger.info('Lambda function invoked index()')

    return 'hello from Flask!'

if __name__ == '__main__':
    app.run()

Expected Behavior

I expect the api to return the text "Hello World!"

Actual Behavior

The API returns

{"message": "Internal server error"}

Steps to Reproduce

The app is live at https://hapcnbby7h.execute-api.us-west-2.amazonaws.com/production

Your Environment

• Zappa version used: 0.45.1
• Operating System and Python version: Windows 10, python 3.6
• The output of pip freeze: argcomplete==1.9.2 base58==0.2.4 boto3==1.7.5 botocore==1.10.5 certifi==2018.4.16 cfn-flip==1.0.3 chardet==3.0.4 click==6.7 docutils==0.14 durationpy==0.5 Flask==0.12.2 future==0.16.0 hjson==3.0.1 idna==2.6 itsdangerous==0.24 Jinja2==2.10 jmespath==0.9.3 kappa==0.6.0 lambda-packages==0.19.0 MarkupSafe==1.0 placebo==0.8.1 python-dateutil==2.6.1 python-slugify==1.2.4 PyYAML==3.12 requests==2.18.4 s3transfer==0.1.13 six==1.11.0 toml==0.9.4 tqdm==4.19.1 troposphere==2.2.1 Unidecode==1.0.22 urllib3==1.22 virtualenv==15.2.0 Werkzeug==0.14.1 wsgi-request-logger==0.4.6 zappa==0.45.1
• Your zappa_settings.py:

  { "production": { "app_function": "app.app", "aws_region": "us-west-2", "profile_name": "default", "project_name": "zappa-test", "runtime": "python3.6", "s3_bucket": "zappa-ds-app-0000", "manage_roles": false, "role_name":"zappa-datascience", "keep_warm": false } }

[vvalorous]

Do you the right IAM permissions for the role you are assigning to the Lambda ? Usually it's a sign of Cloudwatch logs are not included in the permissions list.

[INRIX-Joshua-Kidd]

Do you know what the minimum permissions I will need to add are? I'm pretty sure that I have added sufficient permissions.

[INRIX-Joshua-Kidd]

Found the issue, possibly due to the fact I manually created a role. I had to go into my API gateway > settings and manually add in "CloudWatch log role ARN"