The documentation surrounding dynamo local claims that the keys do not matter in the usage notes section:
http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tools.DynamoDBLocal.html On Dec 13, 2014 9:40 AM, "Willem Jiang" <willem.ji...@gmail.com> wrote: > What’s kind of test mode do you use? > The exception message is "The security token included in the request is > invalid”, can you double check if your security token is set rightly? > > -- > Willem Jiang > > Red Hat, Inc. > Web: http://www.redhat.com > Blog: http://willemjiang.blogspot.com (English) > http://jnn.iteye.com (Chinese) > Twitter: willemjiang > Weibo: 姜宁willem > > > > On December 12, 2014 at 10:29:42 PM, Scott Gentry (sgent...@gmail.com) > wrote: > > I'm attempting to write some json data to a Dynamo Table with blueprint > XML. > > > > While in testing mode I was looking to send data to dynamo local with the > > following snippet: > > > > > > uri="aws-ddb://localhost:8000?tableName=schedule&accessKey=Fake&secretKey=Fake" > > /> > > > > However, when this portion of the route is reached, I receive the > following > > error: > > > > 2014-12-11 17:24:00,354 | ERROR | mix-5.3.0/deploy | > BlueprintCamelContext > > | ?? | 124 - org.apache.camel.camel-blueprint - 2.13.2 | Error occurred > > during starting Camel: CamelContext(camel-10) due Failed to create route > > getSchedule at: >>> > > > To[aws-ddb://localhost:8000?tableName=schedule&accessKey=Fake&secretKey=Fake] > > <<< in route: Route(getSchedule)[[From[seda:ingestSchedule]] -> > > [Recipient... because of Failed to resolve endpoint: > > aws-ddb://localhost:8000?accessKey=Fake&secretKey=Fake&tableName=schedule > > due to: The security token included in the request is invalid. (Service: > > AmazonDynamoDB; Status Code: 400; Error Code: > UnrecognizedClientException; > > Request ID: 54R236QHN2JR3AIRFLOLCKU0RJVV4KQNSO5AEMVJF66Q9ASUAAJG) > > org.apache.camel.FailedToCreateRouteException: Failed to create route > > getSchedule at: >>> > > > To[aws-ddb://localhost:8000?tableName=schedule&accessKey=Fake&secretKey=Fake] > > <<< in route: Route(getSchedule)[[From[seda:ingestSchedule]] -> > > [Recipient... because of Failed to resolve endpoint: > > aws-ddb://localhost:8000?accessKey=Fake&secretKey=Fake&tableName=schedule > > due to: The security token included in the request is invalid. (Service: > > AmazonDynamoDB; Status Code: 400; Error Code: > UnrecognizedClientException; > > Request ID: 54R236QHN2JR3AIRFLOLCKU0RJVV4KQNSO5AEMVJF66Q9ASUAAJG) > > > > From the examples I have seen working with the local DB, the keys do not > > matter, and this should work. > > > > In addition, is there built in support (yet) for working with JSON? I > know > > it hasn't been around for very long, and I don't see options which seem > to > > indicate it is baked into the endpoint yet. > > > > Respectfully, > > > > Scott > > > >
