Apono Connector for AWS
How to install a Connector on an AWS account to integrate an AWS Account or Organization with Apono
Overview
To integrate with AWS and start managing JIT access to AWS cloud resources, you must first install a connector in your AWS environment.
The connector should match the level of access management you want to achieve with Apono: on a single account or on the entire organization.
To manage access to a single AWS account, install a connector on that account. Follow this guide.
To manage access to all the accounts in the AWS organization:
Install a connector on the management account. Follow this guide. OR
Install a connector in any account with ECS or EKS and give it assumable permissions to the management account. Follow this guide.
What's a connector? What makes it so secure?
The Apono Connector is an on-prem connection that can be used to connect resources to Apono and separate the Apono web app from the environment for maximal security.
Read more about the recommended AWS Installation Architecture.
First, decide if you want to integrate Apono with a specific AWS Account or with the entire Organization (containing multiple Accounts).
Follow the guides below depending on your selection.
AWS Account connector
Prerequisites
Administrator permissions to the AWS account you want to connect.
VPC with outbound connectivity
1. In Apono
Login to the Apono platform
Go to the Apono Integrations page
From the Catalog, pick AWS
Pick Account

Install a new connector in AWS. Read more here.
Choose the desired deployment method

2. In CloudFormation
Choose Cloudformation
Click "Open Cloud Formation"
Sign in to your AWS user and click Next

Within the AWS create stack page, scroll down
Make sure you pick at least one Subnet and one VPC from the dropdown lists
Tick the acknowledge box and then select Create Stack
Apono integrates with AWS natively, using AWS CloudFormation as a standard mechanism to deploy all required configurations including a Cross Account Role with Read permission, a SNS notification message, and the Apono Connector that runs using an AWS ECS on Fargate.
AWS Organization connector on the Management account
Prerequisites
Administrator permissions to the AWS management account in the Organization.
VPC with outbound connectivity.
1. In Apono
Login to the Apono platform
Go to the Apono Integrations page
From the Catalog, pick AWS
Pick Organization

Choose Cloudformation

2. In CloudFormation
Click "Open Cloud Formation"
Sign in to your AWS user and click Next

The new stack should be installed in the management account (which manages the organization's Identity Center)
Within the AWS create stack page, scroll down
Make sure you pick at least one Subnet and one VPC from the dropdown lists
Tick the acknowledge box and then select Create Stack
Apono integrates with AWS natively, using AWS CloudFormation as a standard mechanism to deploy all required configurations including a Cross Account Role with Read permission, a SNS notification message, and the Apono Connector that runs using an AWS ECS on Fargate.

Verify that "trusted access" is activated for your organization. Read more here.
Connector with IAM role permissions for AWS Organization management
You can install a connector with assumable permissions to the AWS Management account using either AWS Elastic Container Service (ECS) or Elastic Kubernetes Service (EKS) in CloudFormation.
Once installed, the connector syncs data from cloud applications and enables you to manage access permissions through access flows within Amazon ECS or EKS.
Prerequisites
AdminstratorAccess Policy
AWS role with AdministratorAccess policy providing full access to AWS services and resources
Full AWS access is not granted to Apono.
OrganizationID
Unique identifier of the AWS Organization that will be connected via the integration (ex. o-k012345a67)
Follow these steps to find your OrganizationID:
In your AWS console settings, click Organization. The AWS accounts page appears.
In the left navigation, click Settings. The Settings page appears.
Under Organization details, copy your OrganizationID.
OrganizationUnitID
Root ID for the AWS Organization Unit that will be connected via the integration (ex. r-1a2b)
Follow these steps to obtain your OrganizationUnitID:
In your IAM Identity Center, expand Multi-account permissions.
Click AWS accounts. The AWS accounts page appears.
In the Organizational structure section, copy the ID from the Root folder. This is the parent organizational unit for all accounts in your organization.
VPC
Virtual Private Cloud (VPC) with outbound connectivity
Subnet
One or more Subnet IDs within the selected VPC where the connector resources will run
Permission
Full access (Manage IAM) permissions to enable the connector to create and manage the required IAM resources during deployment
Install the connector

Follow these steps to enable the connector to manage the entire AWS Organization:
On the Connectors page, click Install Connector. The Install Connector page appears.
Under Select connector installation strategy, click Cloud installation > AWS. The permission options appear.
Click No, Just Install the Connector. The installation methods appear.
Do not select Install and Connect AWS Account. This option creates IAM roles in the member account that will conflict with the CloudFormation roles deployed in the Management account, causing the installation to fail.
Click the CloudFormation (ECS) or CloudFormation (EKS) installation method.
You can also install the connector using Terraform.
Finish installing the connector in CloudFormation for your AWS Account.
Once the connector is installed, copy the following values from CloudFormation.
AponoConnectorRoleArn
On the Outputs tab, copy the Value for the AponoConnectorRoleArn.
AponoConnectorId
On the Parameters tab, copy the Value for the AponoConnectorId key.
Open CloudFormation with your Management account. The Quick create stack page appears.
Under Parameters, enter values for the following fields:
AponoConnectorId: Value copied in step 6.
ConnectorRoleArn: Value copied in step 6.
OrganizationId: Organization ID copied during the prerequisites.
OrganizationUnitId: Root ID copied during the prerequisites.
From the Permissions dropdown menu, select Full-Access (Manage IAM).
Under Capabilities, select I acknowledge that AWS CloudFormation might create IAM resources with custom names.
Click Create stack.
(Optional) On the Outputs tab, copy the Value for the ManagementAccountRoleArnOutput.
When integrating an AWS Organization, you can paste the ManagementAccountRoleArnOutput value in the Integration Config settings to use the connector.
On the Connectors page, verify that the connector has been deployed.
(Optional) Follow the steps to integrate an AWS organization.
Last updated
Was this helpful?
