Getting Started with CloudFix

CloudFix analyzes your AWS account to identify cost saving opportunities and execute fixes with a single click, resulting in immediate savings. Resource usage is automatically monitored across your AWS accounts to implement fixes at scale across your organization. Fixes are completely automated and require no downtime. The entire process is managed from your CloudFix dashboard and can be accomplished in a matter of minutes.

Creating a CloudFix account is simple and fast. Browse to the CloudFix site to provide your contact information, choose a password, and click submit. Finding cost-saving recommendations with CloudFix is FREE! You'll need a paid subscription only if you would like CloudFix to execute those recommendations.

CloudFix_Signup.png

After your account is created, login with your new credentials and you will be prompted to connect your first AWS account. Note that you need to be logged into the AWS console in a different tab of the same browser. Cloud Formation is used to configure your account with the appropriate permissions so that CloudFix can both identify and execute fixes.

Read permissions are used to monitor resource usage and identify cost optimizations. Recommended fixes can be applied using the CloudFix dashboard. Fixes are run in an automated fashion by CloudFix using permissions  to create snapshot backups and modify EBS volumes in a safe manner with no downtime.

To connect your account with CloudFix and establish the necessary permissions, click the Run Template button.

CloudFix_Connect_AWS_Account.png

This will open a Cloud Formation page in the AWS console with all of the necessary information populated. The Quick Create Stack interface lists the CloudFix template that will be used and a default template name. Scroll to the bottom of the page and click Create Stack to connect your account.

Resources Created by the Cloud Formation Stack

The CloudFix Cloud Formation stack creates two IAM roles in your account that are assumed by CloudFix. These roles are used to find recommendations and apply fixes.

  1. The Finder role is used to monitor resource usage and identify cost-savings opportunities. This includes permissions to APIs such as ec2:DescribeVolumesconfig:DeliverConfigSnapshot, and cloudwatch:GetMetricData.
  2. The Fixer role is used to safely automate and orchestrate cost optimization changes. This includes permissions such as ec2:ModifyVolumeec2:ModifyInstanceAttribute, and dlm:CreateLifecyclePolicy.

Note that both roles include permissions that will be used in forthcoming releases which include additional cost savings optimizations.

Using CloudFix to Apply Cost Optimization Fixes

Once the stack is created, CloudFix will begin monitoring your resources on a scheduled basis. Recommendations will appear in the CloudFix dashboard. The estimated and current savings amounts are displayed.

CloudFix_Recommendations.png

Use the icons to the right of each recommendation to take the desired action. You can choose to:

  1. Apply the fix now
  2. Schedule the fix to be run later during a maintenance window
  3. Discard the recommendation

Once fixes have been applied, they will appear in the Completed tab.

Note that EBS gp2 volumes are migrated in place to gp3 without any downtime. As a best practice, a snapshot is taken first of the EBS volume before performing the conversion. This allows for a rollback if for any reason it is desired.

You will receive an email once recommendations become available. Note that after the initial connection of your account with CloudFix, it may take up to an hour for recommendations to become available.

Emails will include information on the cost savings that can be realized by logging into CloudFix and applying the recommendations.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request