How rapticore/aws-onboarding works
Project type and purpose
• This is an infrastructure-as-code repository containing AWS CloudFormation templates (JSON/YAML) for onboarding AWS accounts into the Rapticore ecosystem.
• Its goal is to deploy IAM roles (cross-account trust), VPCs, EC2 instances, and supporting resources in either a “standard” or “freemium” configuration.
• There is also a small Kubernetes RBAC manifest and an Azure identity-pool setup via an AWS Lambda.
File structure
Top-level files:
• RapticoreCrossAccountStack.json/.yaml – the main cross-account IAM role template
• cloudAccountSample.csv – example bulk upload format
• freemium/… – CFN stacks for a cost-limited (“freemium”) environment
• standard/… – CFN stacks and scripts for the “standard” environment, including VPC, EC2, and an Azure-identity-pool Lambda
• kubernetes/viewer-role-binding.yml – Kubernetes RBAC for a viewer role in a cluster
Patterns:
• Separate directories per offering (“freemium” vs. “standard”)
• Templates for core IAM cross-account roles, VPC setup, EC2 provisioning
• A shell script + Lambda backup artifacts under standard/setup-azure-identity-pool-lambda
README for additional insights
• Describes two deployment methods (Console vs. AWS CLI) for the RapticoreCrossAccountStack
• Parameters required: RapticoreAccountId, RapticoreTenantId
• The end result is an IAM role ARN to be consumed by the Rapticore portal or CSV bulk onboarding
Detail
• Parameters being passed (RapticoreAccountId, RapticoreTenantId)
• Optional vs. mandatory components