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

CDF No Longer Needs NAT or IGW #169

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

CDF No Longer Needs NAT or IGW #169

anish-kunduru opened this issue Oct 6, 2023 · 0 comments

Comments

@anish-kunduru
Copy link
Contributor

Aws Connected Device Framework Affected Module(s):

I'm submitting a ...

  • bug report
  • feature request

Description:

When CDF was first created, the IoT Core endpoints didn't support PrivateLink, so it wasn't possible to deploy CDF lambdas into a private subnet without IGW & NAT. Since all the IoT Core endpoints we currently use now support VPC-E, we should be able to remove these dependencies entirely.

Current behavior:

Expected behavior:

Steps to reproduce:

Additional Information:
IGW & NAT will be required if a customer is using SPARQL, but this not something currently supported by CDF.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant