AWS and ºÚÁϺ£½Ç91Èë¿Ú have partnered to offer a VPN alternative for securely accessing company applications over the web using ºÚÁϺ£½Ç91Èë¿Ú Goâ„¢, ºÚÁϺ£½Ç91Èë¿Ú SSO (SAML or OIDC) and . With this collaboration, ºÚÁϺ£½Ç91Èë¿Ú can authenticate and authorize devices and identities in one console and provide access control for AWS Verified Access for managed devices. See our blog for more information about our partnership.
Prerequisites
- ºÚÁϺ£½Ç91Èë¿Ú Admin account
- Your ºÚÁϺ£½Ç91Èë¿Ú Org ID
- ºÚÁϺ£½Ç91Èë¿Ú SSO Package or higher or SSO add-on feature.
- ºÚÁϺ£½Ç91Èë¿Ú-managed users on ºÚÁϺ£½Ç91Èë¿Ú-managed devices
- AWS Admin account (AWS root user)
- AWS organization
There are three steps:
Installing ºÚÁϺ£½Ç91Èë¿Ú Go
Customers already using ºÚÁϺ£½Ç91Èë¿Ú Go will have access to AVA with no additional ºÚÁϺ£½Ç91Èë¿Ú configuration.
The ºÚÁϺ£½Ç91Èë¿Ú Go Chrome extension provides secure passwordless authentication to ºÚÁϺ£½Ç91Èë¿Ú protected web resources on managed devices (Mac or Windows). The extension can be installed via ºÚÁϺ£½Ç91Èë¿Ú Policy, Google’s (CBCM), or manual installation.
See Get Started: ºÚÁϺ£½Ç91Èë¿Ú Go and Use ºÚÁϺ£½Ç91Èë¿Ú Go.
Configuring an AWS SSO Connector
If an AWS IAM Center SSO connector already exists, you can optionally create a second OIDC connector or go to the next section, Setup AVA.
To configure AWS IAM Identity Center SSO
See Integrate with AWS IAM Identity Center.
To configure Custom AWS OIDC
See SSO with OIDC.
For additional information about the AWS OIDC configuration, please view the following AWS documentation:
Setting up AVA
AVA provides secure access to company applications over the internet without using a VPN. Once you have set up ºÚÁϺ£½Ç91Èë¿Ú Go and the AWS SSO Connector, the final step is configuring Verified Access inside AWS. To proceed, please view the following AWS documentation:
Your ºÚÁϺ£½Ç91Èë¿Ú Org ID needs to be put in the Tenant ID of AVA.