dynamo | expressive DynamoDB library for Go | AWS library

I have written terraform code which:

1. Creates IAM Role
2. Creates lambda functions and attaches the above created role
3. Dynamo DB table creation
4. Creates API gateway, resources and adds POST method with lambda integration.

The first 3 steps works well. However while creating and configuring the API gateway, I am encountering below error in resource aws_api_gateway_integration & aws_lambda_permission, where I am trying to attach the lambda function "save_course" to the POST method under "courses" resource

I have a method in an AWS Lambda which receives a completed list of items. It processes those items and then inserts them into a Dynamo DB table. Order of processing or inserting into the DB does not matter.

I'm looking for the most thread-safe, yet easy to understand manner in which to make this run faster; Either by using async await or something other (likely parallel?) operations.

I was thinking Parallel.ForEach() but that seems a bit heavy. Is there a simpler, more obvious way?

This might be a very silly question when it comes to dynamo DB.

Well,to summarize the issue I have a dynamoDB set up in my project.
(FYI, I have not setup a local dynamodb, I'm trying to connect to my remote db in lab environment)
The configuration for which is as follows:

I have a table in Dynamo

Now I am trying to add a new row(product) in the table. when I am trying this with API gateway, I created a resource and created a post method with request mode Product

Request Model

When I used enhanced client to put but it throws class cast exception.

I have aws dynamo db table as follows.

Now I want to filter it as follows.

For that I used the following code and i get 0 results in my code.what's wrong with my code.how to fix it?

I'm trying to setup a lambda to receive a dynamo dB stream and publish these database changes to an sns topic. I'm not sure how I would publish a message from the lambda to my topic using the cdk. Are there any examples of this?

I have a DynamoDB table where I'm aggregating CDN access logs. Specifically I want to track:

For a given customer (all of whose requests can be identified from the URL being downloaded), how many bytes were delivered on their behalf each day?

I have a primary partition key on customer and a primary sort key on time_bucket (day). This way given a customer I can say "find all records from March 1st, 2021 to March 31st, 2021" for instance. So far, so good

The issue arose when I wanted to start deleting old data. Anything older than 5 years should be dropped from the database.

Because the partition key isn't on time_bucket, there's no easy way to say "retrieve all records for May 25th, 2016". Doing so requires a scan instead of a query, and scans are out of the question (unusably slow given how much data I'm handling)

I don't want to swap the partition key and sort key for two reasons:

• When processing new data to add to the Dynamo table, all new CDN logs will be for the same day. This means that my table will be unbalanced: every write operation made during a single day will hit the same partition key
• If I wanted to pull a month's worth of data for a single customer I would have to make 30 queries -- one for each day of the month. This gets even worse when pulling a year of data, or 3 years of data

My first thought was "just add an index on the time_bucket column", but when I tried this I got an error:

Attribute Name is duplicated: time_bucket (Service: AmazonDynamoDBv2; Status Code: 400; Error Code: ValidationException; Request ID: PAN9FVSEMBBJT412NCV013VURNVV4KQNSO5AEMVJF66Q9ASUAAJG; Proxy: null)

It seems like DynamoDB does not allow you to create an index on the sort key. So what's the proper solution here?

As per DynamoDB's documentation it supports both key-value and document-oriented properties of NoSQL even though other NoSQL databases fall only under only one type either Key-Value or Document or Graph or Column-oriented

Also it says

Amazon DynamoDB is "built on the principles of Dynamo"[3] and is a hosted service within the AWS infrastructure. However, while Dynamo is based on leaderless replication, DynamoDB uses single-leader replication.

And Dynamo is

A set of techniques that together can form a highly available key-value structured storage system[1] or a distributed data store

So when DynamoDB is built on the principles of Dynamo which is not related to Document-oriented storage system and since it is mandatory for a developer to create a primary key and the table requires key for every item how and in what sense DynamoDB is called a Document-oriented database ?

Can a DB fall under two types of NoSQL databases in the first place ?