components-contrib icon indicating copy to clipboard operation
components-contrib copied to clipboard

Published 20 hours ago • verified publisher icon dapr

Support Amazon Aurora within Dapr

Open sicoyle opened this issue 1 year ago • 5 comments

Describe the feature

There currently is no support for Amazon Aurora within Dapr, ie. there is no state.aws.aurora. I wanted to create an issue to discuss the 2 options to introduce support for Amazon Aurora as a component.

  1. Update the PostgreSQL component with a light wrapper adding the required AWS auth fields
  2. Add a specific component for state.aws.aurora

What would be the preferred approach here?

Release Note

RELEASE NOTE: Add Amazon Aurora support within Dapr

sicoyle avatar Dec 05 '23 18:12 sicoyle

Documenting the discussion on discord over to here:

Amazon Aurora supports multiple database technologies. Adding a generic Aurora component would introduce maintenance overhead that is unideal, and so there is a way to support it for the existing PostgreSQL component. Alternatively, this can become a new component that under the hood uses the shared postgres implementation (see CockroachDB for reference).

Reference code thanks to @berndverst

  • https://github.com/dapr/components-contrib/tree/main/common/component/postgresql

Additionally, Azure Postgres is supported using a new enableAzureAD metadata field. See below for reference for a corresponding "Amazon Postgres" implementation:

  • https://github.com/dapr/components-contrib/pull/2970
  • https://github.com/dapr/components-contrib/pull/2971

The above summary is compiled from the Discord discussion here: https://discord.com/channels/778680217417809931/781589820128493598/1181670307065499678

sicoyle avatar Dec 05 '23 19:12 sicoyle

If someone could add the help wanted label, then that would be much appreciated!

sicoyle avatar Dec 05 '23 19:12 sicoyle

Its best to use the existing component and add the required AWS configuration to it. If it can work transparently than great, if not then it can be set using metadata.

yaron2 avatar Dec 06 '23 05:12 yaron2

Its best to use the existing component and add the required AWS configuration to it. If it can work transparently than great, if not then it can be set using metadata.

Yup. That was exactly my recommendation.

See entire thread starting here: https://discord.com/channels/778680217417809931/781589820128493598/1181677547818328134

berndverst avatar Dec 07 '23 19:12 berndverst

/assign

sicoyle avatar Mar 01 '24 21:03 sicoyle