📦AWS

Installing P0 IAM management on AWS takes about 10 minutes.

Before you begin

• Choose at least one account on which to install P0.

• Make sure you have the ability to create roles, add trust relationships, and create and assign role polices. You can do this if you have the IAMFullAccess managed policy attached to your user.

Setting up AWS IAM management

For fine-grained Kubernetes access in EKS use the P0 Kubernetes integration.

1. Navigate to "Integrations" on p0.app, then select "AWS". Choose the "IAM management" component:

1. Click the "Add account" button to begin the installation

1. Enter an AWS numeric account ID, then click "Next".

1. The next page will display commands you can run using the AWS CLI to provision P0. You can also run these commands using AWS Cloud Shell.

1. Copy and run these commands or use the Terraform configuration to deploy the changes. Click "Next" to verify the installation. If verification is successful you will be taken to the integration configuration page.

Configuring P0 with AWS

On the configuration page, you define how users are provisioned in AWS:

As AWS IAM users

If users are defined in the account's IAM service, choose "As AWS IAM users".

If the user's names equal their email addresses choose "User name is user email".

If users are defined in the account's IAM service, but their user names do not equal their email, you'll need to add a tag to each user you want to allow access via P0. For example, with a tag named "Email":

Via AWS Identity Center

If users are provisioned via Identity Center (for example, if you provision via SSO), choose "Via AWS Identity Center".

A few requirements apply:

• P0 must be installed on the account where the Identity Center instance resides

• Users must be provisioned with user names equal to user email addresses

To finish the configuration select the "Parent AWS account" in which the Identity Center instance resides and click "Next".

Via a federated identity provider

If you use an IAM identity provider to sign in users to your AWS account choose "Via a federated identity provider". This is a legacy sign in method. AWS recommends using Identity Center.

Currently only Okta SAML federation is supported via an AWS Account Federation.

An installed Okta directory integration is required. Your AWS Account Federation Okta app must be in the same Okta organization as the one installed as the directory integration.

Saving the configuration by clicking "Next" automatically applies the following changes to your AWS Account Federation app:

• Adds a custom attribute managedByP0 to your Okta app's user profile. This allows P0 to clean up dynamically assigned users from your AWS SSO Okta app.

• Enables the Join all roles flag. This allows users to assume AWS roles assigned by P0 directly to their Okta user.

Setting up AWS resource inventory

Installing P0 resource inventory on AWS takes about 10 minutes.

The resource inventory component extends the IAM management integration and allows requesting fine-grained resource-level access in AWS.

An installed AWS IAM management integration is required

1. Navigate to "Integrations" on p0.app, then select "AWS". Choose the "Resource inventory" component:

1. Click "Add account"

1. Choose one of the AWS accounts already installed for IAM management:

1. Run the AWS CLI commands to configure Resource Explorer

1. Click "Next" to validate your setup. You will land on the resource inventory configuration page. Clicking "Next" again takes you back to the Resource inventory overview page.

And that's it. You're all set to start granting just-in-time, least-privileged access to AWS with P0.