Amazon DynamoDB Client

Amazon DynamoDB is a serverless, fully managed NoSQL database. It supports both key-value and document data models, which lets you have a flexible schema for your data. This client lets you manage tables and indexes, and read, write, query and scan items, including with transactions.

For more information, see the Amazon DynamoDB documentation.

The Amazon DynamoDB extension is based on AWS Java SDK 2.x. It’s a major rewrite of the 1.x code base that offers two programming models (Blocking & Async).

The Quarkus extension supports two programming models:

  • Blocking access using URL Connection HTTP client (by default), the Apache 5.x HTTP client, the Apache HTTP client (deprecated) or the AWS CRT-based HTTP client

  • Asynchronous programming based on JDK’s CompletableFuture objects and the Netty HTTP client or the AWS CRT-based HTTP client

In this guide, we see how you can get your REST services to use Amazon DynamoDB locally and on AWS.

Prerequisites

To complete this guide, you need:

  • JDK 21+ installed with JAVA_HOME configured appropriately

  • an IDE

  • Apache Maven 3.8.1+

  • Docker, to run Amazon DynamoDB locally with Dev Services and to run the tests

  • Optionally, GraalVM or Mandrel installed to build a native executable

No AWS account is required: Dev Services and the local Floci container provide everything you need. You only need an AWS account and the AWS Command Line Interface if you want to deploy to AWS.

Start Floci automatically with Dev Services

The easiest way to start working with Amazon DynamoDB is to run a local instance using Dev Services. Dev Services starts a Floci container in dev and test modes, and configures the client to use it, so you don’t need an AWS account.

The container listens on a random port, so you never hard-code an endpoint. It is labelled quarkus-dev-service-floci and shared between the Quarkus applications running in dev mode. Refer to Dev Services for Amazon Services for the provider selection, the container configuration and the init scripts.

Start Floci manually

You can also start a Floci container yourself:

docker run --rm --name floci --publish 4566:4566 -d floci/floci:latest-compat

This starts a Floci instance that is accessible on port 4566. Floci exposes all the services it emulates on this single endpoint.

The latest-compat image ships the AWS CLI, already configured to target the local endpoint. Run the provisioning commands of this guide inside the container, with docker exec floci aws …​. You do not need to install or configure the AWS CLI on your host.

You can check the region, the credentials and the endpoint used inside the container:

docker exec floci env | grep AWS_

The CLI uses the region us-east-1, the credentials test / test, and the endpoint http://localhost:4566 seen from inside the container. An application running on the host reaches Floci at http://localhost:4566; an application running in another container must use the container name, for example http://floci:4566, and the containers must share a Docker network.

Solution

The application built here allows to manage elements (fruits) stored in Amazon DynamoDB.

It uses the synchronous client first, then the asynchronous client in Going asynchronous.

We recommend that you follow the instructions in the next sections and create the application step by step. However, you can go right to the completed example.

Clone the Git repository: git clone https://github.com/quarkusio/quarkus-quickstarts.git, or download an archive.

The solution is located in the amazon-dynamodb-quickstart directory.

Walkthrough

Creating the Maven project

First, we need a new project. Create a new project with the following command:

mvn io.quarkus.platform:quarkus-maven-plugin:4.0.0.Beta1:create \
    -DprojectGroupId=org.acme \
    -DprojectArtifactId=amazon-dynamodb-quickstart \
    -DclassName="org.acme.dynamodb.FruitResource" \
    -Dpath="/fruits" \
    -Dextensions="rest-jackson,amazon-dynamodb"
cd amazon-dynamodb-quickstart

This command generates a Maven structure importing the Quarkus REST and Amazon DynamoDB Client extensions. After this, the amazon-dynamodb extension has been added to your pom.xml, along with quarkus-rest and quarkus-rest-jackson.

The Amazon DynamoDB extensions are a component of the Quarkus platform, and the generated pom.xml already imports their BOM through it, which is the recommended setup.

Due to differing release schedules, the Quarkus platform may not include the latest Quarkus Amazon Services release. If you need features from a newer release, replace the generated quarkus-amazon-services-bom import with the Quarkus Amazon Services BOM:

<dependency>
    <groupId>io.quarkiverse.amazonservices</groupId>
    <artifactId>quarkus-amazon-services-bom</artifactId>
    <version>4.0.0.Beta3</version>
    <type>pom</type>
    <scope>import</scope>
</dependency>

The command also generates a FruitResourceTest class and a FruitResourceIT class that call the hello endpoint of the generated resource. The next section replaces that resource: delete these two files, or update them to match the endpoints you create.

Creating the REST resource

First, let’s create the Fruit bean as follows:

package org.acme.dynamodb;

import java.util.Map;
import java.util.Objects;

import io.quarkus.runtime.annotations.RegisterForReflection;
import software.amazon.awssdk.services.dynamodb.model.AttributeValue;

@RegisterForReflection
public class Fruit {

    private String name;
    private String description;

    public Fruit() {
    }

    public static Fruit from(Map<String, AttributeValue> item) {
        Fruit fruit = new Fruit();
        if (item != null && !item.isEmpty()) {
            fruit.setName(item.get(AbstractService.FRUIT_NAME_COL).s());
            fruit.setDescription(item.get(AbstractService.FRUIT_DESC_COL).s());
        }
        return fruit;
    }

    public String getName() {
        return name;
    }

    public void setName(String name) {
        this.name = name;
    }

    public String getDescription() {
        return description;
    }

    public void setDescription(String description) {
        this.description = description;
    }

    @Override
    public boolean equals(Object obj) {
        if (!(obj instanceof Fruit)) {
            return false;
        }

        Fruit other = (Fruit) obj;

        return Objects.equals(other.name, this.name);
    }

    @Override
    public int hashCode() {
        return Objects.hash(this.name);
    }
}
The @RegisterForReflection annotation instructs Quarkus to keep the class and its members during the native compilation. More details about the @RegisterForReflection annotation can be found on the native application tips page.

Nothing fancy. One important thing to note is that having a default constructor is required by the JSON serialization layer. The static from method creates a bean based on the Map object provided by the DynamoDB client response.

Now create a org.acme.dynamodb.AbstractService that will consist of helper methods that prepare DynamoDB request objects for reading and adding items to the table.

package org.acme.dynamodb;

import java.util.HashMap;
import java.util.Map;

import software.amazon.awssdk.services.dynamodb.model.AttributeValue;
import software.amazon.awssdk.services.dynamodb.model.GetItemRequest;
import software.amazon.awssdk.services.dynamodb.model.PutItemRequest;
import software.amazon.awssdk.services.dynamodb.model.QueryRequest;

public abstract class AbstractService {

    public static final String PARTITION_KEY = "partitionKey";
    public static final String PARTITION_VALUE = "FRUIT";

    public static final String FRUIT_NAME_COL = "fruitName";
    public static final String FRUIT_DESC_COL = "fruitDescription";

    public String getTableName() {
        return "QuarkusFruits";
    }

    protected QueryRequest queryRequest() {
        Map<String, AttributeValue> expressionValues = new HashMap<>();
        expressionValues.put(":pk", AttributeValue.builder().s(PARTITION_VALUE).build());
        Map<String, String> expressionNames = new HashMap<>();
        expressionNames.put("#name", FRUIT_NAME_COL);
        expressionNames.put("#description", FRUIT_DESC_COL);

        return QueryRequest.builder()
                .tableName(getTableName())
                .keyConditionExpression(PARTITION_KEY + " = :pk")
                .projectionExpression("#name, #description")
                .expressionAttributeValues(expressionValues)
                .expressionAttributeNames(expressionNames)
                .scanIndexForward(true) // ascending (alphabetical) order guaranteed by DynamoDB
                .build();
    }

