Secrets Management Articles
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Scheduled Maintenance: November 14–15 (starting Nov. 14 at 12:00 AM PST)
LIVEcommunity will temporarily operate in read-only mode as we prepare to welcome Idira!
Public content will remain accessible, but log-ins, posting and community interactions will be paused during this period. Thank you for your patience!
This guide provides a comprehensive, step-by-step explanation of onboarding an AWS Organization (a collection of multiple AWS accounts managed together) into Idira Connect Cloud Environments (CCE). It includes an in-depth overview of AWS CloudFormation—what it is and what it does in this process—along with prerequisites, detailed procedures, security considerations, troubleshooting, and a full breakdown of the template. The process enables secure integration of your AWS environment with Idira services, allowing centralized management of privileged access, secrets, and entitlements without sharing permanent credentials.   What is AWS CloudFormation and What Does It Do?   AWS CloudFormation is a powerful Infrastructure as Code (IaC) service provided by Amazon Web Services. It allows you to define and provision AWS resources in a predictable, automated, and repeatable way using template files (written in JSON or YAML).   Think of it like a blueprint: You write (or download) a template that describes exactly what AWS resources should be created—such as IAM roles, policies, notification topics, or StackSets. What it does:   Automates deployment: Instead of manually creating resources in the AWS console, CloudFormation reads the template and builds everything for you. Manages stacks: A "stack" is the set of resources created from one template. CloudFormation can create, update, or delete entire stacks with one command. Supports multi-account deployments: Using StackSets, it can deploy the same resources across multiple AWS accounts and regions simultaneously—critical for AWS Organizations. Ensures consistency and safety: Templates include rules for validation, rollback on failure, and change management. In the context of Idira CCE onboarding:   Idira generates a customized CloudFormation template (a JSON file) based on your AWS Organization details and selected services. This template creates secure cross-account IAM roles (temporary access only), notification hooks (using SNS), and service-specific components (via StackSets). It establishes trust between your AWS environment and Idira using only temporary credentials from AWS STS — no permanent keys or static access ever shared. No manual resource creation is needed; everything is automated and auditable. Steps Important Prerequisites   Before starting:   Enable Trusted Access in AWS Organizations (done once in the management account): Log into the AWS management account console. Go to AWS Organizations > Services tab. Enable trusted access for "Identity and Access Management" and "CloudFormation". For IAM and CloudFormation (required for cross-account role creation and StackSets). Steps: This allows safe, organization-wide deployments.   Permissions Needed: In CyberArk: User with Cloud Onboarding role (often DpaAdmin or Secrets Hub Admin). In AWS: Admin access in the management account. Step-by-Step: Onboarding an AWS Organization in Idira CCE   1. Navigate in Idira Console Log into your Idira tenant. Go to: Administration > My environment > Cloud connectivity > Connect cloud environments > AWS environment. 2. Add the AWS Organization   Click Add > Add AWS Organization. Fill in Organization details:   Organization ID (starts with "o-"): Found in AWS Organizations dashboard. Root ID: Usually the same as Organization ID. Management Account ID: 12-digit ID of your primary account (top-right in AWS console > Account). Organization name (optional): Friendly name. Deployment region: Usually us-east-1 (matches your Idira tenant region).   Click Next. 3. Select and Configure Services   Choose services to enable (e.g., SIA, Secrets Hub). Review configurations (pre-filled where possible). Click Download CFT (CloudFormation Template) to get the JSON file. 4. Deploy the CloudFormation Template in AWS   Run this in the management account and correct region:   Open AWS Console > Search for CloudFormation. Create stack > With new resources. Upload the downloaded JSON template. Name the stack (e.g., "CyberArk-CCE-Onboarding"). Review parameters (mostly pre-filled by CyberArk). On review page: Acknowledge IAM resource creation. Create stack. What Happens During Deployment (5–20 minutes):   Validation rules check account ID and region. Creates cross-account IAM role for Idira (temporary access only, assumable via STS). Sets up SNS hooks for status notifications (start, scan, complete). Deploys service-specific resources via StackSets across all accounts. Sends verification messages back to CyberArk. Success Indicators:   Stack status: CREATE_COMPLETE in AWS CloudFormation. In CyberArk: Return to Administration > My environment > Cloud connectivity > Connect cloud environments > AWS environment. This opens the AWS environment page (the main dashboard for AWS connections).   Your connected AWS Organization appears as a row or card. Next to each service enabled (e.g., SIA, Secrets Hub), you'll see green checkmarks (or success icons) confirming successful deployment. The row also shows the number of accounts connected (total member accounts onboarded and synced). Overall status is "Active" or fully connected. 5. Troubleshooting Failures   Check CloudFormation Events tab for errors (e.g., trusted access not enabled, wrong region). Delete failed stack and retry after fixing. Common issues: Missing trusted access, incorrect IDs, permissions. In CyberArk, partial failures may show warnings like "Needs attention" instead of green checkmarks. Main Parts of the Template (Simple Breakdown) Full List of Main Resources from the JSON Template   Here is the complete list of the primary logical resource names as they appear in the "Resources" section of the generated CloudFormation JSON template (this template as shown is used for deploying both SIA and Secrets Hub in CCE):   CyberArkOnboardingCrossAccountRole OrganizationDeploymentStartedHook OrganizationScanHook OrganizationDeploymentCompleteHook dpaStack dpaStackSet secretshubStack secretshubStackSet Note on order in the JSON file: The actual order in which these resources are listed in the JSON template does not matter. CloudFormation does not create resources in the order they appear in the file. Instead, it automatically determines the correct creation order based on explicit dependencies (like the DependsOn attribute on the Complete hook) and implicit dependencies (e.g., a StackSet needing the cross-account role to exist first so Idira can assume it to deploy across accounts). This makes the template safer and less error-prone — you don’t have to manually manage the sequence. The CloudFormation template (a JSON file) has two big sections: Resources These are the actual things that get created in your AWS accounts. They are grouped below into logical categories, with a short explanation of what each group means, followed by the resources and their simple explanations: Core Security Component - Role Creation   What this group means: This is the single most important foundation for all security in the integration — the resource that creates the temporary IAM role allowing Idira to securely access your AWS environment without any permanent or static credentials. CyberArkOnboardingCrossAccountRole – The special IAM permission role (temporary by design) that allows Idira to safely access your AWS accounts using only short-lived credentials (no permanent keys shared). This resource is the one that creates the cross-account IAM role in your management account. Notification Hooks (Progress Messengers)   What does this group mean: These are automated messages sent back to Idira at key moments during deployment so your console always knows exactly what stage the onboarding is at. Each hook is a custom resource in CloudFormation. It uses a ServiceToken that points to an SNS topic owned by CyberArk. Simple example of a ServiceToken (one of the actual values from a generated template): "ServiceToken": "arn:aws:sns:us-east-1:871697792279:add-organization-org-complete-us-east-1" Why each hook has a ServiceToken: When CloudFormation creates the hook, it automatically sends a message to this SNS topic. Idira is listening to the topic and instantly receives the update — no direct connection or credentials needed from your side. What "Idira is listening to the topic" means (simple explanation) The SNS topic lives in CyberArk's own AWS account. When your deployment sends a message to it, Idira has a secure subscriber (like a small service) attached to the topic on their side. This subscriber receives the message almost instantly and relays it back to your specific Idira tenant (your company's private space in CyberArk). Idira then processes the message and updates your tenant's CCE console accordingly:   Successes: Shows progress, verifies resources, and displays green checkmarks when everything is complete. Failures: Detects issues (e.g., from errors in the payload or missing resources) and shows warnings or "failed deployment" status in your console. It's a safe, one-way notification: your account only sends, Idira only receives and relays the status directly to your tenant. Actual execution order of the hooks (the logical order in which they fire during deployment):   OrganizationDeploymentStartedHook Sends an immediate “we’re starting now” message to Idira so your console shows that onboarding has begun right away. Why first: This hook is created early (usually right after the cross-account role). It fires as soon as the basic setup begins, letting your CCE console immediately show "deployment in progress" — even before the heavy lifting (StackSets across accounts) starts. OrganizationScanHook Sends a detailed list of everything that was created (like resource IDs, ARNs, versions, regions) so Idira can double-check and verify it all. Why second: This runs after the service-specific StackSets (dpaStackSet and secretshubStackSet) finish deploying across all accounts. Idira needs the full inventory of what was built to perform its safety verification before activating features. OrganizationDeploymentCompleteHook Sends the final “all done successfully” message only after everything else is fully built, triggering the green checkmarks in your Idira console. Why last: This is explicitly the final step. It has a DependsOn attribute that forces CloudFormation to wait for all other key resources (including both StackSets and the Scan hook) to complete successfully. Only then does it send the "complete" message — ensuring no false positives and that green checkmarks only appear when everything is truly ready. This order guarantees smooth progress visibility, thorough verification, and reliable final confirmation — all while keeping the process secure and automated. SIA (Secure Infrastructure Access) Components   What this group means: These resources enable the Secure Infrastructure Access (SIA) feature — the just-in-time, temporary access to your AWS servers, databases, and other resources. dpaStack – Builds the central pieces needed for SIA in the management account only. dpaStackSet – Automatically copies and deploys those SIA pieces to every member account and selected regions in your AWS Organization. Secrets Hub Components   What this group means: These resources enable the Secrets Hub feature — centralized storage, rotation, and automatic synchronization of secrets with AWS Secrets Manager across your accounts. secretshubStack – Builds the central pieces needed for Secrets Hub in the management account only. secretshubStackSet – Automatically copies and deploys those Secrets Hub pieces to every member account and selected regions in your AWS Organization. Rules Section Runs first and checks two things:   The exact AWS account number matches what is expected. The geographic region (data center location, usually us-east-1) is correct. If either is wrong, the template stops immediately with a clear error — preventing accidental setup in test accounts, wrong regions, or member accounts.
View full article
  • 79 Posts
  • 7 Subscriptions