Complete Setup Guide for InfraMorph
This comprehensive guide walks you through purchasing, setting up, and using InfraMorph with any supported cloud provider (DigitalOcean, AWS, or Azure) from start to finish.
Table of Contents
- Account Registration
- Subscription Purchase
- Cloud Provider API Setup
- Using InfraMorph
- Downloading Terraform Configuration
Account Registration
Step 1: Access InfraMorph Website
Visit inframorph.com and click on "Buy Now".
Step 2: Select Your Cloud Provider Plan
Choose your cloud provider and click on "Purchase [Provider] InfraMorph" to proceed with your preferred plan: - DigitalOcean InfraMorph - AWS InfraMorph - Azure InfraMorph
Step 3: Create Your Account
Fill out the registration form with the following information:
Company Information
- Company Name: Enter your organization's name
- Subdomain: Choose a unique subdomain for your InfraMorph account (e.g.,
yourcompany.inframorph.com
)
Personal Information
- First Name: Your first name
- Last Name: Your last name
- Username: Choose a unique username for login
- Email Address: Your business email address
- Password: Create a secure password
Step 4: Complete Registration
- Click "Create Account"
- Check "I Accept the Terms and Privacy Policy"
- Click "Continue"
Subscription Purchase
Step 5: Billing Information
- Email Confirmation: Re-enter your email address
- Marketing Consent: Optionally check the box to receive product updates via email
- Click "Continue »"
Step 6: Payment Details
Enter your payment information:
- Card Number: Your credit card number
- Name on Card: Cardholder's full name
- Expiry Date: MM/YY format (e.g., "01/26")
- Security Code: CVV code from the back of your card
Step 7: Complete Purchase
Click "Pay $19.99" to complete your subscription purchase.
You'll see a "Redirecting you to your dashboard..." message upon successful payment.
Cloud Provider API Setup
Step 8: Access Your Dashboard
- Click "Sign In" on the confirmation page
- Enter your credentials:
- Subdomain/Username: The subdomain or username you created
- Password: Your account password
- Click "Sign In"
Step 9: Configure Cloud Provider API
To connect InfraMorph to your cloud account, you'll need to create API credentials for your chosen provider:
For DigitalOcean:
- Log into your DigitalOcean Control Panel
- Navigate to API in the left sidebar
- Click "Generate New Token"
- Provide a token name (e.g., "InfraMorph Integration")
- Select Read scope (InfraMorph only needs read access for security)
- Click "Generate Token"
- Important: Copy the token immediately as it won't be shown again
For AWS:
- Log into your AWS Console
- Go to IAM → Users → Add User
- Select Programmatic access
- Attach ReadOnlyAccess policy
- Copy the Access Key ID and Secret Access Key
For Azure:
- Log into your Azure Portal
- Go to Azure Active Directory → App registrations
- Click New registration
- After creation, go to Certificates & secrets → New client secret
- Note down the Application (client) ID, Directory (tenant) ID, and client secret
- Assign Reader role to the application
Connecting to InfraMorph
- In your InfraMorph dashboard, locate the API credentials field
- Enter your cloud provider credentials (API token for DigitalOcean, Access Keys for AWS, or App credentials for Azure)
- Click "Test Connection" to verify the connection
- Click "OK" when the connection test succeeds
Using InfraMorph
Step 10: Generate Terraform Configuration
- Once your API connection is verified, click "Start [Your Provider] InfraMorph" (e.g., "Start DigitalOcean InfraMorph", "Start AWS InfraMorph", "Start Azure InfraMorph")
- InfraMorph will begin scanning your cloud infrastructure
- The process typically takes less than 2 minutes
- You'll see real-time progress updates during the scan
What InfraMorph Analyzes by Provider
DigitalOcean:
- Droplets (Virtual Machines), Load Balancers, Databases, Volumes (Block Storage), VPCs, Firewalls, Domain Records, Kubernetes Clusters, App Platform deployments
AWS:
- EC2 Instances, Load Balancers (ALB/NLB/CLB), RDS Databases, EBS Volumes, VPCs, Security Groups, Route53 Records, EKS Clusters, S3 Buckets, IAM Roles/Policies
Azure:
- Virtual Machines, Load Balancers, SQL Databases, Managed Disks, Virtual Networks, Network Security Groups, DNS Zones, AKS Clusters, Storage Accounts, Resource Groups
Downloading Terraform Configuration
Step 11: Download Your Configuration
- When the scan completes, click "Download Terraform Configuration"
- Click "Download" to save the ZIP file to your computer
Step 12: What You'll Receive
Your download will include a complete Terraform project with:
terraform-infrastructure/
├── main.tf # Main Terraform configuration
├── variables.tf # Input variables
├── outputs.tf # Output values
├── providers.tf # Provider configuration
├── versions.tf # Terraform version constraints
├── modules/ # Custom modules (if applicable)
│ ├── droplets/
│ ├── databases/
│ └── networking/
└── README.md # Setup instructions
File Descriptions
- main.tf: Contains all your infrastructure resources
- variables.tf: Configurable parameters for your setup
- outputs.tf: Important values exported after deployment
- providers.tf: Cloud provider configuration (DigitalOcean, AWS, or Azure)
- versions.tf: Terraform and provider version requirements
Next Steps
Terraform Usage
- Install Terraform: Download from terraform.io
- Initialize: Run
terraform init
in your project directory - Plan: Run
terraform plan
to preview changes - Apply: Run
terraform apply
to create infrastructure
File Availability
- Your generated files remain available in your InfraMorph dashboard for 30 days
- You can re-download them anytime during this period
- Consider storing them in version control for long-term management
Support
- Access our Support Center for additional help
- Review our FAQ for common questions
- Contact support for technical assistance
Security Notes
- InfraMorph uses read-only API access to your cloud provider account
- No infrastructure changes are made during the scanning process
- Your API credentials are encrypted and stored securely
- Generated Terraform files contain no sensitive credentials
- All cloud provider connections use industry-standard security practices
Troubleshooting
Common Issues
- API Connection Failed: Verify your credentials have read permissions for your cloud provider
- Incomplete Scan: Ensure your API credentials have access to all required resources
- Download Issues: Check your browser's download settings
- Provider-Specific Issues:
- DigitalOcean: Ensure API token has "Read" scope
- AWS: Verify IAM user has ReadOnlyAccess policy attached
- Azure: Confirm service principal has Reader role assigned
For detailed troubleshooting, see our Troubleshooting Guide.
Generated with InfraMorph - Infrastructure as Code made simple