    protected PutItemRequest putRequest(Fruit fruit) {
        Map<String, AttributeValue> item = new HashMap<>();
        item.put(PARTITION_KEY, AttributeValue.builder().s(PARTITION_VALUE).build());
        item.put(FRUIT_NAME_COL, AttributeValue.builder().s(fruit.getName()).build());
        item.put(FRUIT_DESC_COL, AttributeValue.builder().s(fruit.getDescription()).build());

        return PutItemRequest.builder()
                .tableName(getTableName())
                .item(item)
                .build();
    }

    protected GetItemRequest getRequest(String name) {
        Map<String, AttributeValue> key = new HashMap<>();
        key.put(PARTITION_KEY, AttributeValue.builder().s(PARTITION_VALUE).build());
        key.put(FRUIT_NAME_COL, AttributeValue.builder().s(name).build());

        return GetItemRequest.builder()
                .tableName(getTableName())
                .key(key)
                .attributesToGet(FRUIT_NAME_COL, FRUIT_DESC_COL)
                .build();
    }
}

Then, create a org.acme.dynamodb.FruitSyncService that will be the business layer of our application and stores/loads the fruits from DynamoDB using the synchronous client.

package org.acme.dynamodb;

import java.util.List;
import java.util.stream.Collectors;

import jakarta.enterprise.context.ApplicationScoped;
import jakarta.inject.Inject;

import software.amazon.awssdk.services.dynamodb.DynamoDbClient;

@ApplicationScoped
public class FruitSyncService extends AbstractService {

    @Inject
    DynamoDbClient dynamoDB;

    public List<Fruit> findAll() {
        return dynamoDB.queryPaginator(queryRequest()).items().stream()
                .map(Fruit::from)
                .collect(Collectors.toList());
    }

    public List<Fruit> add(Fruit fruit) {
        dynamoDB.putItem(putRequest(fruit));
        return findAll();
    }

    public Fruit get(String name) {
        return Fruit.from(dynamoDB.getItem(getRequest(name)).item());
    }
}

Now, edit the org.acme.dynamodb.FruitResource class as follows:

package org.acme.dynamodb;

import java.util.List;

import jakarta.inject.Inject;
import jakarta.ws.rs.Consumes;
import jakarta.ws.rs.GET;
import jakarta.ws.rs.POST;
import jakarta.ws.rs.Path;
import jakarta.ws.rs.Produces;
import jakarta.ws.rs.core.MediaType;

@Path("/fruits")
@Produces(MediaType.APPLICATION_JSON)
@Consumes(MediaType.APPLICATION_JSON)
public class FruitResource {

    @Inject
    FruitSyncService service;

    @GET
    public List<Fruit> getAll() {
        return service.findAll();
    }

    @GET
    @Path("{name}")
    public Fruit getSingle(String name) {
        return service.get(name);
    }

    @POST
    public List<Fruit> add(Fruit fruit) {
        service.add(fruit);
        return getAll();
    }
}

The implementation is pretty straightforward and you just need to define your endpoints using the Jakarta REST annotations and use the FruitSyncService to list/add new fruits.

Configuring Amazon DynamoDB clients

Both Amazon DynamoDB clients (sync and async) are configurable via the application.properties file that can be provided in the src/main/resources directory. Additionally, you need to add to the classpath a proper implementation of the sync client. By default, the extension uses the URL connection HTTP client, so you need to add a URL connection client dependency to the pom.xml file:

<dependency>
    <groupId>software.amazon.awssdk</groupId>
    <artifactId>url-connection-client</artifactId>
</dependency>

If you want to use the Apache 5.x HTTP client instead, configure it as follows:

quarkus.dynamodb.sync-client.type=apache5

And add the following dependency to the application pom.xml:

<dependency>
    <groupId>software.amazon.awssdk</groupId>
    <artifactId>apache5-client</artifactId>
</dependency>

If you want to use the Apache HTTP client instead, configure it as follows:

quarkus.dynamodb.sync-client.type=apache

And add the following dependency to the application pom.xml:

<dependency>
    <groupId>software.amazon.awssdk</groupId>
    <artifactId>apache-client</artifactId>
</dependency>

The AWS SDK has deprecated the Apache HTTP client in favor of the Apache 5.x HTTP client, which is a drop-in replacement: prefer apache5. The build logs a warning when the Apache HTTP client is used. Set quarkus.aws.sync-client.apache-deprecation-warning=false to disable it, see Deprecated Apache HTTP client.

If you want to use the AWS CRT-based HTTP client instead, configure it as follows:

quarkus.dynamodb.sync-client.type=aws-crt

And add the following dependency to the application pom.xml:

<dependency>
    <groupId>software.amazon.awssdk</groupId>
    <artifactId>aws-crt-client</artifactId>
</dependency>

Use Dev Services

With Dev Services, there is nothing to configure: in dev and test modes, Dev Services starts Floci and configures the endpoint, the region and the credentials of the clients.

Use a manually started Floci

If you started Floci yourself, configure the client to use it as follows:

quarkus.dynamodb.endpoint-override=http://localhost:4566 (1)

quarkus.dynamodb.aws.region=us-east-1 (2)
quarkus.dynamodb.aws.credentials.type=static (3)
quarkus.dynamodb.aws.credentials.static-provider.access-key-id=test-key
quarkus.dynamodb.aws.credentials.static-provider.secret-access-key=test-secret
1 Override the Amazon DynamoDB client to use Floci instead of the actual AWS service. When it is set, Dev Services does not start a local stack for Amazon DynamoDB.
2 Floci defaults to us-east-1
3 The static credentials provider lets you set the access-key-id and secret-access-key directly

Use your AWS account

If you want to work with an AWS account, you need an AWS account with access to Amazon DynamoDB and the AWS Command Line Interface, then remove or comment out the endpoint-override and the static credentials properties of the previous section. By default, the Amazon DynamoDB client extension uses the default credentials provider chain that looks for credentials in this order:

  • Java System Properties - aws.accessKeyId and aws.secretAccessKey

  • Environment Variables - AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY

  • Credential profiles file at the default location (~/.aws/credentials) shared by all AWS SDKs and the AWS CLI

  • Credentials delivered through the Amazon ECS if the AWS_CONTAINER_CREDENTIALS_RELATIVE_URI environment variable is set and the security manager has permission to access the variable,

  • Instance profile credentials delivered through the Amazon EC2 metadata service

And the region from your AWS CLI profile will be used.

Without endpoint-override, Dev Services starts a local stack for Amazon DynamoDB in dev and test modes, and the client uses it instead of your AWS account. Removing the endpoint-override is therefore not enough to use your AWS account in these modes: also disable Dev Services for Amazon DynamoDB:

quarkus.dynamodb.devservices.enabled=false

Dev Services never starts in production mode.

Create the QuarkusFruits table

All the fruits are stored under the same partitionKey value and sorted by their name with the fruitName sort key, so they can be listed in alphabetical order with a query.

With Dev Services

Dev Services starts Floci with the floci/floci:latest image by default, which does not ship the AWS CLI. To create the QuarkusFruits table automatically at startup, use the latest-compat image and provide init scripts:

quarkus.aws.devservices.floci.image-name=floci/floci:latest-compat
quarkus.aws.devservices.floci.init-scripts-classpath=floci-init
quarkus.aws.devservices.floci.init-completion-msg=#### Init completed

Create src/main/resources/floci-init/01_create_table.sh:

#!/bin/bash
aws dynamodb create-table \
    --table-name QuarkusFruits \
    --attribute-definitions \
        AttributeName=partitionKey,AttributeType=S \
        AttributeName=fruitName,AttributeType=S \
    --key-schema \
        AttributeName=partitionKey,KeyType=HASH \
        AttributeName=fruitName,KeyType=RANGE \
    --provisioned-throughput ReadCapacityUnits=1,WriteCapacityUnits=1

