Infinity Works is an AWS Advanced Consulting Partner with the AWS DevOps Competency and broad experience in government, finance, retail, health, and other sectors. This has the advantage of using the existing MFA used for all Azure access. By connecting to the AWS Client VPN using a browser-based authentication provided by Azure, this approach gives remote users access to Amazon VPC. In this post, I will show you how to integrate AWS Client VPN with an Azure Active Directory. This support requires integration with a SAML 2.0 provider, such as Azure Active Directory.
We had to find a solution that provided access from home but integrated into Active Directory.Īs it turned out, Amazon Web Services (AWS) had announced federated authentication support for AWS Client Virtual Private Network (VPN) in May 2020. It’s well known that IT departments prefer authentication integration into existing identity providers (IdPs) such as Azure Active Directory to reduce operational overhead and the attack surface of IT systems. When working within their offices, they used AWS site-to-site VPNs to gain this access, but more recently, the agents have needed to access these private VPNs from home. Originally, the call center agents required access to systems that were not publicly accessible on the internet, but ran within private subnets of Amazon Virtual Private Clouds (VPCs). One of our clients at Infinity Works was migrating their call center to Amazon Connect when the recent lockdowns hit. By Steven Harper, Engineering Practice Lead at Infinity Works
0 kommentar(er)
