Quarkus Lambda Native Image Memory Leakage

[apurvar1010]

I have created an amazon lambda using Quarkus framework and packaged it using GraalVM native-image. The functionalities is quite simple with basic validations, however I am creating Dynamo DB client and SQS clients. I have instantiated those clients outside of Quarkus Request Handler and using Http Client Connection while building the clients as mentioned in this guide: https://quarkus.io/guides/amazon-lambda#aws-sdk-v2

In the AWS console, I have set the max memory as 256 mb (This is the requirement). The first invocation takes about 1000ms and uses 74 mb. However for each consecutive invocation of lambda, the memory consumption keeps on increasing and it instantiates all the clients (Dynamo DB and SQS) again and again. Is there a way to keep the memory consumed lower and instantiating these clients once in a while as and when required?

The Lambda handler code is as follows:

public class TestLambda implements RequestHandler<KinesisEvent, OutputObject> {

    public static final Logger LOGGER = LoggerFactory.getLogger(TestLambda.class);
    private final GetRecords getRecordsObj = new GetRecords();
    private final DynamoDBService dynamoDB = new DynamoDBService();
    private final TableConfiguration tableConfiguration = dynamoDB.getDynamoDBItem();
    private final AssumeRole assumeRole = new AssumeRole(this.tableConfiguration);
    private StsAssumeRoleCredentialsProvider credentialsProvider = assumeRole.getCredentialsProvider();
    private SendMessage sendMessage = new SendMessage(tableConfiguration, credentialsProvider);

    @Override
    public OutputObject handleRequest(KinesisEvent kinesisEvent, Context context) {
        LOGGER.info("Handler started");

        List<String> collectionPayload = getRecordsObj.records(kinesisEvent);
        String payload = collectionPayload.toString();

        if (payload != null) {
            sendMessage.SendMessageToSqs(payload);
        }
        OutputObject obj = new OutputObject();
        obj.setResult(payload);
        return obj;
    }
}

One of the example of initiating the client is this:

DynamoDbClient dynamoDB = DynamoDbClient.builder()
                .region(Region.AP_SOUTHEAST_2)
                .httpClient(UrlConnectionHttpClient.builder().build())
                .build();

For each of the lambda invocation, the clients are getting initiated and I was wondering if there is a way to limit it to one in let's say 100 requests.
If not, is there any other way to overcome memory leakage.