Then create src/main/resources/floci-init/99_completed.sh, which prints the message Dev Services waits for:

#!/bin/bash
echo "#### Init completed"

The AWS CLI is preconfigured inside the container, so the scripts need no endpoint, profile or credentials. See Dev Services for Amazon Services for the init script details.

On a manually started Floci

Create the table using the AWS CLI of the Floci container:

docker exec floci aws dynamodb create-table --table-name QuarkusFruits \
    --attribute-definitions AttributeName=partitionKey,AttributeType=S \
                            AttributeName=fruitName,AttributeType=S \
    --key-schema AttributeName=partitionKey,KeyType=HASH \
                 AttributeName=fruitName,KeyType=RANGE \
    --provisioned-throughput ReadCapacityUnits=1,WriteCapacityUnits=1

Check that the table exists:

docker exec floci aws dynamodb list-tables
On your AWS account

Before you can use the AWS SDKs with DynamoDB, you must get an AWS access key ID and secret access key. For more information, see Setting Up DynamoDB (Web Service). Then create the same table with your own AWS CLI:

aws dynamodb create-table --table-name QuarkusFruits \
    --attribute-definitions AttributeName=partitionKey,AttributeType=S \
                            AttributeName=fruitName,AttributeType=S \
    --key-schema AttributeName=partitionKey,KeyType=HASH \
                 AttributeName=fruitName,KeyType=RANGE \
    --provisioned-throughput ReadCapacityUnits=1,WriteCapacityUnits=1

Run the application in Dev Mode

Run the application in dev mode with:

./mvnw clean quarkus:dev

If you use Dev Services, it starts a Floci container and configures the Amazon DynamoDB clients to use it. The Dev Services card of the Dev UI, at http://localhost:8080/q/dev-ui, shows the container and the endpoint it exposes.

Next steps

Packaging

Packaging your application is as simple as ./mvnw clean package. It can then be run with java -jar target/quarkus-app/quarkus-run.jar.

With GraalVM or Mandrel installed, you can also create a native executable binary:

./mvnw clean package -Dnative

Without GraalVM or Mandrel, build the native executable inside a container:

./mvnw clean package -Dnative -Dquarkus.native.container-build=true

Depending on your system, that will take some time. Run the native executable with ./target/amazon-dynamodb-quickstart-1.0.0-SNAPSHOT-runner.

Dev Services does not start in production mode, so you need to make sure that your application.properties file is configured to use your AWS account or a local stack. To use a local Floci instance, pass the endpoint and the credentials on the command line: 
java \
    -Dquarkus.dynamodb.endpoint-override=http://localhost:4566 \
    -Dquarkus.dynamodb.aws.region=us-east-1 \
    -Dquarkus.dynamodb.aws.credentials.type=static \
    -Dquarkus.dynamodb.aws.credentials.static-provider.access-key-id=test-key \
    -Dquarkus.dynamodb.aws.credentials.static-provider.secret-access-key=test-secret \
    -jar target/quarkus-app/quarkus-run.jar

See the Packaging applications guide for more details.

Going asynchronous

Thanks to the AWS SDK v2.x used by the Quarkus extension, you can use the asynchronous programming model out of the box.

Create a org.acme.dynamodb.FruitAsyncService that will be similar to our FruitSyncService but using an asynchronous programming model.

package org.acme.dynamodb;

import java.util.List;
import java.util.stream.Collectors;

import jakarta.enterprise.context.ApplicationScoped;
import jakarta.inject.Inject;

import io.smallrye.mutiny.Uni;
import software.amazon.awssdk.services.dynamodb.DynamoDbAsyncClient;

@ApplicationScoped
public class FruitAsyncService extends AbstractService {

    @Inject
    DynamoDbAsyncClient dynamoDB;

    public Uni<List<Fruit>> findAll() {
        return Uni.createFrom().completionStage(() -> dynamoDB.query(queryRequest()))
                .onItem().transform(res -> res.items().stream().map(Fruit::from).collect(Collectors.toList()));
    }

    public Uni<List<Fruit>> add(Fruit fruit) {
        return Uni.createFrom().completionStage(() -> dynamoDB.putItem(putRequest(fruit)))
                .onItem().ignore().andSwitchTo(this::findAll);
    }

    public Uni<Fruit> get(String name) {
        return Uni.createFrom().completionStage(() -> dynamoDB.getItem(getRequest(name)))
                .onItem().transform(resp -> Fruit.from(resp.item()));
    }
}

In the previous code, we create Uni instances from the CompletionStage objects returned by the asynchronous DynamoDB client, and then transform the emitted item.

Then, create an asynchronous REST resource that consumes this async service:

package org.acme.dynamodb;

import java.util.List;

import jakarta.inject.Inject;
import jakarta.ws.rs.GET;
import jakarta.ws.rs.POST;
import jakarta.ws.rs.Path;

import io.smallrye.mutiny.Uni;

@Path("/async-fruits")
public class FruitAsyncResource {

    @Inject
    FruitAsyncService service;

    @GET
    public Uni<List<Fruit>> getAll() {
        return service.findAll();
    }

    @GET
    @Path("{name}")
    public Uni<Fruit> getSingle(String name) {
        return service.get(name);
    }

    @POST
    public Uni<List<Fruit>> add(Fruit fruit) {
        return service.add(fruit)
                .onItem().ignore().andSwitchTo(this::getAll);
    }
}

To enable the asynchronous client, you also need to add the Netty HTTP client dependency to the pom.xml:

<dependency>
    <groupId>software.amazon.awssdk</groupId>
    <artifactId>netty-nio-client</artifactId>
</dependency>

If you want to use the AWS CRT-based HTTP client instead, configure it as follows:

quarkus.dynamodb.async-client.type=aws-crt

And add the following dependency to the application pom.xml:

<dependency>
    <groupId>software.amazon.awssdk</groupId>
    <artifactId>aws-crt-client</artifactId>
</dependency>

Quarkus dev mode picks up the new resource, and restarts by itself when pom.xml changes: if the application is still running, wait a few seconds, then call it again. Otherwise, run it again with ./mvnw quarkus:dev.

Going further

You have built a Quarkus application that uses Amazon DynamoDB, developed locally against Dev Services and ready to run on your AWS account. You are all set to build great applications with Amazon DynamoDB, with the fast startup, the low memory footprint and the developer joy of Quarkus.

To go further:

DynamoDB enhanced client

The DynamoDB enhanced client is part of the AWS SDK for Java version 2 and makes the mapping between DynamoDB Tables and Java beans very easy. The Enhanced Client requires a TableSchema which can be generated from a bean class annotated with DynamoDbBean or DynamoDbImmutable or generated from code. By default, TableSchemas generated from bean classes are registered and cached at startup. You don’t need to explicitly instantiate them at class-load time. It has both a sync and an async variants.

To use the enhanced client, add the quarkus-amazon-dynamodb-enhanced extension to your pom.xml:

<dependency>
    <groupId>io.quarkiverse.amazonservices</groupId>
    <artifactId>quarkus-amazon-dynamodb-enhanced</artifactId>
</dependency>

The Fruit bean would look like this:

package org.acme.dynamodb;

import java.util.Objects;

import software.amazon.awssdk.enhanced.dynamodb.mapper.annotations.DynamoDbAttribute;
import software.amazon.awssdk.enhanced.dynamodb.mapper.annotations.DynamoDbBean;
import software.amazon.awssdk.enhanced.dynamodb.mapper.annotations.DynamoDbPartitionKey;
import software.amazon.awssdk.enhanced.dynamodb.mapper.annotations.DynamoDbSortKey;

