<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Connect to private resources from API Gateway with VPC Link	</title>
	<atom:link href="https://cloudar.be/awsblog/connect-to-private-resources-from-api-gateway-with-vpc-link/feed/" rel="self" type="application/rss+xml" />
	<link>https://cloudar.be/awsblog/connect-to-private-resources-from-api-gateway-with-vpc-link/</link>
	<description>100% Focus On AWS // 100% Customer Obsession</description>
	<lastBuildDate>Mon, 26 May 2025 14:24:04 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		By: Ben Bridts		</title>
		<link>https://cloudar.be/awsblog/connect-to-private-resources-from-api-gateway-with-vpc-link/#comment-16806</link>

		<dc:creator><![CDATA[Ben Bridts]]></dc:creator>
		<pubDate>Mon, 26 May 2025 14:24:04 +0000</pubDate>
		<guid isPermaLink="false">https://cloudar.be/?p=6099#comment-16806</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://cloudar.be/awsblog/connect-to-private-resources-from-api-gateway-with-vpc-link/#comment-16622&quot;&gt;Shoff&lt;/a&gt;.

Yes,

To access private resources using a HTTP API: https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-develop-integrations-private.html
To access private resources using a REST API: https://docs.aws.amazon.com/apigateway/latest/developerguide/set-up-private-integration.html]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://cloudar.be/awsblog/connect-to-private-resources-from-api-gateway-with-vpc-link/#comment-16622">Shoff</a>.</p>
<p>Yes,</p>
<p>To access private resources using a HTTP API: <a href="https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-develop-integrations-private.html" rel="nofollow ugc">https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-develop-integrations-private.html</a><br />
To access private resources using a REST API: <a href="https://docs.aws.amazon.com/apigateway/latest/developerguide/set-up-private-integration.html" rel="nofollow ugc">https://docs.aws.amazon.com/apigateway/latest/developerguide/set-up-private-integration.html</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Shoff		</title>
		<link>https://cloudar.be/awsblog/connect-to-private-resources-from-api-gateway-with-vpc-link/#comment-16622</link>

		<dc:creator><![CDATA[Shoff]]></dc:creator>
		<pubDate>Thu, 01 May 2025 07:03:41 +0000</pubDate>
		<guid isPermaLink="false">https://cloudar.be/?p=6099#comment-16622</guid>

					<description><![CDATA[Can you use VPC Link with both REST APIs and HTTP APIs in API Gateway?]]></description>
			<content:encoded><![CDATA[<p>Can you use VPC Link with both REST APIs and HTTP APIs in API Gateway?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Stefan Tobé		</title>
		<link>https://cloudar.be/awsblog/connect-to-private-resources-from-api-gateway-with-vpc-link/#comment-47</link>

		<dc:creator><![CDATA[Stefan Tobé]]></dc:creator>
		<pubDate>Mon, 22 Apr 2019 20:11:38 +0000</pubDate>
		<guid isPermaLink="false">https://cloudar.be/?p=6099#comment-47</guid>

					<description><![CDATA[Hi Vincent,
I also experience intermittent delays with lambda services.
I have been told that whenever the time between two subsequent https calls to these lambda microservices exceed certain time (like 10 minutes) then the connection to the lambda service is disposed of by the vpc or aws infra. Most likely if you handle microservice requests within 5 minutes or so of each other as a maximum you should not experience this issue. Since clients will randomly generate requests one cannot expect every request to come in within 5 minutes so our external (internet facing) monitoring tool nagios is performing dummy lookups to these microserivces in lambda every 5 minutes in order to keep the services (and aws infra) &#039;hot standby&#039;]]></description>
			<content:encoded><![CDATA[<p>Hi Vincent,<br />
I also experience intermittent delays with lambda services.<br />
I have been told that whenever the time between two subsequent https calls to these lambda microservices exceed certain time (like 10 minutes) then the connection to the lambda service is disposed of by the vpc or aws infra. Most likely if you handle microservice requests within 5 minutes or so of each other as a maximum you should not experience this issue. Since clients will randomly generate requests one cannot expect every request to come in within 5 minutes so our external (internet facing) monitoring tool nagios is performing dummy lookups to these microserivces in lambda every 5 minutes in order to keep the services (and aws infra) &#8216;hot standby&#8217;</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Vincent Van der Kussen		</title>
		<link>https://cloudar.be/awsblog/connect-to-private-resources-from-api-gateway-with-vpc-link/#comment-46</link>

		<dc:creator><![CDATA[Vincent Van der Kussen]]></dc:creator>
		<pubDate>Thu, 28 Feb 2019 08:19:11 +0000</pubDate>
		<guid isPermaLink="false">https://cloudar.be/?p=6099#comment-46</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://cloudar.be/awsblog/connect-to-private-resources-from-api-gateway-with-vpc-link/#comment-45&quot;&gt;Bojan&lt;/a&gt;.

Hi Bojan, 

I&#039;m glad you liked the post and that it helped you out. The delays you are experiencing is something I haven&#039;t seen where we implemented the setup as described in the blogpost.
Are you sure your service on ECS is always responding within the required period?

The API Gateway url should work without delay if you are testing with a few requests. Adding a Custom Domain adds a Cloudfront distribution which might help but I would suggest to check if there are no problems on your backend (ALB -&gt; ECS -&gt; Service). AWS X-ray might be a good tool to troubleshoot your issue.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://cloudar.be/awsblog/connect-to-private-resources-from-api-gateway-with-vpc-link/#comment-45">Bojan</a>.</p>
<p>Hi Bojan, </p>
<p>I&#8217;m glad you liked the post and that it helped you out. The delays you are experiencing is something I haven&#8217;t seen where we implemented the setup as described in the blogpost.<br />
Are you sure your service on ECS is always responding within the required period?</p>
<p>The API Gateway url should work without delay if you are testing with a few requests. Adding a Custom Domain adds a Cloudfront distribution which might help but I would suggest to check if there are no problems on your backend (ALB -> ECS -> Service). AWS X-ray might be a good tool to troubleshoot your issue.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Bojan		</title>
		<link>https://cloudar.be/awsblog/connect-to-private-resources-from-api-gateway-with-vpc-link/#comment-45</link>

		<dc:creator><![CDATA[Bojan]]></dc:creator>
		<pubDate>Tue, 19 Feb 2019 20:13:25 +0000</pubDate>
		<guid isPermaLink="false">https://cloudar.be/?p=6099#comment-45</guid>

					<description><![CDATA[Nice post. Really helpfull. I have case when I have deployed microservices in ecs cluster and I want to access them via api gateway and vpc link. Everythings work well except that every third or second request tooks 5 - 10 second. Sometimesbit takes only 20ms. I tested this with url provided from api gateway after deploy. Should I use domain instead? Will this help to solve performance issue.]]></description>
			<content:encoded><![CDATA[<p>Nice post. Really helpfull. I have case when I have deployed microservices in ecs cluster and I want to access them via api gateway and vpc link. Everythings work well except that every third or second request tooks 5 &#8211; 10 second. Sometimesbit takes only 20ms. I tested this with url provided from api gateway after deploy. Should I use domain instead? Will this help to solve performance issue.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
