<?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: Dynatrace Saas IP for triggering workflow actio s in Automations</title>
    <link>https://community.dynatrace.com/t5/Automations/Dynatrace-SaaS-IP-for-triggering-workflow-actions/m-p/269340#M2027</link>
    <description>&lt;P&gt;Currently, the outgoing IP address is not fixed, and depends on the data-center your environment is hosted in (and even then, the list of IP addresses can be quite long).&lt;/P&gt;&lt;P&gt;If you want a stable IP address for outgoing traffic, at least right now, you need to &lt;A href="https://docs.dynatrace.com/docs/ingest-from/edgeconnect" target="_blank"&gt;setup and use Edge Connect&lt;/A&gt;.&lt;/P&gt;</description>
    <pubDate>Wed, 05 Feb 2025 16:55:08 GMT</pubDate>
    <dc:creator>christian_kreuz</dc:creator>
    <dc:date>2025-02-05T16:55:08Z</dc:date>
    <item>
      <title>Dynatrace SaaS IP for triggering workflow actions</title>
      <link>https://community.dynatrace.com/t5/Automations/Dynatrace-SaaS-IP-for-triggering-workflow-actions/m-p/268386#M2014</link>
      <description>&lt;P&gt;I want to trigger an ansible job template in the workflow. My ansible is hosted in AWS EC2 instance, I need the IPs from which connection will be made to be added to the Security Groups. How to find what IPs need to be added?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;FYI - I tried getting the IP from Deploy Activegate and got 3 IP address, but that didnt work. I'm getting connection timed-out in the workflow&lt;/P&gt;</description>
      <pubDate>Thu, 06 Feb 2025 08:44:15 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Automations/Dynatrace-SaaS-IP-for-triggering-workflow-actions/m-p/268386#M2014</guid>
      <dc:creator>nprashiyer</dc:creator>
      <dc:date>2025-02-06T08:44:15Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace Saas IP for triggering workflow actio s</title>
      <link>https://community.dynatrace.com/t5/Automations/Dynatrace-SaaS-IP-for-triggering-workflow-actions/m-p/268405#M2015</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/85722"&gt;@nprashiyer&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;AG and OA communicate with SaaS via these IP addresses. I guess you can expect communication from these IP addresses if Saas direclty call your Ansible instance.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Mizs_0-1737917785768.png" style="width: 715px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/25965iCB567A16D2444A0A/image-dimensions/715x441?v=v2" width="715" height="441" role="button" title="Mizs_0-1737917785768.png" alt="Mizs_0-1737917785768.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;I hope it helps.&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;János&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 26 Jan 2025 18:59:05 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Automations/Dynatrace-SaaS-IP-for-triggering-workflow-actions/m-p/268405#M2015</guid>
      <dc:creator>Mizső</dc:creator>
      <dc:date>2025-01-26T18:59:05Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace Saas IP for triggering workflow actio s</title>
      <link>https://community.dynatrace.com/t5/Automations/Dynatrace-SaaS-IP-for-triggering-workflow-actions/m-p/269340#M2027</link>
      <description>&lt;P&gt;Currently, the outgoing IP address is not fixed, and depends on the data-center your environment is hosted in (and even then, the list of IP addresses can be quite long).&lt;/P&gt;&lt;P&gt;If you want a stable IP address for outgoing traffic, at least right now, you need to &lt;A href="https://docs.dynatrace.com/docs/ingest-from/edgeconnect" target="_blank"&gt;setup and use Edge Connect&lt;/A&gt;.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Feb 2025 16:55:08 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Automations/Dynatrace-SaaS-IP-for-triggering-workflow-actions/m-p/269340#M2027</guid>
      <dc:creator>christian_kreuz</dc:creator>
      <dc:date>2025-02-05T16:55:08Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace Saas IP for triggering workflow actio s</title>
      <link>https://community.dynatrace.com/t5/Automations/Dynatrace-SaaS-IP-for-triggering-workflow-actions/m-p/269341#M2028</link>
      <description>&lt;P&gt;Sorry, but this is not true for Workflows and Functions.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Feb 2025 16:55:26 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Automations/Dynatrace-SaaS-IP-for-triggering-workflow-actions/m-p/269341#M2028</guid>
      <dc:creator>christian_kreuz</dc:creator>
      <dc:date>2025-02-05T16:55:26Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace SaaS IP for triggering workflow actions</title>
      <link>https://community.dynatrace.com/t5/Automations/Dynatrace-SaaS-IP-for-triggering-workflow-actions/m-p/288359#M2419</link>
      <description>&lt;P&gt;I would like to contribute to this post as follows:&amp;nbsp;&lt;/P&gt;&lt;H3&gt;&lt;STRONG&gt;Dynatrace Workflows &amp;amp; App Engine (SaaS)&lt;/STRONG&gt;&lt;/H3&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Outbound IPs are not fixed&lt;/STRONG&gt;:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Dynatrace SaaS environments use &lt;STRONG&gt;dynamic outbound IPs&lt;/STRONG&gt; for workflows and JavaScript runtime functions.&lt;/LI&gt;&lt;LI&gt;These IPs &lt;STRONG&gt;change frequently&lt;/STRONG&gt; and are &lt;STRONG&gt;not predictable&lt;/STRONG&gt;. &lt;A href="https://community.dynatrace.com/t5/Automations/IP-Allow-List-SaaS-Dynatrace-Outgoing-IPs-from-Javascript/m-p/285932" target="_blank" rel="noopener"&gt;[community....atrace.com]&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;No official static list available&lt;/STRONG&gt;:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Dynatrace does &lt;STRONG&gt;not publish a fixed list&lt;/STRONG&gt; of outbound IPs for workflows or AppEngine.&lt;/LI&gt;&lt;LI&gt;If you need to allow outbound traffic from Dynatrace to your infrastructure, you must &lt;STRONG&gt;sample the IPs&lt;/STRONG&gt; during workflow execution or use &lt;STRONG&gt;Edge Connect&lt;/STRONG&gt; to route traffic through a known IP. &lt;A href="https://community.dynatrace.com/t5/Automations/Dynatrace-SaaS-IP-for-triggering-workflow-actions/m-p/268386" target="_blank" rel="noopener"&gt;[community....atrace.com]&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Workaround: Use Edge Connect&lt;/STRONG&gt;:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;To get &lt;STRONG&gt;stable outbound IPs&lt;/STRONG&gt;, Dynatrace recommends setting up &lt;STRONG&gt;Edge Connect&lt;/STRONG&gt;, which acts as a proxy and gives you control over the IPs used for outbound traffic. &lt;A href="https://community.dynatrace.com/t5/Automations/Dynatrace-SaaS-IP-for-triggering-workflow-actions/m-p/268386" target="_blank" rel="noopener"&gt;[community....atrace.com]&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Allowlisting External Hosts&lt;/STRONG&gt;:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;You can configure which external hosts Dynatrace workflows and functions can connect to via:&lt;UL&gt;&lt;LI&gt;Settings &amp;gt; General &amp;gt; Environment Management &amp;gt; External Requests&lt;/LI&gt;&lt;LI&gt;Add domains or IPs&amp;nbsp;&amp;nbsp;&lt;A href="https://docs.dynatrace.com/docs/manage/account-management/settings/ip-allowlist" target="_blank" rel="noopener"&gt;[docs.dynatrace.com]&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/OL&gt;</description>
      <pubDate>Wed, 22 Oct 2025 22:41:40 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Automations/Dynatrace-SaaS-IP-for-triggering-workflow-actions/m-p/288359#M2419</guid>
      <dc:creator>MarwanC</dc:creator>
      <dc:date>2025-10-22T22:41:40Z</dc:date>
    </item>
  </channel>
</rss>