@DynamoDbBean
public class Fruit {

    private String partitionKey = AbstractService.PARTITION_VALUE;
    private String name;
    private String description;

    public Fruit() {
    }

    @DynamoDbPartitionKey
    @DynamoDbAttribute(AbstractService.PARTITION_KEY)
    public String getPartitionKey() {
        return partitionKey;
    }

    public void setPartitionKey(String partitionKey) {
        this.partitionKey = partitionKey;
    }

    @DynamoDbSortKey
    @DynamoDbAttribute(AbstractService.FRUIT_NAME_COL)
    public String getName() {
        return name;
    }

    public void setName(String name) {
        this.name = name;
    }

    @DynamoDbAttribute(AbstractService.FRUIT_DESC_COL)
    public String getDescription() {
        return description;
    }

    public void setDescription(String description) {
        this.description = description;
    }

    @Override
    public boolean equals(Object obj) {
        if (!(obj instanceof Fruit)) {
            return false;
        }

        Fruit other = (Fruit) obj;

        return Objects.equals(other.name, this.name);
    }

    @Override
    public int hashCode() {
        return Objects.hash(this.name);
    }
}

Note that you don’t need to add @RegisterForReflection anymore. The partitionKey property maps the partition key shared by all the fruits, while the name is the sort key.

The FruitSyncService would need to use the DynamoDbEnhancedClient as well as create a TableSchema:

package org.acme.dynamodb;

import java.util.List;
import java.util.stream.Collectors;

import jakarta.enterprise.context.ApplicationScoped;
import jakarta.inject.Inject;
import software.amazon.awssdk.enhanced.dynamodb.DynamoDbEnhancedClient;
import software.amazon.awssdk.enhanced.dynamodb.DynamoDbTable;
import software.amazon.awssdk.enhanced.dynamodb.Key;
import software.amazon.awssdk.enhanced.dynamodb.TableSchema;
import software.amazon.awssdk.enhanced.dynamodb.model.QueryConditional;

@ApplicationScoped
public class FruitSyncService extends AbstractService {

    private DynamoDbTable<Fruit> fruitTable;

    @Inject
    FruitSyncService(DynamoDbEnhancedClient dynamoEnhancedClient) {
        fruitTable = dynamoEnhancedClient.table(getTableName(),
            TableSchema.fromClass(Fruit.class));
    }

    public List<Fruit> findAll() {
        return fruitTable.query(QueryConditional.keyEqualTo(k -> k.partitionValue(PARTITION_VALUE)))
                .items().stream()
                .collect(Collectors.toList());
    }

    public List<Fruit> add(Fruit fruit) {
        fruitTable.putItem(fruit);
        return findAll();
    }

    public Fruit get(String name) {
        Key key = Key.builder().partitionValue(PARTITION_VALUE).sortValue(name).build();
        return fruitTable.getItem(key);
    }
}

The same goes for the asynchronous version with DynamoDbEnhancedAsyncClient:

package org.acme.dynamodb;

import java.util.List;
import java.util.stream.Collectors;

import io.smallrye.mutiny.Multi;
import io.smallrye.mutiny.Uni;
import jakarta.enterprise.context.ApplicationScoped;
import jakarta.inject.Inject;
import mutiny.zero.flow.adapters.AdaptersToFlow;
import software.amazon.awssdk.enhanced.dynamodb.DynamoDbAsyncTable;
import software.amazon.awssdk.enhanced.dynamodb.DynamoDbEnhancedAsyncClient;
import software.amazon.awssdk.enhanced.dynamodb.Key;
import software.amazon.awssdk.enhanced.dynamodb.TableSchema;
import software.amazon.awssdk.enhanced.dynamodb.model.QueryConditional;

@ApplicationScoped
public class FruitAsyncService extends AbstractService {

    private DynamoDbAsyncTable<Fruit> fruitTable;

    @Inject
    FruitAsyncService(DynamoDbEnhancedAsyncClient dynamoEnhancedAsyncClient) {
        fruitTable = dynamoEnhancedAsyncClient.table(getTableName(),
            TableSchema.fromClass(Fruit.class));
    }

    public Uni<List<Fruit>> findAll() {
        return Multi.createFrom()
                .publisher(AdaptersToFlow.publisher(fruitTable.query(QueryConditional.keyEqualTo(k -> k.partitionValue(PARTITION_VALUE))).items()))
                .collect().asList();
    }

    public Uni<List<Fruit>> add(Fruit fruit) {
        return Uni.createFrom().completionStage(() -> fruitTable.putItem(fruit))
                .onItem().ignore().andSwitchTo(this::findAll);
    }

    public Uni<Fruit> get(String name) {
        Key key = Key.builder().partitionValue(PARTITION_VALUE).sortValue(name).build();
        return Uni.createFrom().completionStage(() -> fruitTable.getItem(key));
    }
}

Resource classes remain unchanged.

Alternatively, if you only need the DynamoDbTable instance, inject it directly with the @NamedDynamoDbTable annotation and the table name, instead of creating it from the enhanced client. In the synchronous service, replace the fruitTable field and the constructor as follows:

-import software.amazon.awssdk.enhanced.dynamodb.DynamoDbEnhancedClient;
-import software.amazon.awssdk.enhanced.dynamodb.TableSchema;
+import io.quarkiverse.amazon.dynamodb.enhanced.runtime.NamedDynamoDbTable;

-    private DynamoDbTable<Fruit> fruitTable;
-
     @Inject
-    FruitSyncService(DynamoDbEnhancedClient dynamoEnhancedClient) {
-        fruitTable = dynamoEnhancedClient.table(getTableName(),
-            TableSchema.fromClass(Fruit.class));
-    }
+    @NamedDynamoDbTable("QuarkusFruits")
+    DynamoDbTable<Fruit> fruitTable;

And in the asynchronous service:

-import software.amazon.awssdk.enhanced.dynamodb.DynamoDbEnhancedAsyncClient;
-import software.amazon.awssdk.enhanced.dynamodb.TableSchema;
+import io.quarkiverse.amazon.dynamodb.enhanced.runtime.NamedDynamoDbTable;

-    private DynamoDbAsyncTable<Fruit> fruitTable;
-
     @Inject
-    FruitAsyncService(DynamoDbEnhancedAsyncClient dynamoEnhancedAsyncClient) {
-        fruitTable = dynamoEnhancedAsyncClient.table(getTableName(),
-            TableSchema.fromClass(Fruit.class));
-    }
+    @NamedDynamoDbTable("QuarkusFruits")
+    DynamoDbAsyncTable<Fruit> fruitTable;

The other methods stay the same.

You can find more information about the DynamoDB enhanced client in the AWS documentation:

Configuration Reference

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Configuration property

Type

Default

quarkus.dynamodb.interceptors

List of execution interceptors that will have access to read and modify the request and response objects as they are processed by the AWS SDK.

The list should consists of class names which implements software.amazon.awssdk.core.interceptor.ExecutionInterceptor interface. Classes will be attempted to be loaded via CDI first, and if no CDI beans are available, then the constructor with no parameters will be invoked to instantiate each class.

Environment variable: QUARKUS_DYNAMODB_INTERCEPTORS

list of string

quarkus.dynamodb.telemetry.enabled

OpenTelemetry AWS SDK instrumentation will be enabled if the OpenTelemetry extension is present and this value is true.

Environment variable: QUARKUS_DYNAMODB_TELEMETRY_ENABLED

boolean

true when quarkus-opentelemetry is present, false otherwise

quarkus.dynamodb.sync-client.type

Type of the sync HTTP client implementation

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_TYPE

url, apache, apache5, aws-crt

url

quarkus.dynamodb.async-client.type

Type of the async HTTP client implementation

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_TYPE

netty, aws-crt

netty

quarkus.dynamodb.devservices.enabled

If a local AWS stack should be used. (default to true) If this is true and endpoint-override is not configured then a local AWS stack will be started and will be used instead of the given configuration. The local AWS stack is provided by the stack provider configured with provider.

Environment variable: QUARKUS_DYNAMODB_DEVSERVICES_ENABLED

boolean

quarkus.dynamodb.devservices.container-properties."container-properties"

Generic properties that are pass for additional container configuration.

Environment variable: QUARKUS_DYNAMODB_DEVSERVICES_CONTAINER_PROPERTIES__CONTAINER_PROPERTIES_

Map<String,String>

quarkus.dynamodb.devservices.provider

The dev services stack provider to use for this service. If not specified, the global setting from quarkus.aws.devservices.provider is used. Supported values: "floci", "localstack", "ministack", "moto"

This allows per-service override of the global stack selection.

Environment variable: QUARKUS_DYNAMODB_DEVSERVICES_PROVIDER

floci, localstack, ministack, moto

quarkus.dynamodb.enable-endpoint-discovery

Enable service endpoint discovery.

Environment variable: QUARKUS_DYNAMODB_ENABLE_ENDPOINT_DISCOVERY

boolean

true for services that requires endpoint discovery.

AWS SDK client configurations

Type

Default

quarkus.dynamodb.endpoint-override

quarkus.dynamodb."client-name".endpoint-override

The endpoint URI with which the SDK should communicate.

If not specified, an appropriate endpoint to be used for the given service and region.

Environment variable: QUARKUS_DYNAMODB_ENDPOINT_OVERRIDE

URI

quarkus.dynamodb.api-call-timeout

quarkus.dynamodb."client-name".api-call-timeout

The amount of time to allow the client to complete the execution of an API call.

This timeout covers the entire client execution except for marshalling. This includes request handler execution, all HTTP requests including retries, unmarshalling, etc.

This value should always be positive, if present.

Environment variable: QUARKUS_DYNAMODB_API_CALL_TIMEOUT

Duration 

quarkus.dynamodb.api-call-attempt-timeout

quarkus.dynamodb."client-name".api-call-attempt-timeout

The amount of time to wait for the HTTP request to complete before giving up and timing out.

This value should always be positive, if present.

Environment variable: QUARKUS_DYNAMODB_API_CALL_ATTEMPT_TIMEOUT

Duration 

quarkus.dynamodb.advanced.use-quarkus-scheduled-executor-service

quarkus.dynamodb."client-name".advanced.use-quarkus-scheduled-executor-service

Whether the Quarkus thread pool should be used for scheduling tasks such as async retry attempts and timeout task.

When disabled, the default sdk behavior is to create a dedicated thread pool for each client, resulting in competition for CPU resources among these thread pools.

Environment variable: QUARKUS_DYNAMODB_ADVANCED_USE_QUARKUS_SCHEDULED_EXECUTOR_SERVICE

boolean

true

AWS services configurations

Type

Default

quarkus.dynamodb.aws.region

quarkus.dynamodb."client-name".aws.region

An Amazon Web Services region that hosts the given service.

It overrides region provider chain with static value of region with which the service client should communicate.

If not set, region is retrieved via the default providers chain in the following order:

  • aws.region system property

  • region property from the profile file

  • Instance profile file

See software.amazon.awssdk.regions.Region for available regions.

Environment variable: QUARKUS_DYNAMODB_AWS_REGION

Region

quarkus.dynamodb.aws.credentials.type

quarkus.dynamodb."client-name".aws.credentials.type

Configure the credentials provider that should be used to authenticate with AWS.

Available values:

  • default - the provider will attempt to identify the credentials automatically using the following checks:

    • Java System Properties - aws.accessKeyId and aws.secretAccessKey

    • Environment Variables - AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY

    • Credential profiles file at the default location (~/.aws/credentials) shared by all AWS SDKs and the AWS CLI

    • Credentials delivered through the Amazon EC2 container service if AWS_CONTAINER_CREDENTIALS_RELATIVE_URI environment variable is set and security manager has permission to access the variable.

    • Instance profile credentials delivered through the Amazon EC2 metadata service

  • static - the provider that uses the access key and secret access key specified in the static-provider section of the config.

  • system-property - it loads credentials from the aws.accessKeyId, aws.secretAccessKey and aws.sessionToken system properties.

  • env-variable - it loads credentials from the AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY and AWS_SESSION_TOKEN environment variables.

  • profile - credentials are based on AWS configuration profiles. This loads credentials from a profile file, allowing you to share multiple sets of AWS security credentials between different tools like the AWS SDK for Java and the AWS CLI.

  • container - It loads credentials from a local metadata service. Containers currently supported by the AWS SDK are Amazon Elastic Container Service (ECS) and AWS Greengrass

  • instance-profile - It loads credentials from the Amazon EC2 Instance Metadata Service.

  • process - Credentials are loaded from an external process. This is used to support the credential_process setting in the profile credentials file. See Sourcing Credentials From External Processes for more information.

  • custom - Credentials are loaded from a registered bean of type AwsCredentialsProvider matching the specified name.

  • anonymous - It always returns anonymous AWS credentials. Anonymous AWS credentials result in un-authenticated requests and will fail unless the resource or API’s policy has been configured to specifically allow anonymous access.

Environment variable: QUARKUS_DYNAMODB_AWS_CREDENTIALS_TYPE

default, static, system-property, env-variable, profile, container, instance-profile, process, custom, anonymous

default

Default credentials provider configuration

Type

Default

quarkus.dynamodb.aws.credentials.default-provider.async-credential-update-enabled

quarkus.dynamodb."client-name".aws.credentials.default-provider.async-credential-update-enabled

Whether this provider should fetch credentials asynchronously in the background.

If this is true, threads are less likely to block, but additional resources are used to maintain the provider.

Environment variable: QUARKUS_DYNAMODB_AWS_CREDENTIALS_DEFAULT_PROVIDER_ASYNC_CREDENTIAL_UPDATE_ENABLED

boolean

false

quarkus.dynamodb.aws.credentials.default-provider.reuse-last-provider-enabled

quarkus.dynamodb."client-name".aws.credentials.default-provider.reuse-last-provider-enabled

Whether the provider should reuse the last successful credentials provider in the chain.

Reusing the last successful credentials provider will typically return credentials faster than searching through the chain.

Environment variable: QUARKUS_DYNAMODB_AWS_CREDENTIALS_DEFAULT_PROVIDER_REUSE_LAST_PROVIDER_ENABLED

boolean

true

Static credentials provider configuration

Type

Default

quarkus.dynamodb.aws.credentials.static-provider.access-key-id

quarkus.dynamodb."client-name".aws.credentials.static-provider.access-key-id

AWS Access key id

Environment variable: QUARKUS_DYNAMODB_AWS_CREDENTIALS_STATIC_PROVIDER_ACCESS_KEY_ID

string

quarkus.dynamodb.aws.credentials.static-provider.secret-access-key

quarkus.dynamodb."client-name".aws.credentials.static-provider.secret-access-key

AWS Secret access key

Environment variable: QUARKUS_DYNAMODB_AWS_CREDENTIALS_STATIC_PROVIDER_SECRET_ACCESS_KEY

string

quarkus.dynamodb.aws.credentials.static-provider.session-token

quarkus.dynamodb."client-name".aws.credentials.static-provider.session-token

AWS Session token

Environment variable: QUARKUS_DYNAMODB_AWS_CREDENTIALS_STATIC_PROVIDER_SESSION_TOKEN

string

AWS Profile credentials provider configuration

Type

Default

quarkus.dynamodb.aws.credentials.profile-provider.profile-name

quarkus.dynamodb."client-name".aws.credentials.profile-provider.profile-name

