Aws Connected Device Framework Affected Module(s):
I'm submitting a ...
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.
Aws Connected Device Framework Affected Module(s):
I'm submitting a ...
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.