Matt

Also suffering from this I believe this is caused when no `credentials` are provided to the Signer configuration, it falls back to using `fromNodeProviderChain` in `@aws-sdk/credential-providers`, but does so without...

For now my workaround is ```js import { fromNodeProviderChain } from '@aws-sdk/credential-providers' import { Signer } from '@aws-sdk/rds-signer' const region = process.env.AWS_REGION ?? 'eu-west-1' const signer = new Signer({ region,...

On further digging, this actually appears to stem from the JSON Schema property that the `zod-to-json-schema` lib outputs And I can reproduce on the standard JSON serde by manually setting...

Yeah let's close this issue as definitely not a restate-server issue I've just thought of a possible "solution", which is to prevent the usage of optional zod types (the root...

> From looking at the code for RDS Signer, it doesn't make any actual network requests. Therefore Im not sure what the expected outcome of adding the custom handler would...

In the meantime, you can do this manually yourself: ```js import https from 'https'; import { fromNodeProviderChain } from '@aws-sdk/credential-providers'; import { Signer } from '@aws-sdk/rds-signer'; const signer = new...

My use case would be a static cron, not dynamic on application events, to start a business process at the same time on the same weekday each week, e.g. 12:00...