<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Security options when accessing an external API from a Serverless Function in APIs &amp; Integrations</title>
    <link>https://community.hubspot.com/t5/APIs-Integrations/Security-options-when-accessing-an-external-API-from-a/m-p/468163#M45429</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/200831"&gt;@RobertBaminger&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The exact minutiae of firewalls is a little outside my realm of expertise, as I am not a network engineer, but there is an idea that I have. Since the serverless function has a different IP every time you call it, though I have not tested this, I am assuming this is the case otherwise you would just allowlist the IP, this gives me just one idea of setting up some sort of middleman. Something like just an AWS EC2 instance, or other VPS, that just acts as a middleman, which you can give an IP address, which you then are able to white list. From there on the compute instance you could set up some sort of basic authentication, but if you are going that far you may as well just run all of your code off of the instance anyways. Perhaps someone with a better background in networking engineering could step in here.&lt;/P&gt;</description>
    <pubDate>Wed, 28 Jul 2021 14:53:05 GMT</pubDate>
    <dc:creator>JBeatty</dc:creator>
    <dc:date>2021-07-28T14:53:05Z</dc:date>
  </channel>
</rss>

