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.

Sign up for GitHub

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

Jump to bottom

APIGW Cannot Be Private and Have an Authorization Mechanism #102

Open
1 of 2 tasks
anish-kunduru opened this issue Feb 13, 2023 · 0 comments
Open
1 of 2 tasks

APIGW Cannot Be Private and Have an Authorization Mechanism #102

anish-kunduru opened this issue Feb 13, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@anish-kunduru
Copy link
Contributor

Aws Connected Device Framework Affected Module(s):

I'm submitting a ...

  • bug report
  • feature request

Description:

Currently, it is not possible to deploy CDF in a manner where the APIGW is restricted from public access while also checking through another authorization mechanism.

Current behavior:

Deployed APIGWs can either be private or auth protected.

Expected behavior:

APIGW can be deployed with multiple properties. For example, private & IAM auth or private & Cognito.

Steps to reproduce:

Additional Information:
@anish-kunduru anish-kunduru added the enhancement New feature or request label Feb 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@anish-kunduru