<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SSO Elevator on FivexL. Cloud Engineering Specialists</title><link>/tags/sso-elevator/</link><description>Recent content in SSO Elevator on FivexL. Cloud Engineering Specialists</description><generator>Hugo</generator><language>en-US</language><managingEditor>info@fivexl.io (FivexL)</managingEditor><webMaster>info@fivexl.io (FivexL)</webMaster><lastBuildDate>Mon, 04 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="/tags/sso-elevator/index.xml" rel="self" type="application/rss+xml"/><item><title>Can You Prove Who Accessed Your Data?</title><link>/blog/just-in-time-access-aws/</link><pubDate>Mon, 04 May 2026 00:00:00 +0000</pubDate><author>info@fivexl.io (FivexL)</author><guid>/blog/just-in-time-access-aws/</guid><description>&lt;p&gt;You have logs. You do not have proof.&lt;/p&gt;
&lt;p&gt;That is the gap most startups in regulated industries like healthcare or fintech discover during their first HIPAA or SOC 2 audit. The IAM policies are there. The roles are configured. Permissions are restricted. But when an auditor asks &amp;ldquo;who had access to this system on March 12th, and what did they do?&amp;rdquo; the answer involves digging through months of logs trying to reconstruct a timeline that was never recorded in the first place.&lt;/p&gt;
&lt;p&gt;A failed audit does not just cost time. It costs the partnership or enterprise contract that required it.&lt;/p&gt;
&lt;p&gt;This is the problem just-in-time access solves - and it is simpler than it sounds.&lt;/p&gt;</description></item><item><title>Bridging the Gap: Automating Group Assignments in AWS IAM Identity Center with SSO Elevator</title><link>/blog/sso-elevator-group-assignment/</link><pubDate>Thu, 18 Dec 2025 00:00:00 +0000</pubDate><author>info@fivexl.io (FivexL)</author><guid>/blog/sso-elevator-group-assignment/</guid><description>Google Workspace SCIM provisioning to AWS IAM Identity Center does not sync groups - a frustrating limitation. SSO Elevator now offers a Terraform-native solution that automatically assigns users to groups based on their attributes, eliminating the need for external tools like ssosync.</description></item><item><title>Building Resilience into SSO Elevator 3.1.0: Lessons from an AWS Outage</title><link>/blog/sso-elevator-3-1-0-resilience/</link><pubDate>Tue, 28 Oct 2025 00:00:00 +0000</pubDate><author>info@fivexl.io (FivexL)</author><guid>/blog/sso-elevator-3-1-0-resilience/</guid><description>How a real AWS outage revealed hidden dependencies in SSO Elevator and led to version 3.1.0 with improved resilience through intelligent S3 caching. A practical guide to engineering for failure.</description></item><item><title>Introducing the Open-Source Terraform AWS SSO Elevator Module with Slack Integration</title><link>/blog/sso-elevator/</link><pubDate>Fri, 02 Jun 2023 00:00:00 +0000</pubDate><author>info@fivexl.io (FivexL)</author><guid>/blog/sso-elevator/</guid><description>Open-source Terraform AWS SSO Elevator tool allows requesting and granting temporary elevated access for AWS SSO through a Slack request/approval workflow.</description></item></channel></rss>