The name of the profile that should be used by this credentials provider.

If not specified, the value in AWS_PROFILE environment variable or aws.profile system property is used and defaults to default name.

Environment variable: QUARKUS_DYNAMODB_AWS_CREDENTIALS_PROFILE_PROVIDER_PROFILE_NAME

string

Process credentials provider configuration

Type

Default

quarkus.dynamodb.aws.credentials.process-provider.async-credential-update-enabled

quarkus.dynamodb."client-name".aws.credentials.process-provider.async-credential-update-enabled

Whether the provider should fetch credentials asynchronously in the background.

If this is true, threads are less likely to block when credentials are loaded, but additional resources are used to maintain the provider.

Environment variable: QUARKUS_DYNAMODB_AWS_CREDENTIALS_PROCESS_PROVIDER_ASYNC_CREDENTIAL_UPDATE_ENABLED

boolean

false

quarkus.dynamodb.aws.credentials.process-provider.credential-refresh-threshold

quarkus.dynamodb."client-name".aws.credentials.process-provider.credential-refresh-threshold

The amount of time between when the credentials expire and when the credentials should start to be refreshed.

This allows the credentials to be refreshed *before* they are reported to expire.

Environment variable: QUARKUS_DYNAMODB_AWS_CREDENTIALS_PROCESS_PROVIDER_CREDENTIAL_REFRESH_THRESHOLD

Duration 

15S

quarkus.dynamodb.aws.credentials.process-provider.process-output-limit

quarkus.dynamodb."client-name".aws.credentials.process-provider.process-output-limit

The maximum size of the output that can be returned by the external process before an exception is raised.

Environment variable: QUARKUS_DYNAMODB_AWS_CREDENTIALS_PROCESS_PROVIDER_PROCESS_OUTPUT_LIMIT

MemorySize 

1M

quarkus.dynamodb.aws.credentials.process-provider.command

quarkus.dynamodb."client-name".aws.credentials.process-provider.command

The command that should be executed to retrieve credentials. Command and parameters are seperated list entries.

Environment variable: QUARKUS_DYNAMODB_AWS_CREDENTIALS_PROCESS_PROVIDER_COMMAND

list of string

Custom credentials provider configuration

Type

Default

quarkus.dynamodb.aws.credentials.custom-provider.name

quarkus.dynamodb."client-name".aws.credentials.custom-provider.name

The name of custom AwsCredentialsProvider bean.

Environment variable: QUARKUS_DYNAMODB_AWS_CREDENTIALS_CUSTOM_PROVIDER_NAME

string

Sync HTTP transport configurations

Type

Default

quarkus.dynamodb.sync-client.connection-timeout

The maximum amount of time to establish a connection before timing out.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_CONNECTION_TIMEOUT

Duration 

2S

quarkus.dynamodb.sync-client.socket-timeout

The amount of time to wait for data to be transferred over an established, open connection before the connection is timed out.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_SOCKET_TIMEOUT

Duration 

30S

quarkus.dynamodb.sync-client.tls-key-managers-provider.type

TLS key managers provider type.

Available providers:

  • none - Use this provider if you don’t want the client to present any certificates to the remote TLS host.

  • system-property - Provider checks the standard javax.net.ssl.keyStore, javax.net.ssl.keyStorePassword, and javax.net.ssl.keyStoreType properties defined by the JSSE.

  • file-store - Provider that loads the key store from a file.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_TLS_KEY_MANAGERS_PROVIDER_TYPE

none, system-property, file-store

system-property

quarkus.dynamodb.sync-client.tls-key-managers-provider.file-store.path

Path to the key store.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_TLS_KEY_MANAGERS_PROVIDER_FILE_STORE_PATH

path

quarkus.dynamodb.sync-client.tls-key-managers-provider.file-store.type

Key store type.

See the KeyStore section in the https://docs.oracle.com/javase/8/docs/technotes/guides/security/StandardNames.html#KeyStore[Java Cryptography Architecture Standard Algorithm Name Documentation] for information about standard keystore types.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_TLS_KEY_MANAGERS_PROVIDER_FILE_STORE_TYPE

string

quarkus.dynamodb.sync-client.tls-key-managers-provider.file-store.password

Key store password

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_TLS_KEY_MANAGERS_PROVIDER_FILE_STORE_PASSWORD

string

quarkus.dynamodb.sync-client.tls-trust-managers-provider.type

TLS trust managers provider type.

Available providers:

  • trust-all - Use this provider to disable the validation of servers certificates and therefore trust all server certificates.

  • system-property - Provider checks the standard javax.net.ssl.keyStore, javax.net.ssl.keyStorePassword, and javax.net.ssl.keyStoreType properties defined by the JSSE.

  • file-store - Provider that loads the key store from a file.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_TLS_TRUST_MANAGERS_PROVIDER_TYPE

trust-all, system-property, file-store

system-property

quarkus.dynamodb.sync-client.tls-trust-managers-provider.file-store.path

Path to the key store.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_TLS_TRUST_MANAGERS_PROVIDER_FILE_STORE_PATH

path

quarkus.dynamodb.sync-client.tls-trust-managers-provider.file-store.type

Key store type.

See the KeyStore section in the https://docs.oracle.com/javase/8/docs/technotes/guides/security/StandardNames.html#KeyStore[Java Cryptography Architecture Standard Algorithm Name Documentation] for information about standard keystore types.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_TLS_TRUST_MANAGERS_PROVIDER_FILE_STORE_TYPE

string

quarkus.dynamodb.sync-client.tls-trust-managers-provider.file-store.password

Key store password

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_TLS_TRUST_MANAGERS_PROVIDER_FILE_STORE_PASSWORD

string

Apache HTTP client specific configurations

Type

Default

quarkus.dynamodb.sync-client.apache.connection-acquisition-timeout

The amount of time to wait when acquiring a connection from the pool before giving up and timing out.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_APACHE_CONNECTION_ACQUISITION_TIMEOUT

Duration 

10S

quarkus.dynamodb.sync-client.apache.connection-max-idle-time

The maximum amount of time that a connection should be allowed to remain open while idle.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_APACHE_CONNECTION_MAX_IDLE_TIME

Duration 

60S

quarkus.dynamodb.sync-client.apache.connection-time-to-live

The maximum amount of time that a connection should be allowed to remain open, regardless of usage frequency.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_APACHE_CONNECTION_TIME_TO_LIVE

Duration 

quarkus.dynamodb.sync-client.apache.max-connections

The maximum number of connections allowed in the connection pool.

Each built HTTP client has its own private connection pool.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_APACHE_MAX_CONNECTIONS

int

50

quarkus.dynamodb.sync-client.apache.expect-continue-enabled

Whether the client should send an HTTP expect-continue handshake before each request.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_APACHE_EXPECT_CONTINUE_ENABLED

boolean

true

quarkus.dynamodb.sync-client.apache.use-idle-connection-reaper

Whether the idle connections in the connection pool should be closed asynchronously.

When enabled, connections left idling for longer than quarkus..sync-client.connection-max-idle-time will be closed. This will not close connections currently in use.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_APACHE_USE_IDLE_CONNECTION_REAPER

boolean

true

quarkus.dynamodb.sync-client.apache.tcp-keep-alive

Configure whether to enable or disable TCP KeepAlive.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_APACHE_TCP_KEEP_ALIVE

boolean

false

quarkus.dynamodb.sync-client.apache.proxy.enabled

Enable HTTP proxy

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_APACHE_PROXY_ENABLED

boolean

false

quarkus.dynamodb.sync-client.apache.proxy.endpoint

The endpoint of the proxy server that the SDK should connect through.

Currently, the endpoint is limited to a host and port. Any other URI components will result in an exception being raised.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_APACHE_PROXY_ENDPOINT

