Fylamynt Product Docs
  • Welcome to Fylamynt
  • Getting started
    • Onboarding Checklist
    • 1. Setting up your first Cloud Service target account
    • 2. Getting to know workflows
    • 3. Creating your first workflow using AWS Cloud Services
    • 4. Setting up your first Integration
    • 5. Setting up your first resource
    • 6. Creating your first Incident Response workflow
    • 7. Incident Management - Automatic workflow execution
    • 8. Quickstart - Fylamynt sample workflows
  • Integrations
    • Amazon EventBridge
    • Ansible
    • AWS
    • AWS Health
    • Container
    • Datadog
    • Elasticsearch
    • Generic Webhook
    • GitHub
    • Google Kubernetes Engine (GKE)
    • Humio
    • Instana
    • Jenkins
    • Jira
    • New Relic
    • Opsgenie
    • PagerDuty
    • Pulumi
    • Prometheus
    • ServiceNow
    • Slack
    • Splunk
    • Splunk On-Call (VictorOps)
    • Spot by Netapp
    • Squadcast
    • Sumo Logic
    • Teleport
    • Terraform Cloud
    • Terraform CLI
    • Twilio
    • Zoom
  • AWS Services
    • EC2
    • Service Health
  • RESOURCES
    • API Keys
    • CloudFormation Templates
    • CloudWatch Targets
    • EKS Permissions
    • S3 Buckets
    • SSH Targets
  • FEATURED WORKFLOWS
    • Stop or Terminate underutilized AWS resources
    • Rightsizing EC2 instances
    • Incident Response Automation
    • Application Performance Monitoring
  • Announcement
    • What's new?
  • Support
    • Contact Fylamynt
Powered by GitBook
On this page
  • Category:
  • Workflow name:
  • Description:
  • Integrations:
  • Workflow review:

Was this helpful?

  1. FEATURED WORKFLOWS

Rightsizing EC2 instances

Cost Optimization Featured Workflow

PreviousStop or Terminate underutilized AWS resourcesNextIncident Response Automation

Last updated 3 years ago

Was this helpful?

Category:

AWS Cost Optimization

Workflow name:

Rightsize EC2 on AWS RightSizing Recommendation

Description:

If you have overprovisioned EC2 instances, chances are you’re paying for resources you do not need. AWS Cost Management provides rightsizing recommendations for greater cost and usage efficiencies by reviewing your historical EC2 usage. We found that even though AWS and Cost Management Tools make it easy to identify the new EC2 instance types, the problem however is taking action on the recommendations. When rightsizing EC2 there are many factors to take into consideration and we love to work with you defining those for your specific situation.

Integrations:

Workflow review:

Our example workflow retrieves all the EC2 rightsizing recommendations from AWS Cost Management however this can also be replaced by your favorite Cost Management Solutions if it has the appropriate APIs available to retrieve this information.

The recommendations MapList output from Trusted Advisor is then used as the input for the JSONPATH action node which extracts the instance ID and recommended new instance type for each EC2 instance using a Path Expression.

The workflow then transforms the JSON to string, and a message is sent to a specified Slack channel with variables listing the EC2 recommendations and recommended sizes.

An approval request is then sent to a Slack channel to resize the instance.

The workflow succeeds if the execution status of the resize action node returns an OK condition.

Our example workflow does not have a trigger to automatically execute it, but through Fylamynt’s Task Manager a recurring schedule can be configured.

Before we review the workflow let’s look at the different tools and integration required to make this happen. First off an has to be configured which provides no-code drag and drop ability to use AWS and allows you to call any AWS API endpoint supported by the boto3 library. And lastly, we require a that provides the ability to send messages and approval requests to your Slack Team.

If a user approves the request the workflow stops the EC2 instance using the .

The workflow then waits for the stop process to complete, and using the node the instance type of the EC2 is changes to the recommended type.

AWS Target account
Execution action node
Slack integration
AWS Execution action node
EC2 Resize Instances action