Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add AWS API Gateway support #6111

Closed
achrinza opened this issue Aug 13, 2020 · 2 comments
Closed

Add AWS API Gateway support #6111

achrinza opened this issue Aug 13, 2020 · 2 comments

Comments

@achrinza
Copy link
Member

achrinza commented Aug 13, 2020

Inspired by @loopback/apiconnect

AWS API Gateway is a SaaS offering that provides tools to manage the full API lifecycle. It is used in tangent with AWS Lambda to expose HTTP, REST and WebSocket APIs. It's capabilities include, but not withstanding:

  • Multi-stage API lifecycle management (e.g. dev, test, prod)
  • API documentation
  • API key management
  • Rate limiting
  • etc.

Sidenote: AWS API Gateway with Lambda and AWS API Gateway with HTTP Proxy (REST API) are 2 distinct integrations that can be supported by LoopBack 4 applications.

Suggestion

Implement a LoopBack 4 extension that:

  • Autofills AWS API Gateway OpenAPI extensions (OpenAPI enhancer 1)
  • Refactors aforementioned OpenAPI extensions where possible (OpenAPI enhancer 2)
  • Normalizes AWS API Gateway HTTP header remappings (Sequence Middleware)
  • Logs use of restricted HTTP headers or unsupported features (see link above) (Sequence Middleware)

Use Cases

  • Adds interoperability of LoopBack 4 applications on and off-AWS API Gateway architectures without needing developers to worry about restriction nuances
  • Allows integration of AWS-specific features (e.g. IAM-based authentication)

Examples

TBD

Acceptance criteria

TBD - will be filled by the team.

@stale
Copy link

stale bot commented Jul 14, 2021

This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository. This issue will be closed within 30 days of being stale.

@stale stale bot added the stale label Jul 14, 2021
@stale
Copy link

stale bot commented Aug 13, 2021

This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository.

@stale stale bot closed this as completed Aug 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants