<?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>Question Re: Invalid URL API Management in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/invalid-url-api-management/qaa-p/751349#M213741</link>
    <description>&lt;P&gt;Hi Anand,&lt;/P&gt;&lt;P&gt;Can you share a little more details on the scenario? The microservice on AWS has an HTTP endpoint which is Internet accessible? Or this endpoint is struggling to be accessible at all?&lt;/P&gt;&lt;P&gt;I believe that if you are not able to access your AWS landscape from SAP Cloud Platform, you should be able to deploy the SAP Cloud Connector agent into your AWS landscape, in order to create a tunnel between the two.&lt;/P&gt;&lt;P&gt;But please provide a little additional information around the scenario.&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Elijah&lt;/P&gt;</description>
    <pubDate>Thu, 01 Nov 2018 05:47:38 GMT</pubDate>
    <dc:creator>Elijah_Martinez1</dc:creator>
    <dc:date>2018-11-01T05:47:38Z</dc:date>
    <item>
      <title>Invalid URL API Management</title>
      <link>https://community.sap.com/t5/technology-q-a/invalid-url-api-management/qaq-p/751348</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;We have a microsservice on AWS and am trying to manage the service using API Management. However, I am getting invalid URL as response when trying to test it from the Testing Console in API Portal (API Mgmt). If I try to call it from outside the url is not reachable. Can someone please advise if I am doing something wrong? I have created an API Proxy and trying to test this now. Any help or pointers will be appreciated.&lt;/P&gt;
  &lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/238385-invalid-url.png" /&gt;&lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;Thanks,&lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;Anand&lt;/P&gt;</description>
      <pubDate>Thu, 01 Nov 2018 04:50:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/invalid-url-api-management/qaq-p/751348</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2018-11-01T04:50:54Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid URL API Management</title>
      <link>https://community.sap.com/t5/technology-q-a/invalid-url-api-management/qaa-p/751349#M213741</link>
      <description>&lt;P&gt;Hi Anand,&lt;/P&gt;&lt;P&gt;Can you share a little more details on the scenario? The microservice on AWS has an HTTP endpoint which is Internet accessible? Or this endpoint is struggling to be accessible at all?&lt;/P&gt;&lt;P&gt;I believe that if you are not able to access your AWS landscape from SAP Cloud Platform, you should be able to deploy the SAP Cloud Connector agent into your AWS landscape, in order to create a tunnel between the two.&lt;/P&gt;&lt;P&gt;But please provide a little additional information around the scenario.&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Elijah&lt;/P&gt;</description>
      <pubDate>Thu, 01 Nov 2018 05:47:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/invalid-url-api-management/qaa-p/751349#M213741</guid>
      <dc:creator>Elijah_Martinez1</dc:creator>
      <dc:date>2018-11-01T05:47:38Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid URL API Management</title>
      <link>https://community.sap.com/t5/technology-q-a/invalid-url-api-management/qaa-p/751350#M213742</link>
      <description>&lt;P&gt;Hi Elijah,&lt;/P&gt;&lt;P&gt;Thanks for taking time to respond.&lt;/P&gt;&lt;P&gt;The microservice on AWS has HTTP endpoint is accessible over the internet and is accessible publicly. &lt;/P&gt;&lt;P&gt;API Proxy(SAP API Mgmt Cloud) -----&amp;gt; Microservice on AWS (Publicly available service).&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;U&gt;AWS Microservice when accessed directly:&lt;/U&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/238419-aws-microservice.png" /&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;U&gt;API Portal service when accessed:&lt;/U&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/238420-api-portal-service.png" /&gt;&lt;/P&gt;&lt;P&gt;Let me know if you need more clarity.&lt;/P&gt;&lt;P&gt;Thanks,&lt;BR /&gt;Anand&lt;/P&gt;</description>
      <pubDate>Thu, 01 Nov 2018 20:55:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/invalid-url-api-management/qaa-p/751350#M213742</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2018-11-01T20:55:27Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid URL API Management</title>
      <link>https://community.sap.com/t5/technology-q-a/invalid-url-api-management/qaa-p/751351#M213743</link>
      <description>&lt;P&gt;I had submitted an incident with SAP and they resolved it. SAP said that the certs were mixed up and they have fixed it now. The issue has been resolved now.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks SAP!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;</description>
      <pubDate>Thu, 08 Nov 2018 01:18:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/invalid-url-api-management/qaa-p/751351#M213743</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2018-11-08T01:18:04Z</dc:date>
    </item>
  </channel>
</rss>

