Skip to content
View suneetnangia's full-sized avatar

Organizations

@Azure

Block or report suneetnangia

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Please don't include any personal information such as legal names or email addresses. Maximum 100 characters, markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse

Pinned Loading

  1. wasm-orchestration-with-spin wasm-orchestration-with-spin Public

    Repository to demonstrate Wasm modules orchestration with containers in Kubernetes

    Shell 3 3

  2. IoTEdgeAccess IoTEdgeAccess Public

    IoT Edge module to allow secure remote access.

    C# 17 5

  3. distributed-az-edge-framework distributed-az-edge-framework Public archive

    This accelerator is (being) developed to allow heavy edge solutions to run on K8s, in distributed and resilient manner.

    PowerShell 5 5

  4. Iot Hub Secure Data Egress with Priv... Iot Hub Secure Data Egress with Private Network and Public Device Endpoint
    1
    # Iot Hub Secure Data Egress with Private Network and Public Device Endpoint
    2
    
                  
    3
    This document explains how we can securely create IoT Hub in a [private virtual network](https://learn.microsoft.com/en-us/azure/iot-hub/virtual-network-support) and at the same time allow devices (both leaf and edge devices) to connect to this IoT Hub **without** being part of the virtual network, the latter is the key part of the challenge we are addressing in this solution. If we enforce devices to be in the same network as that of IoT Hub, the flexibility is lost as not all devices can connect to Azure Virtual Network without a significant pre-work ahead of time, which may not even be an option in some cases. On the other hand, if we do not enable Private Link for IoT Hub, the data egress endpoint is made publicly available which is not always ideal, as most customers would like to keep data processing private.
    4
    
                  
    5
    The following diagram provides the overarching solution and it's key components:
  5. spinkube/spin-trigger-mqtt spinkube/spin-trigger-mqtt Public

    An MQTT trigger for Spin

    Rust 16 10

  6. DynamicCAFExecutionEngine DynamicCAFExecutionEngine Public

    PaaS solution to execute CAF Landing Zones via API

    HCL 1