Error while using PutItem API of DynamoDB

[diptanu]

I have a some code like this -

svc := dynamodb.New(&aws.Config{Region: "us-east-1"})
    svc.Endpoint = "http://localhost:8080"
    params := &dynamodb.PutItemInput{
        Item: map[string]*dynamodb.AttributeValue{
            "Foo": {
                S: aws.String("value"),
            },
            "Bar": {
                S: aws.String("value"),
            },
        },
        TableName: aws.String("DataBaseName"),
    }
    resp, err := svc.PutItem(params)

I get the following error - Unmarshal failed decoding JSON RPC error response invalid character 'p' after top-level value. I am running code from master of aws-sdk-go

Any pointers to what the issue is? My hunch is the parameters I am setting for the PutItem API is incomplete.

[lsegal]

Passing LogLevel: 1, LogHTTPBody: true to your configuration should provide information on what the SDK was unable to parse.

My guess is that DynamoDB Local is generating an error and returning an invalid JSON response (probably plaintext indicating the failure).

[lsegal]

Also note that you should not set Endpoint directly on service, use configuration instead:

svc := dynamodb.New(&aws.Config{Region: "us-east-1", Endpoint: "http://localhost:8080"})

[diptanu]

Here is what I am seeing in the logs with LogLevel set to 1

---[ CANONICAL STRING  ]-----------------------------
POST
/

accept-encoding:identity
host:localhost:8080
x-amz-date:20150608T183625Z
x-amz-target:DynamoDB_20120810.PutItem

accept-encoding;host;x-amz-date;x-amz-target
2f23609c1bc208b32ac6a2a23f21b7e7d35d0b6bf5ffb6b569bba75b7b5d97d6
---[ STRING TO SIGN ]--------------------------------
AWS4-HMAC-SHA256
20150608T183625Z
20150608/us-east-1/dynamodb/aws4_request
ae1068d59cba3179e22e92ac7adf92cf42817058398596ad3a7d780dbbb05e20
-----------------------------------------------------
---[ REQUEST POST-SIGN ]-----------------------------
POST / HTTP/1.1
Host: localhost:8080
User-Agent: aws-sdk-go/0.6.1
Content-Length: 82
Accept-Encoding: identity
Authorization: AWS4-HMAC-SHA256 Credential=.../20150608/us-east-1/dynamodb/aws4_request, SignedHeaders=accept-encoding;host;x-amz-date;x-amz-target, Signature=a25d8746a5aa0d0458ef117ddf081dd48d2ec1a5e2096c38b5ffe493268d5168
Content-Type: application/x-amz-json-1.0
X-Amz-Content-Sha256: 2f23609c1bc208b32ac6a2a23f21b7e7d35d0b6bf5ffb6b569bba75b7b5d97d6
X-Amz-Date: 20150608T183625Z
X-Amz-Target: DynamoDB_20120810.PutItem

{"Item":{"Foo":{"S":"value"},"Bar":{"S":"value"}},"TableName":"DataBaseName"}
-----------------------------------------------------
---[ RESPONSE ]--------------------------------------
HTTP/1.1 404 Not Found
Content-Length: 19
Content-Type: text/plain; charset=utf-8
Date: Mon, 08 Jun 2015 18:36:25 GMT

404 page not found

-----------------------------------------------------
Unmarshal failed decoding JSON RPC error response invalid character 'p' after top-level value

[marcosnils]

@diptanu seems like your post is going to localhost:8080 according to the Host header. Do you have a dynamodb listening there?

[diptanu]

Yes it should go to localhost:8080, since I am using dynamodb local.

[marcosnils]

@diptanu seems like something is not working with your dynamo local. What do you get if you issue a curl localhost:8080/ ?

[marcosnils]

BTW: I'm also using dynamo local in my projects and this is how initialize my dynamo connection:

func Server() *dynamodb.DynamoDB {
        server := dynamodb.New(config.Current.DynamoConfig)                                                                                                                                                    

        return server
}

Where DynamoConfig is:

        Current.DynamoConfig = &aws.Config{Credentials: Current.DynamoAwsCredentials,
                Endpoint: Current.DynamoHost,
                Region:   Current.DynamoRegion,
        } 

You need to specify credentials even though those are fake.

[diptanu]

Well, the ports were messed up, sorry I got rat-holed into believing the client was not able to parse the response from Dynamo Local. Closing this issue.

[diptanu]

@marcosnils I thought the SDK could use on-instance keys if I don't specify any credentials. It would be really nice if that's how it worked even if it doesn't work like that today.

[lsegal]

@diptanu I would recommend opening a feature request on the Amazon DynamoDB forums if you would like to see support for anonymous access in Local.