Connect your customers' AWS accounts to your product without ever asking them to hand over access keys. Askel uses a cross-account IAM role so you read only what you need, and customers can revoke access in one click.
Askel reads instance types, running state, storage volumes, bucket names, and database engine versions. The default role carries SecurityAudit only, so nothing in the customer's account can be changed unless they explicitly grant write permissions.
Pull the full list of IAM principals, their attached policies, MFA status, and last-used dates. Useful for access-review workflows and security-posture checks during onboarding.
Fetch recent management events from CloudTrail to surface what changed in a customer's account and when. Pair this with your own product's activity log for a complete picture.
Query Config rule results to see which resources are compliant and which are not. Lets your product surface compliance drift without customers needing to file support tickets.
One IAM role covers all regions. Your product can query us-east-1, eu-west-1, or any other region the customer operates in without additional setup steps.
Customers running an AWS Organization can deploy the CloudFormation stack in each member account. Askel tracks each account separately so your product can show a consolidated view across the org.
You sell a cloud security posture product. A new customer, Ridgeline Analytics, runs their data platform on AWS across three accounts: production, staging, and a shared-services account. Your product needs to read their EC2 instances, S3 bucket policies, IAM roles, and Config rule results on day one so their security team can see their baseline posture before the kickoff call.
Ridgeline's AWS admin logs into the production account and clicks the one-click stack link from your product's onboarding wizard. The stack creates a cross-account IAM role named AskelReadRole with a SecurityAudit policy attached and Askel's account ID plus a unique externalId in the trust policy. The whole process takes about three minutes.
The admin copies the role ARN from the CloudFormation outputs tab and pastes it into the connection form in your product. Askel immediately calls AssumeRole to verify the role is reachable before saving the connection.
The admin deploys the same stack template in the staging and shared-services accounts. Each stack produces a separate role ARN. They add both to Askel as additional connections under the same customer record.
Askel fans out read calls across all three accounts: EC2 DescribeInstances, S3 GetBucketPolicy, IAM GetAccountAuthorizationDetails, and Config DescribeComplianceByConfigRule. Your product receives structured data for each resource type within a few minutes.
Your customer-success team opens the posture dashboard and sees Ridgeline's baseline: 47 EC2 instances, 12 S3 buckets with public-access settings flagged, 6 Config rules failing, and 3 IAM users without MFA. The kickoff call now starts from a concrete list of findings rather than a blank slate.
Customer's AWS admin deploys a one-click CloudFormation stack that creates a cross-account IAM role with a least-privilege SecurityAudit policy. Askel assumes the role with an externalId on every request; no long-lived AWS credentials are ever stored. Customers can swap the default policy for a custom one when they need write access.
© 2025 Askel.ai. All rights reserved.