Support Multi-tenancy

[medhost-bfindeisen]

Add support for multi-tenancy for a more economic Saas offering without affecting the existing non-tenant based approach.

Initial design proposal:

• API Gateway will be enhanced to pass tenant-id as part of URL - https://fhir.server.com/tenant/{tenant-id}/{resource}

• API Gateway - extract tenant-id and pass it as parameter

• Lambda write into tenant based table - resource-db-dev-1-tenant-id

• DynamoDB - streaming pass this data to ElasticSearch

• Separate - index per tenant/resource OR - global resource index

• Meta-data/conformance page need to incorporate tenant-id based approach

• lack of a tenant id would use the existing non-tenant design

Open design items:

• Tenant S3 bucket binary storage

• Finalize ES design decision

[Dunmail]

+1 We use FWoA as a facade on multiple systems. We would benefit from the tenant-id in the URL and as a parameter.

[rsmayda]

Thanks for opening this issue -- If folks from our community are interested in this please 'thumbs-up' up the issue.

We would love to get diverse use-cases to ensure FWoA is built to support flexibility

[asrour-vytalize]

Any updates on this?

[medhost-bfindeisen]

Any updates on this?

Thanks for the interest - our team is wrapping up work on this and hope to have a PR up in the near future

[asrour-vytalize]

Can you share the code/branch?
Because I am working on a solution for us.

[rashedoumar]

hey @medhost-bfindeisen you are doing a great job here , what's the update on the Multi-tenancy ?

[ericfuxealth]

@@medhost-bfindeisen We are interested to contribute to the multi-tenant solution. Would love to connect.

[rsmayda]

We will be merging in this feature by end of this week!

[rsmayda]

Merged and released! https://github.com/awslabs/fhir-works-on-aws-deployment/releases/tag/v4.0.0