URI

quarkus.dynamodb.sync-client.apache.proxy.username

The username to use when connecting through a proxy.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_APACHE_PROXY_USERNAME

string

quarkus.dynamodb.sync-client.apache.proxy.password

The password to use when connecting through a proxy.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_APACHE_PROXY_PASSWORD

string

quarkus.dynamodb.sync-client.apache.proxy.ntlm-domain

For NTLM proxies - the Windows domain name to use when authenticating with the proxy.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_APACHE_PROXY_NTLM_DOMAIN

string

quarkus.dynamodb.sync-client.apache.proxy.ntlm-workstation

For NTLM proxies - the Windows workstation name to use when authenticating with the proxy.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_APACHE_PROXY_NTLM_WORKSTATION

string

quarkus.dynamodb.sync-client.apache.proxy.preemptive-basic-authentication-enabled

Whether to attempt to authenticate preemptively against the proxy server using basic authentication.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_APACHE_PROXY_PREEMPTIVE_BASIC_AUTHENTICATION_ENABLED

boolean

quarkus.dynamodb.sync-client.apache.proxy.non-proxy-hosts

The hosts that the client is allowed to access without going through the proxy.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_APACHE_PROXY_NON_PROXY_HOSTS

list of string

AWS CRT-based HTTP client specific configurations

Type

Default

quarkus.dynamodb.sync-client.crt.connection-max-idle-time

The maximum amount of time that a connection should be allowed to remain open while idle.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_CRT_CONNECTION_MAX_IDLE_TIME

Duration 

60S

quarkus.dynamodb.sync-client.crt.max-concurrency

The maximum number of allowed concurrent requests.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_CRT_MAX_CONCURRENCY

int

50

quarkus.dynamodb.sync-client.crt.connection-acquisition-timeout

The amount of time to wait when initially establishing a connection before giving up and timing out.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_CRT_CONNECTION_ACQUISITION_TIMEOUT

Duration 

10S

quarkus.dynamodb.sync-client.crt.proxy.enabled

Enable HTTP proxy

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_CRT_PROXY_ENABLED

boolean

false

quarkus.dynamodb.sync-client.crt.proxy.endpoint

The endpoint of the proxy server that the SDK should connect through.

Currently, the endpoint is limited to a host and port. Any other URI components will result in an exception being raised.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_CRT_PROXY_ENDPOINT

URI

quarkus.dynamodb.sync-client.crt.proxy.username

The username to use when connecting through a proxy.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_CRT_PROXY_USERNAME

string

quarkus.dynamodb.sync-client.crt.proxy.password

The password to use when connecting through a proxy.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_CRT_PROXY_PASSWORD

string

quarkus.dynamodb.sync-client.crt.tcp-keep-alive.enabled

Configure whether to enable or disable TCP KeepAlive.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_CRT_TCP_KEEP_ALIVE_ENABLED

boolean

false

quarkus.dynamodb.sync-client.crt.tcp-keep-alive.keep-alive-interval

Time between TCP keepalive packets being sent to the peer.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_CRT_TCP_KEEP_ALIVE_KEEP_ALIVE_INTERVAL

Duration 

75MS

quarkus.dynamodb.sync-client.crt.tcp-keep-alive.keep-alive-timeout

Time to wait for a keepalive response before considering the connection timed out.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_CRT_TCP_KEEP_ALIVE_KEEP_ALIVE_TIMEOUT

Duration 

7200MS

quarkus.dynamodb.sync-client.crt.tcp-keep-alive.keep-alive-probes

Number of keepalive probes allowed to fail before the connection is considered lost.

Environment variable: QUARKUS_DYNAMODB_SYNC_CLIENT_CRT_TCP_KEEP_ALIVE_KEEP_ALIVE_PROBES

int

9

Async HTTP transport configurations

Type

Default

quarkus.dynamodb.async-client.max-concurrency

The maximum number of allowed concurrent requests.

For HTTP/1.1 this is the same as max connections. For HTTP/2 the number of connections that will be used depends on the max streams allowed per connection.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_MAX_CONCURRENCY

int

50

quarkus.dynamodb.async-client.max-pending-connection-acquires

The maximum number of pending acquires allowed.

Once this exceeds, acquire tries will be failed.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_MAX_PENDING_CONNECTION_ACQUIRES

int

10000

quarkus.dynamodb.async-client.read-timeout

The amount of time to wait for a read on a socket before an exception is thrown.

Specify 0 to disable.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_READ_TIMEOUT

Duration 

30S

quarkus.dynamodb.async-client.write-timeout

The amount of time to wait for a write on a socket before an exception is thrown.

Specify 0 to disable.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_WRITE_TIMEOUT

Duration 

30S

quarkus.dynamodb.async-client.connection-timeout

The amount of time to wait when initially establishing a connection before giving up and timing out.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_CONNECTION_TIMEOUT

Duration 

10S

quarkus.dynamodb.async-client.connection-acquisition-timeout

The amount of time to wait when acquiring a connection from the pool before giving up and timing out.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_CONNECTION_ACQUISITION_TIMEOUT

Duration 

2S

quarkus.dynamodb.async-client.connection-time-to-live

The maximum amount of time that a connection should be allowed to remain open, regardless of usage frequency.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_CONNECTION_TIME_TO_LIVE

Duration 

quarkus.dynamodb.async-client.connection-max-idle-time

The maximum amount of time that a connection should be allowed to remain open while idle.

Currently has no effect if quarkus..async-client.use-idle-connection-reaper is false.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_CONNECTION_MAX_IDLE_TIME

Duration 

5S

quarkus.dynamodb.async-client.use-idle-connection-reaper

Whether the idle connections in the connection pool should be closed.

When enabled, connections left idling for longer than quarkus..async-client.connection-max-idle-time will be closed. This will not close connections currently in use.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_USE_IDLE_CONNECTION_REAPER

boolean

true

quarkus.dynamodb.async-client.tcp-keep-alive

Configure whether to enable or disable TCP KeepAlive. Applicable only to netty-nio client.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_TCP_KEEP_ALIVE

boolean

false

AWS CRT-based HTTP client specific configurations

Type

Default

quarkus.dynamodb.async-client.crt.connection-max-idle-time

The maximum amount of time that a connection should be allowed to remain open while idle.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_CRT_CONNECTION_MAX_IDLE_TIME

Duration 

60S

quarkus.dynamodb.async-client.crt.max-concurrency

The maximum number of allowed concurrent requests.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_CRT_MAX_CONCURRENCY

int

50

quarkus.dynamodb.async-client.crt.connection-acquisition-timeout

The amount of time to wait when initially establishing a connection before giving up and timing out.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_CRT_CONNECTION_ACQUISITION_TIMEOUT

Duration 

10S

quarkus.dynamodb.async-client.crt.proxy.enabled

Enable HTTP proxy

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_CRT_PROXY_ENABLED

boolean

false

quarkus.dynamodb.async-client.crt.proxy.endpoint

The endpoint of the proxy server that the SDK should connect through.

Currently, the endpoint is limited to a host and port. Any other URI components will result in an exception being raised.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_CRT_PROXY_ENDPOINT

URI

quarkus.dynamodb.async-client.crt.proxy.username

The username to use when connecting through a proxy.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_CRT_PROXY_USERNAME

string

quarkus.dynamodb.async-client.crt.proxy.password

The password to use when connecting through a proxy.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_CRT_PROXY_PASSWORD

string

quarkus.dynamodb.async-client.crt.tcp-keep-alive.enabled

Configure whether to enable or disable TCP KeepAlive.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_CRT_TCP_KEEP_ALIVE_ENABLED

boolean

false

quarkus.dynamodb.async-client.crt.tcp-keep-alive.keep-alive-interval

