Dollar Cost Averaging to reduce the impact of volatility on large purchases.

Automating your investments to free up your time for better things

Low Fees to keep more of your money

1. Follow along with this Youtube Video (Thanks @Rhett)
2. Gather the needed resources here.
3. Supplement the lambda functions with the ones in the repository. Check back often for updates.

Instead of creating a lambda function for each different crypto (or price/coin combination) you can create a single Event Bridge Rule and pass parameters to the function.

The required parameters are sandbox, currency and amount. Example:

{
   "sandbox" : false,
   "currency": "BTCUSD",
   "amount": 10
}

or

{
   "sandbox" : false,
   "currency": "ETHUSD",
   "amount": 5
}

An example of all of the currently supported parameters and their applicable default values.

{
   "sandbox" : true,
   "orderFillFactor" : 0.999,
   "currency": "BTCUSD",
   "amount": 0,
   "includeFear" : false,
   "fearFloor" : 20,
   "fearMultiplier" : 1.5,
   "includeGreed" : false,
   "greedCeiling" : 80,
   "greedMultiplier" : 0.5
}

The Fear and Greed Index analyzes the current sentiment of the Bitcoin market and converts the data into a simple meter from 0 to 100. Zero means "Extreme Fear", while 100 means "Extreme Greed". The index is for BTC only and utilizes 5 metrics.

• Volatility (25 %)
• Market Momentum/Volume (25%)
• Social Media (15%)
• Surveys (15%) currently paused
• Dominance (10%)
• Trends (10%)

Instead of pasting your public and private API keys directly into the lambda function they should be stored in the AWS Systems Manager Parameter Store.

1. Go to the AWS Systems Manager > Parameter Store https://console.aws.amazon.com/systems-manager/parameters/
2. Click Create parameter
3. Set the Secret name as GeminiAPISandbox or GeminiAPI
4. Select Tier: Standard
5. Select Type: SecureString
6. Select Data type: text
7. Enter your Gemini public and private key into the value box as show here

{
  "API key": "account-YourPublicKeyHere",
  "API Secret": "YourPrivateKeyHere"
}

8. Finally, modify the Lambda function execution role to have an updated IAM Role with access to the SSM keys. This can be done by going to the Lambda function's Configuration > Permissions page, and editing the role to add the AmazonSSMReadOnlyAccess policy.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "ssm:Describe*",
                "ssm:Get*",
                "ssm:List*"
            ],
            "Resource": "*"
        }
    ]
}

Submit an Enhancement Request

bc1qqyhxl0cjj885t7aqh5fmygxxclg4xketq0suaz