Amazon GameLift · Arazzo Workflow

Amazon GameLift Verify Build Readiness then Create a Fleet

Version 1.0.0

Poll a build until it is READY, then create a fleet that deploys it.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub Cloud ComputingGame ServersGamingMultiplayerMatchmakingFlexMatchFleetIQArazzoWorkflows

Provider

amazon-gamelift

Workflows

verify-build-create-fleet
Poll a build until READY, then create a fleet from it.
Repeatedly describes a build until it is READY (or FAILED), then creates a fleet that deploys the build.
2 steps inputs: buildId, ec2InstanceType, fleetName, runtimeConfiguration outputs: buildStatus, fleetId
1
pollBuildReady
Describe the build and check its status. Repeat while INITIALIZED; proceed once the build is READY, or end if it FAILED.
2
createFleet
Create a fleet that deploys the READY build on EC2 instances.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Amazon GameLift Verify Build Readiness then Create a Fleet
  summary: Poll a build until it is READY, then create a fleet that deploys it.
  description: >-
    Fleets can only be created from builds in READY status, which a build
    reaches after its files finish uploading. This workflow polls an existing
    build until it reports READY (branching to a terminal end if the build
    FAILED), and then creates a fleet that deploys the build on EC2 instances.
    Each step spells out its AWS JSON protocol request inline, including the
    X-Amz-Target header, so the flow can be read and executed without opening
    the underlying OpenAPI description.
  version: 1.0.0
  x-realizes-capability-ids:
  - BC-600.50
  x-capability-derivation:
    method: 'deterministic join: sourceDescriptions -> per-tag OpenAPI -> tag/capability edge. No classification at this step.'
    min_confidence: 0.7
    sources:
    - capability_id: BC-600.50
      capability_name: IT Infrastructure Management
      spec: amazon-gamelift-x-amz-target-gamelift-createfleet-api-openapi.yml
      confidence: 0.7
    model: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
sourceDescriptions:
- name: xAmzTargetGameliftCreatefleetApi
  url: ../openapi/amazon-gamelift-x-amz-target-gamelift-createfleet-api-openapi.yml
  type: openapi
- name: xAmzTargetGameliftDescribebuildApi
  url: ../openapi/amazon-gamelift-x-amz-target-gamelift-describebuild-api-openapi.yml
  type: openapi
workflows:
- workflowId: verify-build-create-fleet
  summary: Poll a build until READY, then create a fleet from it.
  description: >-
    Repeatedly describes a build until it is READY (or FAILED), then creates a
    fleet that deploys the build.
  inputs:
    type: object
    required:
    - buildId
    - fleetName
    - ec2InstanceType
    - runtimeConfiguration
    properties:
      buildId:
        type: string
        description: The build ID or ARN to verify and deploy.
      fleetName:
        type: string
        description: A descriptive label for the new fleet.
      ec2InstanceType:
        type: string
        description: The EC2 instance type to host game servers on (e.g. c5.large).
      runtimeConfiguration:
        type: object
        description: Instructions for how to launch and maintain server processes on each instance.
  steps:
  - stepId: pollBuildReady
    description: >-
      Describe the build and check its status. Repeat while INITIALIZED;
      proceed once the build is READY, or end if it FAILED.
    operationId: DescribeBuild
    parameters:
    - name: X-Amz-Target
      in: header
      value: GameLift.DescribeBuild
    requestBody:
      contentType: application/x-amz-json-1.1
      payload:
        BuildId: $inputs.buildId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      buildStatus: $response.body#/Build/Status
    onSuccess:
    - name: buildReady
      type: goto
      stepId: createFleet
      criteria:
      - context: $response.body
        condition: $.Build.Status == "READY"
        type: jsonpath
    - name: buildFailed
      type: end
      criteria:
      - context: $response.body
        condition: $.Build.Status == "FAILED"
        type: jsonpath
    - name: buildInitializing
      type: goto
      stepId: pollBuildReady
      criteria:
      - context: $response.body
        condition: $.Build.Status == "INITIALIZED"
        type: jsonpath
  - stepId: createFleet
    description: >-
      Create a fleet that deploys the READY build on EC2 instances.
    operationId: CreateFleet
    parameters:
    - name: X-Amz-Target
      in: header
      value: GameLift.CreateFleet
    requestBody:
      contentType: application/x-amz-json-1.1
      payload:
        Name: $inputs.fleetName
        BuildId: $inputs.buildId
        EC2InstanceType: $inputs.ec2InstanceType
        RuntimeConfiguration: $inputs.runtimeConfiguration
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      fleetId: $response.body#/FleetAttributes/FleetId
      fleetStatus: $response.body#/FleetAttributes/Status
  outputs:
    buildStatus: $steps.pollBuildReady.outputs.buildStatus
    fleetId: $steps.createFleet.outputs.fleetId

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/amazon-gamelift-verify-build-create-fleet-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.