Time between TCP keepalive packets being sent to the peer.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_CRT_TCP_KEEP_ALIVE_KEEP_ALIVE_INTERVAL

Duration 

75MS

quarkus.dynamodb.async-client.crt.tcp-keep-alive.keep-alive-timeout

Time to wait for a keepalive response before considering the connection timed out.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_CRT_TCP_KEEP_ALIVE_KEEP_ALIVE_TIMEOUT

Duration 

7200MS

quarkus.dynamodb.async-client.crt.tcp-keep-alive.keep-alive-probes

Number of keepalive probes allowed to fail before the connection is considered lost.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_CRT_TCP_KEEP_ALIVE_KEEP_ALIVE_PROBES

int

9

quarkus.dynamodb.async-client.protocol

The HTTP protocol to use.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_PROTOCOL

http1-1, http2

http1-1

quarkus.dynamodb.async-client.ssl-provider

The SSL Provider to be used in the Netty client.

Default is OPENSSL if available, JDK otherwise.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_SSL_PROVIDER

jdk, openssl, openssl-refcnt

quarkus.dynamodb.async-client.http2.max-streams

The maximum number of concurrent streams for an HTTP/2 connection.

This setting is only respected when the HTTP/2 protocol is used.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_HTTP2_MAX_STREAMS

long

4294967295

quarkus.dynamodb.async-client.http2.initial-window-size

The initial window size for an HTTP/2 stream.

This setting is only respected when the HTTP/2 protocol is used.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_HTTP2_INITIAL_WINDOW_SIZE

int

1048576

quarkus.dynamodb.async-client.http2.health-check-ping-period

Sets the period that the Netty client will send PING frames to the remote endpoint to check the health of the connection. To disable this feature, set a duration of 0.

This setting is only respected when the HTTP/2 protocol is used.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_HTTP2_HEALTH_CHECK_PING_PERIOD

Duration 

5

quarkus.dynamodb.async-client.proxy.enabled

Enable HTTP proxy.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_PROXY_ENABLED

boolean

false

quarkus.dynamodb.async-client.proxy.endpoint

The endpoint of the proxy server that the SDK should connect through.

Currently, the endpoint is limited to a host and port. Any other URI components will result in an exception being raised.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_PROXY_ENDPOINT

URI

quarkus.dynamodb.async-client.proxy.non-proxy-hosts

The hosts that the client is allowed to access without going through the proxy.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_PROXY_NON_PROXY_HOSTS

list of string

quarkus.dynamodb.async-client.tls-key-managers-provider.type

TLS key managers provider type.

Available providers:

  • none - Use this provider if you don’t want the client to present any certificates to the remote TLS host.

  • system-property - Provider checks the standard javax.net.ssl.keyStore, javax.net.ssl.keyStorePassword, and javax.net.ssl.keyStoreType properties defined by the JSSE.

  • file-store - Provider that loads the key store from a file.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_TLS_KEY_MANAGERS_PROVIDER_TYPE

none, system-property, file-store

system-property

quarkus.dynamodb.async-client.tls-key-managers-provider.file-store.path

Path to the key store.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_TLS_KEY_MANAGERS_PROVIDER_FILE_STORE_PATH

path

quarkus.dynamodb.async-client.tls-key-managers-provider.file-store.type

Key store type.

See the KeyStore section in the https://docs.oracle.com/javase/8/docs/technotes/guides/security/StandardNames.html#KeyStore[Java Cryptography Architecture Standard Algorithm Name Documentation] for information about standard keystore types.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_TLS_KEY_MANAGERS_PROVIDER_FILE_STORE_TYPE

string

quarkus.dynamodb.async-client.tls-key-managers-provider.file-store.password

Key store password

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_TLS_KEY_MANAGERS_PROVIDER_FILE_STORE_PASSWORD

string

quarkus.dynamodb.async-client.tls-trust-managers-provider.type

TLS trust managers provider type.

Available providers:

  • trust-all - Use this provider to disable the validation of servers certificates and therefore trust all server certificates.

  • system-property - Provider checks the standard javax.net.ssl.keyStore, javax.net.ssl.keyStorePassword, and javax.net.ssl.keyStoreType properties defined by the JSSE.

  • file-store - Provider that loads the key store from a file.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_TLS_TRUST_MANAGERS_PROVIDER_TYPE

trust-all, system-property, file-store

system-property

quarkus.dynamodb.async-client.tls-trust-managers-provider.file-store.path

Path to the key store.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_TLS_TRUST_MANAGERS_PROVIDER_FILE_STORE_PATH

path

quarkus.dynamodb.async-client.tls-trust-managers-provider.file-store.type

Key store type.

See the KeyStore section in the https://docs.oracle.com/javase/8/docs/technotes/guides/security/StandardNames.html#KeyStore[Java Cryptography Architecture Standard Algorithm Name Documentation] for information about standard keystore types.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_TLS_TRUST_MANAGERS_PROVIDER_FILE_STORE_TYPE

string

quarkus.dynamodb.async-client.tls-trust-managers-provider.file-store.password

Key store password

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_TLS_TRUST_MANAGERS_PROVIDER_FILE_STORE_PASSWORD

string

quarkus.dynamodb.async-client.event-loop.override

Enable the custom configuration of the Netty event loop group. This option is only available when using Quarkus 3.x. With Quarkus 4, the AWS SDK always uses its own event loop.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_EVENT_LOOP_OVERRIDE

boolean

quarkus.dynamodb.async-client.event-loop.number-of-threads

Number of threads to use for the event loop group.

If not set, the default Netty thread count is used (which is double the number of available processors unless the io.netty.eventLoopThreads system property is set).

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_EVENT_LOOP_NUMBER_OF_THREADS

int

quarkus.dynamodb.async-client.event-loop.thread-name-prefix

The thread name prefix for threads created by this thread factory used by event loop group.

The prefix will be appended with a number unique to the thread factory and a number unique to the thread.

If not specified it defaults to aws-java-sdk-NettyEventLoop

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_EVENT_LOOP_THREAD_NAME_PREFIX

string

quarkus.dynamodb.async-client.advanced.use-future-completion-thread-pool

Whether the default thread pool should be used to complete the futures returned from the HTTP client request.

When disabled, futures will be completed on the Netty event loop thread.

Environment variable: QUARKUS_DYNAMODB_ASYNC_CLIENT_ADVANCED_USE_FUTURE_COMPLETION_THREAD_POOL

boolean

true
About the Duration format

To write duration values, use the standard java.time.Duration format. See the Duration#parse() Java API documentation for more information.

You can also use a simplified format, starting with a number:

  • If the value is only a number, it represents time in seconds.

  • If the value is a number followed by ms, it represents time in milliseconds.

In other cases, the simplified format is translated to the java.time.Duration format for parsing:

  • If the value is a number followed by h, m, or s, it is prefixed with PT.

  • If the value is a number followed by d, it is prefixed with P.
About the MemorySize format

A size configuration option recognizes strings in this format (shown as a regular expression): [0-9]+[KkMmGgTtPpEeZzYy]?.

If no suffix is given, assume bytes.

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Configuration property

Type

Default

quarkus.dynamodbenhanced.client-extensions

List of extensions to load with the enhanced client

Environment variable: QUARKUS_DYNAMODBENHANCED_CLIENT_EXTENSIONS

list of string

quarkus.dynamodbenhanced.create-table-schemas

Whether a TableSchema should be created at start up for DynamoDb mappable entities annotated with DynamoDbBean or DynamoDbImmutable

TableSchema are cached and can be retrieved later with TableSchema.fromClass()

Environment variable: QUARKUS_DYNAMODBENHANCED_CREATE_TABLE_SCHEMAS

boolean

true