Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

RequestSpotInstancesRequest

import type { RequestSpotInstancesRequest } from "https://aws-api.deno.dev/v0.3/services/ec2.ts?docs=full";

Contains the parameters for RequestSpotInstances.

interface RequestSpotInstancesRequest {
AvailabilityZoneGroup?: string | null;
BlockDurationMinutes?: number | null;
ClientToken?: string | null;
DryRun?: boolean | null;
InstanceCount?: number | null;
InstanceInterruptionBehavior?: InstanceInterruptionBehavior | null;
LaunchGroup?: string | null;
LaunchSpecification?: RequestSpotLaunchSpecification | null;
SpotPrice?: string | null;
TagSpecifications?: TagSpecification[] | null;
Type?: SpotInstanceType | null;
ValidFrom?: Date | number | null;
ValidUntil?: Date | number | null;
}

§Properties

§
AvailabilityZoneGroup?: string | null
[src]

The user-specified name for a logical grouping of requests.

When you specify an Availability Zone group in a Spot Instance request, all Spot Instances in the request are launched in the same Availability Zone. Instance proximity is maintained with this parameter, but the choice of Availability Zone is not. The group applies only to requests for Spot Instances of the same instance type. Any additional Spot Instance requests that are specified with the same Availability Zone group name are launched in that same Availability Zone, as long as at least one instance from the group is still active.

If there is no active instance running in the Availability Zone group that you specify for a new Spot Instance request (all instances are terminated, the request is expired, or the maximum price you specified falls below current Spot price), then Amazon EC2 launches the instance in any Availability Zone where the constraint can be met. Consequently, the subsequent set of Spot Instances could be placed in a different zone from the original request, even if you specified the same Availability Zone group.

Default: Instances are launched in any available Availability Zone.

§
BlockDurationMinutes?: number | null
[src]

Deprecated.

§
ClientToken?: string | null
[src]

Unique, case-sensitive identifier that you provide to ensure the idempotency of the request. For more information, see How to Ensure Idempotency in the Amazon EC2 User Guide for Linux Instances.

§
DryRun?: boolean | null
[src]

Checks whether you have the required permissions for the action, without actually making the request, and provides an error response. If you have the required permissions, the error response is DryRunOperation. Otherwise, it is UnauthorizedOperation.

§
InstanceCount?: number | null
[src]

The maximum number of Spot Instances to launch.

Default: 1

§
InstanceInterruptionBehavior?: InstanceInterruptionBehavior | null
[src]

The behavior when a Spot Instance is interrupted. The default is terminate.

§
LaunchGroup?: string | null
[src]

The instance launch group. Launch groups are Spot Instances that launch together and terminate together.

Default: Instances are launched and terminated individually

§
LaunchSpecification?: RequestSpotLaunchSpecification | null
[src]

The launch specification.

§
SpotPrice?: string | null
[src]

The maximum price per hour that you are willing to pay for a Spot Instance. The default is the On-Demand price.

§
TagSpecifications?: TagSpecification[] | null
[src]

The key-value pair for tagging the Spot Instance request on creation. The value for ResourceType must be spot-instances-request, otherwise the Spot Instance request fails. To tag the Spot Instance request after it has been created, see CreateTags.

§
Type?: SpotInstanceType | null
[src]

The Spot Instance request type.

Default: one-time

§
ValidFrom?: Date | number | null
[src]

The start date of the request. If this is a one-time request, the request becomes active at this date and time and remains active until all instances launch, the request expires, or the request is canceled. If the request is persistent, the request becomes active at this date and time and remains active until it expires or is canceled.

The specified start date and time cannot be equal to the current date and time. You must specify a start date and time that occurs after the current date and time.

§
ValidUntil?: Date | number | null
[src]

The end date of the request, in UTC format (YYYY-MM-DD_T_HH:MM:_SS_Z).

  • For a persistent request, the request remains active until the ValidUntil date and time is reached. Otherwise, the request remains active until you cancel it.
  • For a one-time request, the request remains active until all instances launch, the request is canceled, or the ValidUntil date and time is reached. By default, the request is valid for 7 days from the date the request was created.