> For the complete documentation index, see [llms.txt](https://brightercommand.gitbook.io/paramore-brighter-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://brightercommand.gitbook.io/paramore-brighter-documentation/outbox-and-inbox/brighterinboxsupport/dynamoinbox.md).

# Dynamo Inbox

The DynamoDb Inbox allows use of DynamoDb for Brighter's inbox support.

> **Reference** · Applies to **Brighter V10**

## Dynamo Inbox Usage

The DynamoDb Inbox allows use of DynamoDb for [Brighter's inbox support](/paramore-brighter-documentation/outbox-and-inbox/brighterinboxsupport.md). The configuration is described in [Dispatcher Configuration Reference](/paramore-brighter-documentation/brighter-configuration/brighterbasicconfiguration/dispatcherconfigurationreference.md#inbox).

For this we will need the *Inbox* packages for the DynamoDb *Inbox*.

**AWS SDK v3** (legacy support):

* **Paramore.Brighter.Inbox.DynamoDb**

**AWS SDK v4** (recommended for new projects):

* **Paramore.Brighter.Inbox.DynamoDb.V4**

The example on this page uses the v3 package's namespace, `Paramore.Brighter.Inbox.DynamoDB`; the v4 package's is `Paramore.Brighter.Inbox.DynamoDB.V4`.

See [AWS SQS Migration](/paramore-brighter-documentation/transports/awssqsconfiguration/awssqsmigratetov10.md#migrating-from-aws-sdk-v3-to-v4) for migration guidance between v3 and v4.

## Dynamo Inbox Options

`DynamoDbInboxConfiguration` names the table and nothing else. Everything about the connection — credentials, region, service URL — belongs to the `AmazonDynamoDBClient` you construct and pass to `DynamoDbInbox`.

| Option      | Type     | Default            | Description                                    |
| ----------- | -------- | ------------------ | ---------------------------------------------- |
| `TableName` | `string` | `"brighter_inbox"` | Names the DynamoDB table that holds the Inbox. |

`tableName` is also a constructor parameter, so `new DynamoDbInboxConfiguration("my_inbox")` and setting the property afterwards are the same thing.

The type also declares `Credentials` and `Region`. **Neither does anything**: the Inbox reads only `TableName`, and in the AWS SDK v3 package the two are get-only and never assigned, so they are always null. The v4 package declares them settable and still reads neither.

```csharp
using Amazon.DynamoDBv2;
using Microsoft.Extensions.DependencyInjection;
using Microsoft.Extensions.Hosting;
using Paramore.Brighter;
using Paramore.Brighter.Inbox.DynamoDB;
using Paramore.Brighter.ServiceActivator.Extensions.DependencyInjection;

private static IHostBuilder CreateHostBuilder(string[] args) =>
    Host.CreateDefaultBuilder(args)
        .ConfigureServices((hostContext, services) =>
        {
            ConfigureBrighter(hostContext, services);
        });

private static void ConfigureBrighter(HostBuilderContext hostContext, IServiceCollection services)
{
	var dynamoDb = new AmazonDynamoDBClient(credentials, new AmazonDynamoDBConfig { ServiceURL = "http://dynamodb.us-east-1.amazonaws.com" });

	services.AddConsumers(opt => 
	{
		opt.InboxConfiguration = new InboxConfiguration(new DynamoDbInbox(dynamoDb, new DynamoDbInboxConfiguration()));
		// ...
	});
}

// ...
```

Before Brighter 10.8.0 this configuration took effect only in an application that also called `AddProducers`; see [Global Inbox Configuration in a Consumer-Only Application](/paramore-brighter-documentation/outbox-and-inbox/brighterinboxsupport.md#global-inbox-configuration-in-a-consumer-only-application).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://brightercommand.gitbook.io/paramore-brighter-documentation/outbox-and-inbox/brighterinboxsupport/dynamoinbox.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.