serverless / serverless/examples

Question: Is it possible to share an Authorizer or HTTP Api

Open
#484 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
11.5k
Forks
4.4k
Avg merge
2h 55m
Merged PRs (30d)
3

Description

I've seen multiple threads and discussion around splitting up services into their own serverless.yml file setups.

Including this example showing sharing an API Gateway.
https://github.com/serverless/examples/tree/master/aws-node-shared-gateway

Is it possible to share an HTTP Api, instead of the RestApi in this example? I have a question on SO regarding splitting up a HTTP Api service using an authorizer which falls into the same question.
https://stackoverflow.com/questions/60968313/sharing-an-authorizer-between-different-http-api-services-in-aws-with-serverless

I have seen various threads on Export/Fn:Import information, but I cannot see documentation on what should be exported and imported in the different services to get this working.

For example, if you Export an Authorizer/Cognito User Pool, what should value should you export and where/how do you Fn: Import that value in sub-services?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the aws-node-shared-gateway example and compare its RestApi setup with HTTP Api services in serverless.yml. Review the linked Stack Overflow discussion and the issue's Fn::ImportValue question; done would be documented, working guidance for sharing an HTTP Api authorizer or a clear statement that it is unsupported.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, javascript
Domain
api, authentication, cloud
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.