Skip to content
This repository was archived by the owner on Aug 7, 2026. It is now read-only.
This repository was archived by the owner on Aug 7, 2026. It is now read-only.

CDF No Longer Needs NAT or IGW #169

Description

@anish-kunduru

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions