Along with the General Guides, it might be helpful to add a niche guide section, which is broken down by AWS service. Happy to issue a PR with some quality tutorials as an example.

If you'd like to have your company represented and are using Komiser please give formal written permission below via a comment and email to contact@komiser.io.

We will need a URL to a svg or png logo, a text title and a company URL.

The limit parameter for the scan method is defined as:

limit – Used to limit the number of results returned

However, this is not really what limit does. The Boto3 doc for limit in part reads:

Limit (integer) -- The maximum number of items to evaluate (not necessarily the number of matching items). If DynamoDB processes the number of items up to the limit while processing the results,

Is there anyway to specify log group name to be AppSync's api name instead of API ID. I see this code is used to fetch the loggroupname

LogGroupName: { 'Fn::Join': ['/', ['/aws/appsync/apis', { 'Fn::GetAtt': [logicalIdGraphQLApi, 'ApiId'] }]] },

is there a way to make this API name instead. In cloudwatch - pointing at correct appsync loggroup becomes little difficult as we have to know s

Currently, the README.md file lists all tables with their full table comment.

I'm putting a lot of info in some of my table descriptions, including SQL code blocks. These render rather badly in the comment column of the central Tables table, which treats markdown just a little different.

Perhaps the Tables table should only use the first paragraph of each table description.

E.g.

We need to implement integration/unit tests for internal/transport package.

Wanted to get this package added to awesome go but it is missing a couple of things in the Readme

godoc link to the repo
coverage service link to the repo
goreportcard link to the repo

데모영상을 보니 DynamoDB의 프라이머리 키 명칭이 해쉬키라고 되어 있는데 혼란을 피하기 위해 명칭을 공식 문서와 동일하게 파티션 키로 하는게 어떨까 합니다.

http://docs.aws.amazon.com/ko_kr/amazondynamodb/latest/developerguide/HowItWorks.CoreComponents.html#HowItWorks.CoreComponents.PrimaryKey

In the documentation (at -dbPath option) it states that the current working directory of dynamo-local is:

<project root>/node_modules/serverless-dynamodb-local/dynamodb

In my env I see that the directory is:

<project root>/node_modules/dynamodb-localhost/dynamodb/bin

I am not sure if this is something local to my env (I am running on Windows) or an error in the documentation. Migh

Would it make sense to update the 'joi' dependency to use '@hapi/joi' instead which is forked from the original project. The former also depends on older versions of hoek/topo.

If you guys think it's a good idea I can try to submit a pull request.

I tried to run the setup function, do I need to create an API token?

backend git:(master) ✗ sil setup

  Error --------------------------------------------------

     Server responded with status code 401:
{"message":"Bad
     credentials","documentation_url":"https://

I would love to see a tutorial on how to do per function IAM role to added to the website.
This https://serverless.com/framework/docs/providers/aws/guide/iam/#custom-iam-roles but explained in a much better way :)

Hi! 👋

On the documentation it states the following:

Contrary to what you'd expect, association information is always contained on the object specifying the association, even if it seems like the association has a foreign key. This is a side effect of DynamoDB's structure: it's very difficult to find foreign keys without an index. Usually you won't find this to be a problem, but it does me

@chrisbennight missed a badge!

Typos are marked with bold:

1. Tables
   Tables represent one-to-one mappings to your DynamoDB tables. Then contain information about your table's name, primary keys, indexes, and more. They are also used organize and coordinate operations between entities. Tables support a number of methods that allow you to interact with your entities including performing queries, scans, batch gets a