<?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>Janelle Hopper &#8211; Noise</title>
	<atom:link href="https://noise.getoto.net/author/janelle-hopper/feed/" rel="self" type="application/rss+xml" />
	<link>https://noise.getoto.net</link>
	<description>The collective thoughts of the interwebz</description>
	<lastBuildDate>Tue, 28 Jun 2022 16:57:32 +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>TLS 1.2 to become the minimum TLS protocol level for all AWS API endpoints</title>
		<link>https://noise.getoto.net/2022/06/28/tls-1-2-to-become-the-minimum-tls-protocol-level-for-all-aws-api-endpoints/</link>
		
		<dc:creator><![CDATA[Janelle Hopper]]></dc:creator>
		<pubDate>Tue, 28 Jun 2022 16:57:32 +0000</pubDate>
				<category><![CDATA[announcements]]></category>
		<category><![CDATA[AWS CloudTrail]]></category>
		<category><![CDATA[AWS Cloudwatch]]></category>
		<category><![CDATA[FedRAMP]]></category>
		<category><![CDATA[Foundational (100)]]></category>
		<category><![CDATA[Security Blog]]></category>
		<category><![CDATA[Security, Identity & Compliance]]></category>
		<category><![CDATA[TLS]]></category>
		<category><![CDATA[Transport Layer Security]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=593d198b6bb7e20a6e32d9837b1871d8</guid>

					<description><![CDATA[At Amazon Web Services (AWS), we continuously innovate to deliver you a cloud computing environment that works to help meet the requirements of the most security-sensitive organizations. To respond to evolving technology and regulatory standards for Transport Layer Security (TLS), we will be updating the TLS configuration for all AWS service API endpoints to a […]]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>TLS 1.2 will be required for all AWS FIPS endpoints beginning March 31, 2021</title>
		<link>https://noise.getoto.net/2021/03/01/tls-1-2-will-be-required-for-all-aws-fips-endpoints-beginning-march-31-2021/</link>
		
		<dc:creator><![CDATA[Janelle Hopper]]></dc:creator>
		<pubDate>Mon, 01 Mar 2021 18:04:09 +0000</pubDate>
				<category><![CDATA[announcements]]></category>
		<category><![CDATA[AWS service FIPS endpoints]]></category>
		<category><![CDATA[Federal Information Processing Standard]]></category>
		<category><![CDATA[FedRAMP]]></category>
		<category><![CDATA[FIPS]]></category>
		<category><![CDATA[FIPS 140-2]]></category>
		<category><![CDATA[FIPS endpoints]]></category>
		<category><![CDATA[Intermediate (200)]]></category>
		<category><![CDATA[nist]]></category>
		<category><![CDATA[Security Blog]]></category>
		<category><![CDATA[Security, Identity & Compliance]]></category>
		<category><![CDATA[TLS]]></category>
		<category><![CDATA[Transport Layer Security]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=b7595d3a117aaaece8a3199844baeba4</guid>

					<description><![CDATA[To help you meet your compliance needs, we’re updating all AWS Federal Information Processing Standard (FIPS) endpoints to a minimum of Transport Layer Security (TLS) 1.2. We have already updated over 40 services to require TLS 1.2, removing support for TLS 1.0 and TLS 1.1. Beginning March 31, 2021, if your client application cannot support […]]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Over 40 services require TLS 1.2 minimum for AWS FIPS endpoints</title>
		<link>https://noise.getoto.net/2021/02/02/over-40-services-require-tls-1-2-minimum-for-aws-fips-endpoints/</link>
		
		<dc:creator><![CDATA[Janelle Hopper]]></dc:creator>
		<pubDate>Tue, 02 Feb 2021 17:47:30 +0000</pubDate>
				<category><![CDATA[announcements]]></category>
		<category><![CDATA[AWS service FIPS endpoints]]></category>
		<category><![CDATA[Federal Information Processing Standard]]></category>
		<category><![CDATA[FedRAMP]]></category>
		<category><![CDATA[FIPS]]></category>
		<category><![CDATA[FIPS 140-2]]></category>
		<category><![CDATA[FIPS endpoints]]></category>
		<category><![CDATA[Foundational (100)]]></category>
		<category><![CDATA[nist]]></category>
		<category><![CDATA[Security Blog]]></category>
		<category><![CDATA[Security, Identity & Compliance]]></category>
		<category><![CDATA[TLS]]></category>
		<category><![CDATA[Transport Layer Security]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=a84c315c500d025d43c7cb43bb4f8910</guid>

					<description><![CDATA[In a March 2020 blog post, we told you about work Amazon Web Services (AWS) was undertaking to update all of our AWS Federal Information Processing Standard (FIPS) endpoints to a minimum of Transport Layer Security (TLS) 1.2 across all AWS Regions. Today, we’re happy to announce that over 40 services have been updated and […]]]></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 28/96 objects using Memcached
Page Caching using Disk: Enhanced 
Lazy Loading (feed)
Database Caching using Memcached

Served from: noise.getoto.net @ 2026-02-06 22:45:24 by W3 Total Cache
-->