Auto Scaling

00Overview

Manage EC2 Auto Scaling groups from a flow — create and update groups, set desired capacity, and add or remove scaling policies and scheduled capacity changes without touching the AWS console. Move instances into and out of standby, attach or detach instances, attach load balancer target groups, mark instances healthy or unhealthy, and roll out a new launch template with an instance refresh. Read back group details, policies and recent scaling activities so a flow can react to what your fleet is actually doing.

Every field below is exactly what you see in the Flomation editor. Fields marked ● live picker let you choose from a list pulled live from your account — no IDs to look up.

01Connecting Auto Scaling

1. In the node's Authentication field, choose how Flomation signs its AWS calls: Access Keys (your own IAM key pair), Assume Role (cross-account) (Flomation's own identity assumes a role you grant it), or Managed Role (Credential) (a reusable AWS credential your admin has already configured).
2. For Access Keys, open the AWS IAM console (console.aws.amazon.com/iam) → Users, select or create a user, and under Security credentials choose Create access key. Attach a policy that grants Auto Scaling access — the AWS-managed AutoScalingFullAccess covers everything this node does.
3. Copy the Access key ID and Secret access key into the node's AWS Access Key and AWS Secret Key fields, and set Region to the region your Auto Scaling groups live in (e.g. us-east-1). If you are using temporary STS credentials, also paste the Session Token (optional).
4. For Assume Role (cross-account), create an IAM role in your account whose trust policy lets Flomation's principal call sts:AssumeRole, then put the role's ARN in Role ARN to Assume and, if the trust policy sets one, the matching Assume Role External ID (optional) — you enter no keys for this method.
5. For Managed Role (Credential), simply pick the pre-configured entry in the AWS Role Credential field.
6. In Flomation, store your secret access key as an environment secret (e.g. autoscaling_secret) rather than typing it inline, then select it in the node's AWS Secret Key field.

02Attach

AWS Attach Instances

aws/autoscaling/attach_instances · Action

Attach EC2 instances to an Auto Scaling group.

Returns: tool_result, auto_scaling_group_name

AWS Auto Scaling Attach Target Groups

aws/autoscaling/attach_load_balancer_target_groups · Action

Attach one or more load balancer target groups to an Auto Scaling group.

Returns: tool_result

03Create

AWS Create Auto Scaling Group

aws/autoscaling/create_auto_scaling_group · Action

Create an EC2 Auto Scaling group from a launch template.

Returns: tool_result, auto_scaling_group_name

04Delete

AWS Delete Auto Scaling Group

aws/autoscaling/delete_auto_scaling_group · Action

Delete an EC2 Auto Scaling group, optionally forcing termination.

Returns: tool_result, auto_scaling_group_name

AWS Auto Scaling Delete Policy

aws/autoscaling/delete_policy · Action

Delete a scaling policy from an Auto Scaling group by name or ARN.

Returns: tool_result

05Describe

AWS Describe Auto Scaling Groups

aws/autoscaling/describe_auto_scaling_groups · Action

List EC2 Auto Scaling groups with size and health details.

Returns: tool_result, groups, count

AWS Auto Scaling Describe Policies

aws/autoscaling/describe_policies · Action

List scaling policies for an Auto Scaling group.

Returns: tool_result, policies, count

AWS Auto Scaling Describe Activities

aws/autoscaling/describe_scaling_activities · Action

List recent scaling activities for an Auto Scaling group.

Returns: tool_result, activities, count

06Detach

AWS Detach Instances

aws/autoscaling/detach_instances · Action

Detach EC2 instances from an Auto Scaling group.

Returns: tool_result, auto_scaling_group_name

07Enter

AWS Auto Scaling Enter Standby

aws/autoscaling/enter_standby · Action

Move Auto Scaling group instances into Standby state.

Returns: tool_result, activities

08Exit

AWS Auto Scaling Exit Standby

aws/autoscaling/exit_standby · Action

Return Auto Scaling group instances from Standby back into service.

Returns: tool_result, activities

09Put

AWS Auto Scaling Put Scaling Policy

aws/autoscaling/put_scaling_policy · Action

Create or update a scaling policy on an Auto Scaling group (target-tracking config is JSON).

Returns: tool_result, policy_arn

AWS Auto Scaling Put Scheduled Action

aws/autoscaling/put_scheduled_update_group_action · Action

Schedule a capacity change (min/max/desired) on an Auto Scaling group.

Returns: tool_result

10Set

AWS Set Desired Capacity

aws/autoscaling/set_desired_capacity · Action

Set the desired capacity of an EC2 Auto Scaling group.

Returns: tool_result, auto_scaling_group_name

AWS Set Instance Health

aws/autoscaling/set_instance_health · Action

Set the health status of an instance in an Auto Scaling group.

Returns: tool_result, instance_id

11Start

AWS Auto Scaling Start Instance Refresh

aws/autoscaling/start_instance_refresh · Action

Start a rolling instance refresh on an Auto Scaling group (preferences are JSON).

Returns: tool_result, instance_refresh_id

12Terminate

AWS Terminate Instance In Group

aws/autoscaling/terminate_instance_in_auto_scaling_group · Action

Terminate an EC2 instance in an Auto Scaling group.

Returns: tool_result, instance_id

13Update

AWS Update Auto Scaling Group

aws/autoscaling/update_auto_scaling_group · Action

Update size, health check or subnets of an Auto Scaling group.

Returns: tool_result, auto_scaling_group_name

14Notes & Limitations

Behaviours and constraints worth knowing before you build with these nodes.

• Every action is scoped to the single Region you select, so a group and the launch template, subnets and target groups it references must all live in that same region.
• Capacity and refresh actions return as soon as AWS accepts the request while instances launch or terminate in the background, so use Describe Scaling Activities to confirm a change actually completed.
• Setting a desired capacity outside the group's current minimum or maximum size is rejected, so widen the bounds with Update Auto Scaling Group first when scaling beyond them.
• Deleting a group that still contains instances or has in-progress scaling activity fails unless Force Delete is enabled, which removes the group and terminates its instances without waiting for lifecycle hooks.
• Terminate Instance and Set Instance Health identify the owning group from the instance itself, so the instance must currently be a member of an Auto Scaling group.
• A scheduled action's recurrence cron runs in UTC unless you set a Time Zone, and a one-off action needs a Start Time rather than a recurrence.