Payment Successful!

Provide your AWS credentials to start the analysis

Verifying payment...

Payment Confirmed

Your payment has been successfully processed

Provide AWS Credentials

We need read-only access to your AWS account to analyze your costs and generate your personalized optimization playbook.

Security Assurance

✓

Read-Only Access

We don't make ANY changes to your AWS account

✓

Encrypted Transit

Credentials encrypted during transmission

✓

Deleted After Use

Credentials permanently deleted after report generation

Video Tutorial: How to Create AWS Credentials

Quick Setup Guide (2-3 minutes)

1

Go to AWS IAM Console

Open AWS IAM Users in a new tab
2

Create a New User

Click "Create user", name it botix-cost-analyzer, click Next
3

Attach Custom Policy

Click "Attach policies directly", then "Create policy", paste the JSON policy below, then complete user creation
4

Create Access Key

Open the user, go to "Security credentials" tab, click "Create access key", select "Third-party service"
5

Copy Credentials

Copy the Access Key ID and Secret Access Key, paste them below

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "ce:GetCostAndUsage",
        "ec2:DescribeInstances",
        "ec2:DescribeVolumes",
        "ec2:DescribeVpcs",
        "ec2:DescribeNatGateways",
        "ec2:DescribeAddresses",
        "ec2:DescribeVpcEndpoints",
        "ec2:DescribeRegions",
        "rds:DescribeDBInstances",
        "rds:DescribeDBClusters",
        "dynamodb:ListTables",
        "dynamodb:DescribeTable",
        "dynamodb:DescribeTimeToLive",
        "elasticache:DescribeCacheClusters",
        "elasticache:DescribeReplicationGroups",
        "es:ListDomainNames",
        "es:DescribeDomain",
        "s3:ListAllMyBuckets",
        "s3:GetLifecycleConfiguration",
        "s3:GetBucketVersioning",
        "s3:GetIntelligentTieringConfiguration",
        "s3:GetBucketTagging",
        "ecs:ListClusters",
        "ecs:DescribeClusters",
        "ecs:ListServices",
        "ecs:DescribeServices",
        "ecs:ListTagsForResource",
        "eks:ListClusters",
        "eks:DescribeCluster",
        "eks:ListTagsForResource",
        "lambda:ListFunctions",
        "lambda:ListTags",
        "logs:DescribeLogGroups",
        "cloudwatch:GetMetricData",
        "autoscaling:DescribeAutoScalingGroups",
        "elasticloadbalancing:DescribeLoadBalancers",
        "elasticloadbalancing:DescribeTags",
        "redshift:DescribeClusters",
        "kinesis:ListStreams",
        "kinesis:DescribeStreamSummary",
        "elasticfilesystem:DescribeFileSystems",
        "sts:GetCallerIdentity",
        "iam:ListAccountAliases"
      ],
      "Resource": "*"
    }
  ]
}

This read-only policy allows us to analyze EC2, RDS, S3, Lambda, ECS, EKS, CloudWatch, Cost Explorer, and other AWS services. We cannot modify any resources.

AWS Access Key ID

20 characters starting with AKIA

AWS Secret Access Key

40 character secret key

Primary AWS Region

Frequently Asked Questions

Why do you need AWS credentials?

We need read-only access to analyze your actual AWS resources, usage patterns, and configurations. This allows us to provide specific, actionable optimization recommendations tailored to your infrastructure.

What happens to my credentials after analysis?

Your credentials are encrypted during transit, used only for the analysis (typically 2-5 minutes), and then permanently deleted from our systems. We never store credentials after report generation.

What permissions are required?

We only require read-only (Describe/List/Get) permissions. The policy includes access to Cost Explorer, EC2, RDS, S3, Lambda, ECS, EKS, CloudWatch, and other services for comprehensive analysis. We cannot modify, delete, or create any resources.

How long does the analysis take?

The analysis typically takes 2-5 minutes depending on the size of your AWS account. You'll receive an email with a link to your report once it's complete.

Is my data safe?

Yes. Credentials are securely encrypted during transit. We only collect resource metadata and cost data needed for analysis. We don't access your application data, databases, or files. All analysis is performed automatically without human access to your credentials.

Can I delete the IAM user after analysis?

Yes! After receiving your report, we recommend deleting the IAM user you created for this analysis. You can always create a new one if you want to run another analysis in the future.