<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Artem Lovan &#8211; Noise</title>
	<atom:link href="https://noise.getoto.net/author/artem-lovan/feed/" rel="self" type="application/rss+xml" />
	<link>https://noise.getoto.net</link>
	<description>The collective thoughts of the interwebz</description>
	<lastBuildDate>Fri, 23 Jul 2021 00:00:26 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8.2</generator>
	<item>
		<title>The three most important AWS WAF rate-based rules</title>
		<link>https://noise.getoto.net/2021/07/23/the-three-most-important-aws-waf-rate-based-rules/</link>
		
		<dc:creator><![CDATA[Artem Lovan]]></dc:creator>
		<pubDate>Fri, 23 Jul 2021 00:00:26 +0000</pubDate>
				<category><![CDATA[Advanced (300)]]></category>
		<category><![CDATA[Amazon Athena]]></category>
		<category><![CDATA[AWS Shield]]></category>
		<category><![CDATA[AWS Threat Research Team]]></category>
		<category><![CDATA[AWS WAF]]></category>
		<category><![CDATA[Security Blog]]></category>
		<category><![CDATA[Security, Identity & Compliance]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=003341b8dae4740fde514a1ddc728d2f</guid>

					<description><![CDATA[In this post, we explain what the three most important AWS WAF rate-based rules are for proactively protecting your web applications against common HTTP flood events, and how to implement these rules. We share what the Shield Response Team (SRT) has learned from helping customers respond to HTTP floods and show how all AWS WAF […]]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>How to restrict IAM roles to access AWS resources from specific geolocations using AWS Client VPN</title>
		<link>https://noise.getoto.net/2021/07/20/how-to-restrict-iam-roles-to-access-aws-resources-from-specific-geolocations-using-aws-client-vpn/</link>
		
		<dc:creator><![CDATA[Artem Lovan]]></dc:creator>
		<pubDate>Tue, 20 Jul 2021 17:48:19 +0000</pubDate>
				<category><![CDATA[Advanced (300)]]></category>
		<category><![CDATA[Amazon VPC]]></category>
		<category><![CDATA[AWS Client VPN]]></category>
		<category><![CDATA[AWS Identity and Access Management (IAM)]]></category>
		<category><![CDATA[AWS Lambda]]></category>
		<category><![CDATA[AWS Organizations]]></category>
		<category><![CDATA[Geo-restriction]]></category>
		<category><![CDATA[SCPs]]></category>
		<category><![CDATA[Security Blog]]></category>
		<category><![CDATA[Security, Identity & Compliance]]></category>
		<category><![CDATA[service control policies]]></category>
		<category><![CDATA[VPC]]></category>
		<category><![CDATA[vpn]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=c87af14d2ea50b847700e4ba0c27440b</guid>

					<description><![CDATA[You can improve your organization’s security posture by enforcing access to Amazon Web Services (AWS) resources based on IP address and geolocation. For example, users in your organization might bring their own devices, which might require additional security authorization checks and posture assessment in order to comply with corporate security requirements. Enforcing access to AWS […]]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Building fine-grained authorization using Amazon Cognito, API Gateway, and IAM</title>
		<link>https://noise.getoto.net/2021/05/21/building-fine-grained-authorization-using-amazon-cognito-api-gateway-and-iam/</link>
		
		<dc:creator><![CDATA[Artem Lovan]]></dc:creator>
		<pubDate>Fri, 21 May 2021 19:22:59 +0000</pubDate>
				<category><![CDATA[Advanced (300)]]></category>
		<category><![CDATA[Amazon API Gateway]]></category>
		<category><![CDATA[Amazon Cognito]]></category>
		<category><![CDATA[Amazon DynamoDB]]></category>
		<category><![CDATA[authorization]]></category>
		<category><![CDATA[AWS IAM]]></category>
		<category><![CDATA[AWS Identity and Access Management (IAM)]]></category>
		<category><![CDATA[custom authorizer]]></category>
		<category><![CDATA[JWT]]></category>
		<category><![CDATA[Oauth]]></category>
		<category><![CDATA[RBAC]]></category>
		<category><![CDATA[SAML]]></category>
		<category><![CDATA[Security Blog]]></category>
		<category><![CDATA[Security, Identity & Compliance]]></category>
		<category><![CDATA[Token]]></category>
		<category><![CDATA[апи]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=bca00f935848a7b631a841ad8138449b</guid>

					<description><![CDATA[June 5, 2021: We’ve updated Figure 1: User request flow. Authorizing functionality of an application based on group membership is a best practice. If you’re building APIs with Amazon API Gateway and you need fine-grained access control for your users, you can use Amazon Cognito. Amazon Cognito allows you to use groups to create a […]]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/

Object Caching 35/115 objects using Memcached
Page Caching using Disk: Enhanced 
Lazy Loading (feed)
Database Caching using Memcached

Served from: noise.getoto.net @ 2026-02-15 15:52:50 by W3 Total Cache
-->