Post reply

Getting In: Running External Code in a Locked-Down PaaS

  • July 16, 2025 at 7:00 pm

    #4622326

    Comments posted to this topic are about the item Getting In: Running External Code in a Locked-Down PaaS

    Cheers, Tonie

    See you at Sea(QL) this year?
    https://seaql.nl

  • July 17, 2025 at 7:10 pm

    #4623925

    Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

  • July 18, 2025 at 12:00 pm

    #4624216

    Thanks for sharing this insightful article!

    Running external code in a locked-down PaaS environment is always a challenge, especially with the increasing focus on security and compliance. One approach we've found useful is leveraging managed connectors or services (such as Azure Functions with approved bindings or Azure API Management) to isolate and control external code execution. This keeps the PaaS layer secure while still enabling integration with external processes or APIs.

    It’s also crucial to check whether the platform allows private endpoints, firewall rules, or service tags that can restrict traffic to only trusted services. That way, even if you're calling out to external systems, you’re doing so in a controlled, auditable way.

    Would be great to hear if others have tried containerized microservices as a companion to a locked-down PaaS to offload such tasks securely.

     

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply