<?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 for Cloudar	</title>
	<atom:link href="https://cloudar.be/comments/feed/" rel="self" type="application/rss+xml" />
	<link>https://cloudar.be/</link>
	<description>100% Focus On AWS // 100% Customer Obsession</description>
	<lastBuildDate>Sat, 15 Nov 2025 10:54:11 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		Comment on Aws workspaces with multi-factor authentication by multiOTP		</title>
		<link>https://cloudar.be/awsblog/aws-workspaces-with-multi-factor-authentication/#comment-18406</link>

		<dc:creator><![CDATA[multiOTP]]></dc:creator>
		<pubDate>Sat, 15 Nov 2025 10:54:11 +0000</pubDate>
		<guid isPermaLink="false">https://cloudar.be/?p=6554#comment-18406</guid>

					<description><![CDATA[The latest version 5.10.0.3 (2025-11-04) is available (in open source as always) on https://github.com/multiOTP/multiotp]]></description>
			<content:encoded><![CDATA[<p>The latest version 5.10.0.3 (2025-11-04) is available (in open source as always) on <a href="https://github.com/multiOTP/multiotp" rel="nofollow ugc">https://github.com/multiOTP/multiotp</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Connect to private resources from API Gateway with VPC Link 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>
		Comment on Connect to private resources from API Gateway with VPC Link 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>
		Comment on Integrating Fail2Ban with AWS Network ACLs by Adam		</title>
		<link>https://cloudar.be/awsblog/integrating-fail2ban-with-aws-network-acls/#comment-7985</link>

		<dc:creator><![CDATA[Adam]]></dc:creator>
		<pubDate>Wed, 08 May 2024 15:15:43 +0000</pubDate>
		<guid isPermaLink="false">https://cloudar.be/?p=7782#comment-7985</guid>

					<description><![CDATA[fail2ban isn&#039;t in the Amazon Linux yum repo, so this falls at the first hurdle]]></description>
			<content:encoded><![CDATA[<p>fail2ban isn&#8217;t in the Amazon Linux yum repo, so this falls at the first hurdle</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Undocumented feature: Using Template Constraint Rules in CloudFormation by Steve Kinsman		</title>
		<link>https://cloudar.be/awsblog/undocumented-feature-using-template-constraint-rules-in-cloudformation/#comment-48</link>

		<dc:creator><![CDATA[Steve Kinsman]]></dc:creator>
		<pubDate>Wed, 21 Oct 2020 04:05:25 +0000</pubDate>
		<guid isPermaLink="false">https://cloudar.be/?p=11349#comment-48</guid>

					<description><![CDATA[Thanks for blogging that Ben, it&#039;s always fun to play with new things in CloudFormation!]]></description>
			<content:encoded><![CDATA[<p>Thanks for blogging that Ben, it&#8217;s always fun to play with new things in CloudFormation!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Using the Application Load Balancer and WAF to replace CloudFront Security Groups by Jorge		</title>
		<link>https://cloudar.be/awsblog/using-the-application-load-balancer-and-waf-to-replace-cloudfront-security-groups/#comment-37</link>

		<dc:creator><![CDATA[Jorge]]></dc:creator>
		<pubDate>Thu, 30 Apr 2020 12:20:55 +0000</pubDate>
		<guid isPermaLink="false">https://cloudar.be/?p=3681#comment-37</guid>

					<description><![CDATA[Good post. Thanks for the tip.]]></description>
			<content:encoded><![CDATA[<p>Good post. Thanks for the tip.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Enabling Federation to AWS Using Windows Active Directory, ADFS and SAML by eijer		</title>
		<link>https://cloudar.be/awsblog/enabling-federation-to-aws-using-windows-active-directory-adfs-and-saml/#comment-26</link>

		<dc:creator><![CDATA[eijer]]></dc:creator>
		<pubDate>Wed, 22 Apr 2020 04:18:24 +0000</pubDate>
		<guid isPermaLink="false">https://cloudar.be/?p=3352#comment-26</guid>

					<description><![CDATA[Hello,

Thank for informative article!

I would like to configure AWS Cognito to receive the user&#039;s department name and user&#039;s full name from ADFS. At this time, I would like to get help if you have experience in how to construct the Claims rule.]]></description>
			<content:encoded><![CDATA[<p>Hello,</p>
<p>Thank for informative article!</p>
<p>I would like to configure AWS Cognito to receive the user&#8217;s department name and user&#8217;s full name from ADFS. At this time, I would like to get help if you have experience in how to construct the Claims rule.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Windows servers patching with AWS EC2 Systems Manager by Rutger Beyen		</title>
		<link>https://cloudar.be/awsblog/windows-servers-patching-with-aws-ec2-systems-manager/#comment-43</link>

		<dc:creator><![CDATA[Rutger Beyen]]></dc:creator>
		<pubDate>Mon, 06 Apr 2020 10:36:21 +0000</pubDate>
		<guid isPermaLink="false">https://cloudar.be/?p=3733#comment-43</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://cloudar.be/awsblog/windows-servers-patching-with-aws-ec2-systems-manager/#comment-42&quot;&gt;pradeep&lt;/a&gt;.

Hello Pradeep.

As far as my knowledge goes, there&#039;s no such one-click solution available.
However, what we do here at Cloudar is running the SSM Maintenance Window task with the option &quot;Enable SNS notifications&quot; set to true. This will cause the results of the Maintenance Window to be delivered to an SNS topic. From this SNS topic you can either subscribe your email address, or a Lambda function which can further sanitize and cleanup the output according to your preferences, as by default you will get an ugly JSON.
Alternatively you can query your instance patch results using the CLI with &#039;aws ssm describe-instance-patches&#039; or &#039;aws ssm describe-instance-patch-states&#039;.

Regards,
Rutger]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://cloudar.be/awsblog/windows-servers-patching-with-aws-ec2-systems-manager/#comment-42">pradeep</a>.</p>
<p>Hello Pradeep.</p>
<p>As far as my knowledge goes, there&#8217;s no such one-click solution available.<br />
However, what we do here at Cloudar is running the SSM Maintenance Window task with the option &#8220;Enable SNS notifications&#8221; set to true. This will cause the results of the Maintenance Window to be delivered to an SNS topic. From this SNS topic you can either subscribe your email address, or a Lambda function which can further sanitize and cleanup the output according to your preferences, as by default you will get an ugly JSON.<br />
Alternatively you can query your instance patch results using the CLI with &#8216;aws ssm describe-instance-patches&#8217; or &#8216;aws ssm describe-instance-patch-states&#8217;.</p>
<p>Regards,<br />
Rutger</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Windows servers patching with AWS EC2 Systems Manager by pradeep		</title>
		<link>https://cloudar.be/awsblog/windows-servers-patching-with-aws-ec2-systems-manager/#comment-42</link>

		<dc:creator><![CDATA[pradeep]]></dc:creator>
		<pubDate>Mon, 06 Apr 2020 09:43:44 +0000</pubDate>
		<guid isPermaLink="false">https://cloudar.be/?p=3733#comment-42</guid>

					<description><![CDATA[Hi There,

Is there any way after scanning the instances, Could we get the result to our Inbox. 
For example like only Non-complaint issues in a particular instance.]]></description>
			<content:encoded><![CDATA[<p>Hi There,</p>
<p>Is there any way after scanning the instances, Could we get the result to our Inbox.<br />
For example like only Non-complaint issues in a particular instance.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Multicast on AWS by Ben Bridts		</title>
		<link>https://cloudar.be/awsblog/multicast-on-aws/#comment-9</link>

		<dc:creator><![CDATA[Ben Bridts]]></dc:creator>
		<pubDate>Thu, 12 Dec 2019 11:55:43 +0000</pubDate>
		<guid isPermaLink="false">https://cloudar.be/?p=323#comment-9</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://cloudar.be/awsblog/multicast-on-aws/#comment-8&quot;&gt;Steve&lt;/a&gt;.

Hi Steve,

AWS released multicast support for Transit Gateway. If that covers your use case, I&#039;d recommend using that: https://aws.amazon.com/about-aws/whats-new/2019/12/run-ip-multicast-workloads-aws-transit-gateway/

Since this solution uses an overlay network the scale will be limited by the performance of n2n. They try to use peer to peer connections, but your multicast traffic will eventually have to be sent over the underlying vpc network. I&#039;d recommend doing a load test to make sure the performance matches your expectations.

If you want to load balance the supernode, you&#039;d have to search the n2n documentation to see if that is possible.

Kind regards,
Ben]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://cloudar.be/awsblog/multicast-on-aws/#comment-8">Steve</a>.</p>
<p>Hi Steve,</p>
<p>AWS released multicast support for Transit Gateway. If that covers your use case, I&#8217;d recommend using that: <a href="https://aws.amazon.com/about-aws/whats-new/2019/12/run-ip-multicast-workloads-aws-transit-gateway/" rel="nofollow ugc">https://aws.amazon.com/about-aws/whats-new/2019/12/run-ip-multicast-workloads-aws-transit-gateway/</a></p>
<p>Since this solution uses an overlay network the scale will be limited by the performance of n2n. They try to use peer to peer connections, but your multicast traffic will eventually have to be sent over the underlying vpc network. I&#8217;d recommend doing a load test to make sure the performance matches your expectations.</p>
<p>If you want to load balance the supernode, you&#8217;d have to search the n2n documentation to see if that is possible.</p>
<p>Kind regards,<br />
Ben</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
