'Invalid endpoint' when Lambda invokes DynamoDB

[MCLDG-zz]

'Invalid endpoint' when Lambda invokes DynamoDB

[sanathkr]

Ah, so region is not being passed to docker somehow. How are you configuring your AWS credentials?

[MCLDG-zz]

I've tried it with 2 credentials: one with a default region, one without. Result is the same.

$ aws configure
AWS Access Key ID [****************etc]: 
AWS Secret Access Key [****************etc]: 
Default region name [us-east-1]: 
Default output format [None]: 

Error is:

Invalid endpoint: https://dynamodb..amazonaws.com: ValueError
Traceback (most recent call last):
  File "/var/task/calc-airmile-lambda.py", line 36, in handler
    dynamodb = boto3.resource('dynamodb' )
  File "/var/runtime/boto3/__init__.py", line 92, in resource
    return _get_default_session().resource(*args, **kwargs)
  File "/var/runtime/boto3/session.py", line 389, in resource
    aws_session_token=aws_session_token, config=config)
  File "/var/runtime/boto3/session.py", line 263, in client
    aws_session_token=aws_session_token, config=config)
  File "/var/runtime/botocore/session.py", line 836, in create_client
    client_config=config, api_version=api_version)
  File "/var/runtime/botocore/client.py", line 71, in create_client
    verify, credentials, scoped_config, client_config, endpoint_bridge)
  File "/var/runtime/botocore/client.py", line 281, in _get_client_args
    verify, credentials, scoped_config, client_config, endpoint_bridge)
  File "/var/runtime/botocore/args.py", line 79, in get_client_args
    timeout=(new_config.connect_timeout, new_config.read_timeout))
  File "/var/runtime/botocore/endpoint.py", line 273, in create_endpoint
    raise ValueError("Invalid endpoint: %s" % endpoint_url)
ValueError: Invalid endpoint: https://dynamodb..amazonaws.com

[sanathkr]

I just tried with nodejs and python. I get AWS_REGION and AWS_DEFAULT_REGION populated with nodejs4.3 runtime, but not with python2.7.

As a workaround, can you set region when you call sam local?
Ex: AWS_REGION=us-east-1 sam local start-api

I will continue to dig into the problem

[nitzien]

Workaround worked for me.