search

awslabs / fhir-works-on-aws-routing

The routing implementation of the FHIR Works on AWS framework. Finding the correct component to handle the HTTP FHIR request
Apache License 2.0
31 stars 26 forks source link

feat: Feature/private api gateway #153

Closed Zambonilli closed 1 year ago

Zambonilli commented 2 years ago

Issue #, if available: https://github.com/awslabs/fhir-works-on-aws-deployment/issues/378

Description of changes: Added logic to the setServerUrl middleware to dynamically compute the TLD based on the request's hostname if fwoa is currently configured to in server.dynamicHostName. This allows for supporting private API gateways, custom DNS and cname TLDs and fixes public API links being used in search bundle response's link values.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

nisankep commented 1 year ago

FHIR Works on AWS has been moved to maintenance mode. While in maintenance, we will not add any new features to this solution. All security issues should be reported directly to AWS Security at [aws-security@amazon.com] (mailto:security@amazon.com). If you are new to this solution, we advise you to explore using [HealthLake] (https://aws.amazon.com/healthlake), which is our managed service for building FHIR based transactional and analytics applications. You can get started by contacting your AWS Account team. If you are an existing customer of FHIR Works on AWS, and have additional questions or need immediate help, please reach out to fwoa-migration-support@amazon.com or contact your AWS Account team.