RFC 012: API Architecture
Last updated
Last updated
This RFC proposes a solution for serving Wellcome Collection APIs from a single domain, api.wellcomecollection.org, using AWS API Gateway and CloudFront.
Last modified: 2019-01-25T15:26:28+00:00
Wellcome Collection provides multiple APIs to interact with our data. A single API can be made up of multiple services, providing responses at different endpoints.
Some API endpoints require authentication, while others are public and would benefit from rate limiting.
In order to provide a consistent location for Wellcome Collection APIs we'd like to serve all APIs from .
As of 09/01/2019 we are focusing on serving the storage and catalogue APIs from api.wellcomecollection.org. The storage API requires authentication, the catalogue API does not.
We are using to host our REST APIs and making use of a to serve requests via an .
We wish to segregate infrastructure projects into different AWS accounts for simplicity and security. See .
Currently it is not possible to point a from one account to another account using API Gateway.
The recommended solution is to use an to field requests to api.wellcomecollection.org and then use to serve requests from API Gateway in other accounts using their own Custom Domains.
See:
