search
Ctrlk

Connecting AWS Organizations to the managed Apono SaaS

Apono integrates seamlessly with AWS, using AWS CloudFormation to automate the deployment of all the necessary configurations:

  • Cross-account IAM role with read permissions

  • Apono Managed Connector, which runs on managed instances in Apono

Once installed, the connector syncs metadata information from cloud resources and enables you to manage access permissions through access flows within an AWS Organization.

hashtag
Prerequisites

Item
Description

AdminstratorAccess Policy

User with an AWS role with AdministratorAccessarrow-up-right policy providing full access to AWS services and resources, required for deploying an assumable role via a cloudformation stack

Full AWS access is not granted to Apono.

AWS Cloudformation Parameters from Apono

Apono will provide an ARN and ConnectorID of the connector that will need to assume the role created using the CloudFormation template

AWS OrganizationID

Root organizationID for the AWS organization that will be connected via the integration (ex. r-1a2b)

hashtag
Deploy the CloudFormation template for AWS Organization management

  1. Open this CloudFormationarrow-up-right in the AWS management account. The Create stack page appears.

  2. Under Parameters, enter values for the following fields:

    • AponoConnectorId: Value provided by Apono Services.

    • ConnectorRoleArn: Value provided by Apono Services.

    • OrganizationalUnitId: AWS organization unit ID

  3. Click Create stack.

  4. Once completed, copy the value for ManagementAccountRoleArnOutput from the output of the CloudFormation stack

hashtag
Create AWS organization Integration

  • To sync and manage access to EC2 servers, make sure you add the AmazonSSMManagedInstanceCore policy to the connector's IAM role

Follow these steps to integrate Apono with your AWS organization:

  1. On the Catalog tab, click AWS. The Connect Integrations Group page appears.

  2. Under Discovery, click Amazon Organization.

  3. Click one or more resource types to sync with Apono.

Apono automatically discovers and syncs all the instances in the environment. After syncing, you can manage access flows to these resources.

  1. Click Next. The Apono connector section expands.

  2. From the dropdown menu, select the connector with the connector ID that Apono provided in the previous steps.

  3. Click Next. The Integration Config section expands.

  4. Define the Integration Config settings.

Setting
Description

Integration Name

Unique, alphanumeric, user-friendly name used to identify this integration when constructing an access flow

Region

Region in which the organization runs

AWS SSO Region

Region for which your single sign-on is configured

SSO Portal

Single sign-on URL

This is required for Apono to generate a sign-in link for end users to use their granted access.

Management Account Role ARN

ARN (step 4) of the role to assume in the management account

Exclude Organization Unit IDs

(Optional) ID of organizational units to exclude

Example: ou-aaa1-1111, ou-bbb2-2222

Enable Audit

(Optional) Feature that allows Apono to ingest and aggregate session audit logs

  1. Click Next. The Get more with Apono section expands.

  2. Define the Get more with Apono settings.

Setting
Description

Custom Access Details

(Optional) Instructions explaining how to access this integration's resources

Upon accessing an integration, a message with these instructions will be displayed to end users in the User Portal. The message may include up to 400 characters.

To view the message as it appears to end users, click Preview.

Integration Owner

(Optional) Fallback approver if no resource owner is found

Follow these steps to define one or several integration owners:

  1. From the Attribute dropdown menu, select User or Group under the relevant identity provider (IdP) platform.

  2. From the Value dropdown menu, select one or multiple users or groups.

NOTE: When the Resource Owner is defined, an Integration Owner must be defined.

Resource Owner

(Optional) Group or role responsible for managing access approvals or rejections for the resource

Follow these steps to define one or several resource owners:

  1. Enter a Key name. This value is the name of the tag created in your cloud environment.

  2. From the Attribute dropdown menu, select an attribute under the IdP platform to which the key name is associated.

  3. Apono will use the value associated with the key (tag) to identify the resource owner. When you update the membership of the group or role in your IdP platform, this change is also reflected in Apono.

NOTE: When this setting is defined, an Integration Owner must also be defined.

  1. Click Confirm.

After connecting your AWS account to Apono, you will be redirected to the Connected tab to view your integrations. The new AWS integration will initialize once it completes its first data fetch and will be marked Active upon completion.

Now that you have completed this integration, you can create access flows that grant permission to AWS IAM resources, such as AWS Roles.

Last updated

Was this helpful?