FUSE
CUSTOMER ONBOARDING

Connect AWS in under 60 seconds.

Fuse deploys an isolated, cross-account IAM role in your AWS account with scoped CloudWatch metric reads and regional WAF IP block permissions.

1
Register Target API
Specify AWS Account and REST API Gateway
2
1-Click CloudFormation
Deploy verified IAM trust policy
3
Verify & Activate
Autonomous telemetry handshake
Zero-Trust Credential Security

We never request IAM user keys. Access is bounded by secret ExternalId and short-lived sts:AssumeRole. Revoke anytime by deleting the stack.

Step 1: Register Target API

Define the AWS environment you want Fuse to monitor.

Step 2: Deploy IAM Role

Deploy the CloudFormation template in your AWS Management Console.

YOUR UNIQUE EXTERNAL ID
—
1-Click Launch in AWS Console →

Opens CloudFormation with pre-filled parameters. Click "Create Stack".


Final Step: Provision & Attach WAF in Your Account

The CloudFormation template provisions the cross-account IAM role for Fuse. If you don't already have a WAF Web ACL, run these 3 AWS CLI commands in your account to create the IPSet, create the Web ACL, and attach it to your API Gateway stage:

1. CREATE FUSE IPSET
aws wafv2 create-ip-set \
  --name fuse-blocked-ips \
  --scope REGIONAL \
  --ip-address-version IPV4 \
  --addresses '[]' \
  --description "Fuse Guardrail: Blocked runaway caller IPs"
2. CREATE WAF WEB ACL (ATTACH IPSET RULE)
aws wafv2 create-web-acl \
  --name fuse-guardrail-acl \
  --scope REGIONAL \
  --default-action Allow={} \
  --visibility-config SampledRequestsEnabled=true,CloudWatchMetricsEnabled=true,MetricName=fuse-guardrail-acl \
  --rules '[{"Name":"fuse-block-runaway-ips","Priority":0,"Statement":{"IPSetReferenceStatement":{"ARN":"arn:aws:wafv2:<REGION>:<ACCOUNT_ID>:regional/ipset/fuse-blocked-ips/<IPSET_ID>"}},"Action":{"Block":{}},"VisibilityConfig":{"SampledRequestsEnabled":true,"CloudWatchMetricsEnabled":true,"MetricName":"fuse-blocked-ips"}}]'
3. ASSOCIATE WEB ACL TO API GATEWAY STAGE
aws wafv2 associate-web-acl \
  --web-acl-arn <YOUR_WEB_ACL_ARN> \
  --resource-arn arn:aws:apigateway:<REGION>::/restapis/<API_ID>/stages/<STAGE>
4. VERIFY ATTACHMENT
aws wafv2 get-web-acl-for-resource \
  --resource-arn arn:aws:apigateway:<REGION>::/restapis/<API_ID>/stages/<STAGE>

Verify Connection

Once the stack status is CREATE_COMPLETE, verify the role ARN:

✓

Guardrail Activated Successfully!

Fuse has verified short-lived cross-account access. Your API Gateway is now protected by out-of-band statistical anomaly detection and surgical WAF containment.

WAF Attachment Verification

Remember to ensure your WAF Web ACL is associated with the monitored API stage so that IP blocks applied by Fuse take immediate effect:

aws wafv2 get-web-acl-for-resource --resource-arn arn:aws:apigateway:<REGION>::/restapis/<API_ID>/stages/<STAGE>
Open Fuse Operator Console →