Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

607
Views
One or more parameter values were invalid: dynamodb
const dynamoDBConfig = require("../../config/dynamodb");
var AWS = require("aws-sdk");
AWS.config.update(dynamoDBConfig.aws_remote_config);
var dynamodb = new AWS.DynamoDB();

var params = {
    TableName : "year",
    KeySchema: [       
        { AttributeName: "year", KeyType: "HASH"},  //Partition key
        { AttributeName: "title", KeyType: "RANGE" }  //Sort key
    ],
    // other properties, it is the same every time
};
dynamodb.createTable(params, function(err, data) {
    if (err) {
        console.error("Unable to create table. Error JSON:", JSON.stringify(err, null, 2));
    } else {
        console.log("Created table. Table description JSON:", JSON.stringify(data, null, 2));
    }
});

You can notice my primary key is year, AttributeName: "year", KeyType: "HASH". If i just change table name too anything it workes fine. But, when i change,AttributeName: "year", KeyType: "HASH" to AttributeName: "anything", KeyType: "HASH" then it is generating error.

Unable to create table. Error JSON: {
  "message": "One or more parameter values were invalid: Some index key attributes are not defined in AttributeDefinitions. Keys: [test, title], AttributeDefinitions: [title, year]",
  "code": "ValidationException",
  "time": "2021-01-28T05:33:33.723Z",
  "requestId": "H4S1BQ5LB4G46S594UTBK4QMVRVVASDASSFGFGF4KQNSO5AEMVJF66Q9ASUAAJG",
  "statusCode": 400,
  "retryable": false,
  "retryDelay": 4.143072370771728
}

What is wrong, when I change the name of the primary key attribute?

Full params

var params = {
    TableName : "iam",
    KeySchema: [       
        { AttributeName: "test", KeyType: "HASH"},  //Partition key
        { AttributeName: "title", KeyType: "RANGE" }  //Sort key
    ],
    AttributeDefinitions: [       
        { AttributeName: "year", AttributeType: "N" },
        { AttributeName: "title", AttributeType: "S" }
    ],
    ProvisionedThroughput: {       
        ReadCapacityUnits: 10, 
        WriteCapacityUnits: 10
    }
};
over 4 years ago · Santiago Trujillo
1 answers
Answer question

0

The issue is cause by the fact that your KeySchema does not match AttributeDefinitions.

In the KeySchema you have test, while in your AttributeDefinitions you have year. This obviously leads to your issue, as you can't have AttributeDefinitions which are not part of your KeySchema, nor part of schema of Local or Global Secondary Indices.

over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!