We recommend new projects start with resources from the AWS provider.
aws-native.codebuild.Fleet
Explore with Pulumi AI
We recommend new projects start with resources from the AWS provider.
Resource Type definition for AWS::CodeBuild::Fleet
Create Fleet Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new Fleet(name: string, args?: FleetArgs, opts?: CustomResourceOptions);
@overload
def Fleet(resource_name: str,
args: Optional[FleetArgs] = None,
opts: Optional[ResourceOptions] = None)
@overload
def Fleet(resource_name: str,
opts: Optional[ResourceOptions] = None,
base_capacity: Optional[int] = None,
compute_configuration: Optional[FleetComputeConfigurationArgs] = None,
compute_type: Optional[FleetComputeType] = None,
environment_type: Optional[FleetEnvironmentType] = None,
fleet_proxy_configuration: Optional[FleetProxyConfigurationArgs] = None,
fleet_service_role: Optional[str] = None,
fleet_vpc_config: Optional[FleetVpcConfigArgs] = None,
image_id: Optional[str] = None,
name: Optional[str] = None,
overflow_behavior: Optional[FleetOverflowBehavior] = None,
scaling_configuration: Optional[FleetScalingConfigurationInputArgs] = None,
tags: Optional[Sequence[_root_inputs.TagArgs]] = None)
func NewFleet(ctx *Context, name string, args *FleetArgs, opts ...ResourceOption) (*Fleet, error)
public Fleet(string name, FleetArgs? args = null, CustomResourceOptions? opts = null)
type: aws-native:codebuild:Fleet
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name string
- The unique name of the resource.
- args FleetArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args FleetArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args FleetArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args FleetArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args FleetArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Fleet Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.
The Fleet resource accepts the following input properties:
- Base
Capacity int - The initial number of machines allocated to the compute fleet, which defines the number of builds that can run in parallel.
- Compute
Configuration Pulumi.Aws Native. Code Build. Inputs. Fleet Compute Configuration - The compute configuration of the compute fleet. This is only required if
computeType
is set toATTRIBUTE_BASED_COMPUTE
. - Compute
Type Pulumi.Aws Native. Code Build. Fleet Compute Type Information about the compute resources the compute fleet uses. Available values include:
ATTRIBUTE_BASED_COMPUTE
: Specify the amount of vCPUs, memory, disk space, and the type of machine.
If you use
ATTRIBUTE_BASED_COMPUTE
, you must define your attributes by usingcomputeConfiguration
. AWS CodeBuild will select the cheapest instance that satisfies your specified attributes. For more information, see Reserved capacity environment types in the AWS CodeBuild User Guide .BUILD_GENERAL1_SMALL
: Use up to 4 GiB memory and 2 vCPUs for builds.BUILD_GENERAL1_MEDIUM
: Use up to 8 GiB memory and 4 vCPUs for builds.BUILD_GENERAL1_LARGE
: Use up to 16 GiB memory and 8 vCPUs for builds, depending on your environment type.BUILD_GENERAL1_XLARGE
: Use up to 72 GiB memory and 36 vCPUs for builds, depending on your environment type.BUILD_GENERAL1_2XLARGE
: Use up to 144 GiB memory, 72 vCPUs, and 824 GB of SSD storage for builds. This compute type supports Docker images up to 100 GB uncompressed.BUILD_LAMBDA_1GB
: Use up to 1 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.BUILD_LAMBDA_2GB
: Use up to 2 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.BUILD_LAMBDA_4GB
: Use up to 4 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.BUILD_LAMBDA_8GB
: Use up to 8 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.BUILD_LAMBDA_10GB
: Use up to 10 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.
If you use
BUILD_GENERAL1_SMALL
:- For environment type
LINUX_CONTAINER
, you can use up to 4 GiB memory and 2 vCPUs for builds. - For environment type
LINUX_GPU_CONTAINER
, you can use up to 16 GiB memory, 4 vCPUs, and 1 NVIDIA A10G Tensor Core GPU for builds. - For environment type
ARM_CONTAINER
, you can use up to 4 GiB memory and 2 vCPUs on ARM-based processors for builds.
If you use
BUILD_GENERAL1_LARGE
:- For environment type
LINUX_CONTAINER
, you can use up to 16 GiB memory and 8 vCPUs for builds. - For environment type
LINUX_GPU_CONTAINER
, you can use up to 255 GiB memory, 32 vCPUs, and 4 NVIDIA Tesla V100 GPUs for builds. - For environment type
ARM_CONTAINER
, you can use up to 16 GiB memory and 8 vCPUs on ARM-based processors for builds.
For more information, see On-demand environment types in the AWS CodeBuild User Guide.
- Environment
Type Pulumi.Aws Native. Code Build. Fleet Environment Type The environment type of the compute fleet.
- The environment type
ARM_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), Asia Pacific (Mumbai), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), EU (Frankfurt), and South America (São Paulo). - The environment type
ARM_EC2
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), South America (São Paulo), and Asia Pacific (Mumbai). - The environment type
LINUX_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), South America (São Paulo), and Asia Pacific (Mumbai). - The environment type
LINUX_EC2
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), South America (São Paulo), and Asia Pacific (Mumbai). - The environment type
LINUX_GPU_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), and Asia Pacific (Sydney). - The environment type
MAC_ARM
is available only in regions US East (Ohio), US East (N. Virginia), US West (Oregon), Europe (Frankfurt), and Asia Pacific (Sydney). - The environment type
WINDOWS_EC2
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), South America (São Paulo), and Asia Pacific (Mumbai). - The environment type
WINDOWS_SERVER_2019_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Sydney), Asia Pacific (Tokyo), Asia Pacific (Mumbai) and EU (Ireland). - The environment type
WINDOWS_SERVER_2022_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Sydney), Asia Pacific (Singapore), Asia Pacific (Tokyo), South America (São Paulo) and Asia Pacific (Mumbai).
For more information, see Build environment compute types in the AWS CodeBuild user guide .
- The environment type
- Fleet
Proxy Pulumi.Configuration Aws Native. Code Build. Inputs. Fleet Proxy Configuration - Information about the proxy configurations that apply network access control to your reserved capacity instances.
- Fleet
Service stringRole - The service role associated with the compute fleet. For more information, see Allow a user to add a permission policy for a fleet service role in the AWS CodeBuild User Guide .
- Fleet
Vpc Pulumi.Config Aws Native. Code Build. Inputs. Fleet Vpc Config - Information about the VPC configuration that AWS CodeBuild accesses.
- Image
Id string - The Amazon Machine Image (AMI) of the compute fleet.
- Name string
- The name of the compute fleet.
- Overflow
Behavior Pulumi.Aws Native. Code Build. Fleet Overflow Behavior The compute fleet overflow behavior.
- For overflow behavior
QUEUE
, your overflow builds need to wait on the existing fleet instance to become available. - For overflow behavior
ON_DEMAND
, your overflow builds run on CodeBuild on-demand.
If you choose to set your overflow behavior to on-demand while creating a VPC-connected fleet, make sure that you add the required VPC permissions to your project service role. For more information, see Example policy statement to allow CodeBuild access to AWS services required to create a VPC network interface .
- For overflow behavior
- Scaling
Configuration Pulumi.Aws Native. Code Build. Inputs. Fleet Scaling Configuration Input - The scaling configuration of the compute fleet.
- List<Pulumi.
Aws Native. Inputs. Tag> A list of tag key and value pairs associated with this compute fleet.
These tags are available for use by AWS services that support AWS CodeBuild compute fleet tags.
- Base
Capacity int - The initial number of machines allocated to the compute fleet, which defines the number of builds that can run in parallel.
- Compute
Configuration FleetCompute Configuration Args - The compute configuration of the compute fleet. This is only required if
computeType
is set toATTRIBUTE_BASED_COMPUTE
. - Compute
Type FleetCompute Type Information about the compute resources the compute fleet uses. Available values include:
ATTRIBUTE_BASED_COMPUTE
: Specify the amount of vCPUs, memory, disk space, and the type of machine.
If you use
ATTRIBUTE_BASED_COMPUTE
, you must define your attributes by usingcomputeConfiguration
. AWS CodeBuild will select the cheapest instance that satisfies your specified attributes. For more information, see Reserved capacity environment types in the AWS CodeBuild User Guide .BUILD_GENERAL1_SMALL
: Use up to 4 GiB memory and 2 vCPUs for builds.BUILD_GENERAL1_MEDIUM
: Use up to 8 GiB memory and 4 vCPUs for builds.BUILD_GENERAL1_LARGE
: Use up to 16 GiB memory and 8 vCPUs for builds, depending on your environment type.BUILD_GENERAL1_XLARGE
: Use up to 72 GiB memory and 36 vCPUs for builds, depending on your environment type.BUILD_GENERAL1_2XLARGE
: Use up to 144 GiB memory, 72 vCPUs, and 824 GB of SSD storage for builds. This compute type supports Docker images up to 100 GB uncompressed.BUILD_LAMBDA_1GB
: Use up to 1 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.BUILD_LAMBDA_2GB
: Use up to 2 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.BUILD_LAMBDA_4GB
: Use up to 4 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.BUILD_LAMBDA_8GB
: Use up to 8 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.BUILD_LAMBDA_10GB
: Use up to 10 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.
If you use
BUILD_GENERAL1_SMALL
:- For environment type
LINUX_CONTAINER
, you can use up to 4 GiB memory and 2 vCPUs for builds. - For environment type
LINUX_GPU_CONTAINER
, you can use up to 16 GiB memory, 4 vCPUs, and 1 NVIDIA A10G Tensor Core GPU for builds. - For environment type
ARM_CONTAINER
, you can use up to 4 GiB memory and 2 vCPUs on ARM-based processors for builds.
If you use
BUILD_GENERAL1_LARGE
:- For environment type
LINUX_CONTAINER
, you can use up to 16 GiB memory and 8 vCPUs for builds. - For environment type
LINUX_GPU_CONTAINER
, you can use up to 255 GiB memory, 32 vCPUs, and 4 NVIDIA Tesla V100 GPUs for builds. - For environment type
ARM_CONTAINER
, you can use up to 16 GiB memory and 8 vCPUs on ARM-based processors for builds.
For more information, see On-demand environment types in the AWS CodeBuild User Guide.
- Environment
Type FleetEnvironment Type The environment type of the compute fleet.
- The environment type
ARM_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), Asia Pacific (Mumbai), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), EU (Frankfurt), and South America (São Paulo). - The environment type
ARM_EC2
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), South America (São Paulo), and Asia Pacific (Mumbai). - The environment type
LINUX_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), South America (São Paulo), and Asia Pacific (Mumbai). - The environment type
LINUX_EC2
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), South America (São Paulo), and Asia Pacific (Mumbai). - The environment type
LINUX_GPU_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), and Asia Pacific (Sydney). - The environment type
MAC_ARM
is available only in regions US East (Ohio), US East (N. Virginia), US West (Oregon), Europe (Frankfurt), and Asia Pacific (Sydney). - The environment type
WINDOWS_EC2
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), South America (São Paulo), and Asia Pacific (Mumbai). - The environment type
WINDOWS_SERVER_2019_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Sydney), Asia Pacific (Tokyo), Asia Pacific (Mumbai) and EU (Ireland). - The environment type
WINDOWS_SERVER_2022_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Sydney), Asia Pacific (Singapore), Asia Pacific (Tokyo), South America (São Paulo) and Asia Pacific (Mumbai).
For more information, see Build environment compute types in the AWS CodeBuild user guide .
- The environment type
- Fleet
Proxy FleetConfiguration Proxy Configuration Args - Information about the proxy configurations that apply network access control to your reserved capacity instances.
- Fleet
Service stringRole - The service role associated with the compute fleet. For more information, see Allow a user to add a permission policy for a fleet service role in the AWS CodeBuild User Guide .
- Fleet
Vpc FleetConfig Vpc Config Args - Information about the VPC configuration that AWS CodeBuild accesses.
- Image
Id string - The Amazon Machine Image (AMI) of the compute fleet.
- Name string
- The name of the compute fleet.
- Overflow
Behavior FleetOverflow Behavior The compute fleet overflow behavior.
- For overflow behavior
QUEUE
, your overflow builds need to wait on the existing fleet instance to become available. - For overflow behavior
ON_DEMAND
, your overflow builds run on CodeBuild on-demand.
If you choose to set your overflow behavior to on-demand while creating a VPC-connected fleet, make sure that you add the required VPC permissions to your project service role. For more information, see Example policy statement to allow CodeBuild access to AWS services required to create a VPC network interface .
- For overflow behavior
- Scaling
Configuration FleetScaling Configuration Input Args - The scaling configuration of the compute fleet.
- Tag
Args A list of tag key and value pairs associated with this compute fleet.
These tags are available for use by AWS services that support AWS CodeBuild compute fleet tags.
- base
Capacity Integer - The initial number of machines allocated to the compute fleet, which defines the number of builds that can run in parallel.
- compute
Configuration FleetCompute Configuration - The compute configuration of the compute fleet. This is only required if
computeType
is set toATTRIBUTE_BASED_COMPUTE
. - compute
Type FleetCompute Type Information about the compute resources the compute fleet uses. Available values include:
ATTRIBUTE_BASED_COMPUTE
: Specify the amount of vCPUs, memory, disk space, and the type of machine.
If you use
ATTRIBUTE_BASED_COMPUTE
, you must define your attributes by usingcomputeConfiguration
. AWS CodeBuild will select the cheapest instance that satisfies your specified attributes. For more information, see Reserved capacity environment types in the AWS CodeBuild User Guide .BUILD_GENERAL1_SMALL
: Use up to 4 GiB memory and 2 vCPUs for builds.BUILD_GENERAL1_MEDIUM
: Use up to 8 GiB memory and 4 vCPUs for builds.BUILD_GENERAL1_LARGE
: Use up to 16 GiB memory and 8 vCPUs for builds, depending on your environment type.BUILD_GENERAL1_XLARGE
: Use up to 72 GiB memory and 36 vCPUs for builds, depending on your environment type.BUILD_GENERAL1_2XLARGE
: Use up to 144 GiB memory, 72 vCPUs, and 824 GB of SSD storage for builds. This compute type supports Docker images up to 100 GB uncompressed.BUILD_LAMBDA_1GB
: Use up to 1 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.BUILD_LAMBDA_2GB
: Use up to 2 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.BUILD_LAMBDA_4GB
: Use up to 4 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.BUILD_LAMBDA_8GB
: Use up to 8 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.BUILD_LAMBDA_10GB
: Use up to 10 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.
If you use
BUILD_GENERAL1_SMALL
:- For environment type
LINUX_CONTAINER
, you can use up to 4 GiB memory and 2 vCPUs for builds. - For environment type
LINUX_GPU_CONTAINER
, you can use up to 16 GiB memory, 4 vCPUs, and 1 NVIDIA A10G Tensor Core GPU for builds. - For environment type
ARM_CONTAINER
, you can use up to 4 GiB memory and 2 vCPUs on ARM-based processors for builds.
If you use
BUILD_GENERAL1_LARGE
:- For environment type
LINUX_CONTAINER
, you can use up to 16 GiB memory and 8 vCPUs for builds. - For environment type
LINUX_GPU_CONTAINER
, you can use up to 255 GiB memory, 32 vCPUs, and 4 NVIDIA Tesla V100 GPUs for builds. - For environment type
ARM_CONTAINER
, you can use up to 16 GiB memory and 8 vCPUs on ARM-based processors for builds.
For more information, see On-demand environment types in the AWS CodeBuild User Guide.
- environment
Type FleetEnvironment Type The environment type of the compute fleet.
- The environment type
ARM_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), Asia Pacific (Mumbai), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), EU (Frankfurt), and South America (São Paulo). - The environment type
ARM_EC2
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), South America (São Paulo), and Asia Pacific (Mumbai). - The environment type
LINUX_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), South America (São Paulo), and Asia Pacific (Mumbai). - The environment type
LINUX_EC2
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), South America (São Paulo), and Asia Pacific (Mumbai). - The environment type
LINUX_GPU_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), and Asia Pacific (Sydney). - The environment type
MAC_ARM
is available only in regions US East (Ohio), US East (N. Virginia), US West (Oregon), Europe (Frankfurt), and Asia Pacific (Sydney). - The environment type
WINDOWS_EC2
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), South America (São Paulo), and Asia Pacific (Mumbai). - The environment type
WINDOWS_SERVER_2019_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Sydney), Asia Pacific (Tokyo), Asia Pacific (Mumbai) and EU (Ireland). - The environment type
WINDOWS_SERVER_2022_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Sydney), Asia Pacific (Singapore), Asia Pacific (Tokyo), South America (São Paulo) and Asia Pacific (Mumbai).
For more information, see Build environment compute types in the AWS CodeBuild user guide .
- The environment type
- fleet
Proxy FleetConfiguration Proxy Configuration - Information about the proxy configurations that apply network access control to your reserved capacity instances.
- fleet
Service StringRole - The service role associated with the compute fleet. For more information, see Allow a user to add a permission policy for a fleet service role in the AWS CodeBuild User Guide .
- fleet
Vpc FleetConfig Vpc Config - Information about the VPC configuration that AWS CodeBuild accesses.
- image
Id String - The Amazon Machine Image (AMI) of the compute fleet.
- name String
- The name of the compute fleet.
- overflow
Behavior FleetOverflow Behavior The compute fleet overflow behavior.
- For overflow behavior
QUEUE
, your overflow builds need to wait on the existing fleet instance to become available. - For overflow behavior
ON_DEMAND
, your overflow builds run on CodeBuild on-demand.
If you choose to set your overflow behavior to on-demand while creating a VPC-connected fleet, make sure that you add the required VPC permissions to your project service role. For more information, see Example policy statement to allow CodeBuild access to AWS services required to create a VPC network interface .
- For overflow behavior
- scaling
Configuration FleetScaling Configuration Input - The scaling configuration of the compute fleet.
- List<Tag>
A list of tag key and value pairs associated with this compute fleet.
These tags are available for use by AWS services that support AWS CodeBuild compute fleet tags.
- base
Capacity number - The initial number of machines allocated to the compute fleet, which defines the number of builds that can run in parallel.
- compute
Configuration FleetCompute Configuration - The compute configuration of the compute fleet. This is only required if
computeType
is set toATTRIBUTE_BASED_COMPUTE
. - compute
Type FleetCompute Type Information about the compute resources the compute fleet uses. Available values include:
ATTRIBUTE_BASED_COMPUTE
: Specify the amount of vCPUs, memory, disk space, and the type of machine.
If you use
ATTRIBUTE_BASED_COMPUTE
, you must define your attributes by usingcomputeConfiguration
. AWS CodeBuild will select the cheapest instance that satisfies your specified attributes. For more information, see Reserved capacity environment types in the AWS CodeBuild User Guide .BUILD_GENERAL1_SMALL
: Use up to 4 GiB memory and 2 vCPUs for builds.BUILD_GENERAL1_MEDIUM
: Use up to 8 GiB memory and 4 vCPUs for builds.BUILD_GENERAL1_LARGE
: Use up to 16 GiB memory and 8 vCPUs for builds, depending on your environment type.BUILD_GENERAL1_XLARGE
: Use up to 72 GiB memory and 36 vCPUs for builds, depending on your environment type.BUILD_GENERAL1_2XLARGE
: Use up to 144 GiB memory, 72 vCPUs, and 824 GB of SSD storage for builds. This compute type supports Docker images up to 100 GB uncompressed.BUILD_LAMBDA_1GB
: Use up to 1 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.BUILD_LAMBDA_2GB
: Use up to 2 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.BUILD_LAMBDA_4GB
: Use up to 4 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.BUILD_LAMBDA_8GB
: Use up to 8 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.BUILD_LAMBDA_10GB
: Use up to 10 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.
If you use
BUILD_GENERAL1_SMALL
:- For environment type
LINUX_CONTAINER
, you can use up to 4 GiB memory and 2 vCPUs for builds. - For environment type
LINUX_GPU_CONTAINER
, you can use up to 16 GiB memory, 4 vCPUs, and 1 NVIDIA A10G Tensor Core GPU for builds. - For environment type
ARM_CONTAINER
, you can use up to 4 GiB memory and 2 vCPUs on ARM-based processors for builds.
If you use
BUILD_GENERAL1_LARGE
:- For environment type
LINUX_CONTAINER
, you can use up to 16 GiB memory and 8 vCPUs for builds. - For environment type
LINUX_GPU_CONTAINER
, you can use up to 255 GiB memory, 32 vCPUs, and 4 NVIDIA Tesla V100 GPUs for builds. - For environment type
ARM_CONTAINER
, you can use up to 16 GiB memory and 8 vCPUs on ARM-based processors for builds.
For more information, see On-demand environment types in the AWS CodeBuild User Guide.
- environment
Type FleetEnvironment Type The environment type of the compute fleet.
- The environment type
ARM_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), Asia Pacific (Mumbai), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), EU (Frankfurt), and South America (São Paulo). - The environment type
ARM_EC2
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), South America (São Paulo), and Asia Pacific (Mumbai). - The environment type
LINUX_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), South America (São Paulo), and Asia Pacific (Mumbai). - The environment type
LINUX_EC2
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), South America (São Paulo), and Asia Pacific (Mumbai). - The environment type
LINUX_GPU_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), and Asia Pacific (Sydney). - The environment type
MAC_ARM
is available only in regions US East (Ohio), US East (N. Virginia), US West (Oregon), Europe (Frankfurt), and Asia Pacific (Sydney). - The environment type
WINDOWS_EC2
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), South America (São Paulo), and Asia Pacific (Mumbai). - The environment type
WINDOWS_SERVER_2019_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Sydney), Asia Pacific (Tokyo), Asia Pacific (Mumbai) and EU (Ireland). - The environment type
WINDOWS_SERVER_2022_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Sydney), Asia Pacific (Singapore), Asia Pacific (Tokyo), South America (São Paulo) and Asia Pacific (Mumbai).
For more information, see Build environment compute types in the AWS CodeBuild user guide .
- The environment type
- fleet
Proxy FleetConfiguration Proxy Configuration - Information about the proxy configurations that apply network access control to your reserved capacity instances.
- fleet
Service stringRole - The service role associated with the compute fleet. For more information, see Allow a user to add a permission policy for a fleet service role in the AWS CodeBuild User Guide .
- fleet
Vpc FleetConfig Vpc Config - Information about the VPC configuration that AWS CodeBuild accesses.
- image
Id string - The Amazon Machine Image (AMI) of the compute fleet.
- name string
- The name of the compute fleet.
- overflow
Behavior FleetOverflow Behavior The compute fleet overflow behavior.
- For overflow behavior
QUEUE
, your overflow builds need to wait on the existing fleet instance to become available. - For overflow behavior
ON_DEMAND
, your overflow builds run on CodeBuild on-demand.
If you choose to set your overflow behavior to on-demand while creating a VPC-connected fleet, make sure that you add the required VPC permissions to your project service role. For more information, see Example policy statement to allow CodeBuild access to AWS services required to create a VPC network interface .
- For overflow behavior
- scaling
Configuration FleetScaling Configuration Input - The scaling configuration of the compute fleet.
- Tag[]
A list of tag key and value pairs associated with this compute fleet.
These tags are available for use by AWS services that support AWS CodeBuild compute fleet tags.
- base_
capacity int - The initial number of machines allocated to the compute fleet, which defines the number of builds that can run in parallel.
- compute_
configuration FleetCompute Configuration Args - The compute configuration of the compute fleet. This is only required if
computeType
is set toATTRIBUTE_BASED_COMPUTE
. - compute_
type FleetCompute Type Information about the compute resources the compute fleet uses. Available values include:
ATTRIBUTE_BASED_COMPUTE
: Specify the amount of vCPUs, memory, disk space, and the type of machine.
If you use
ATTRIBUTE_BASED_COMPUTE
, you must define your attributes by usingcomputeConfiguration
. AWS CodeBuild will select the cheapest instance that satisfies your specified attributes. For more information, see Reserved capacity environment types in the AWS CodeBuild User Guide .BUILD_GENERAL1_SMALL
: Use up to 4 GiB memory and 2 vCPUs for builds.BUILD_GENERAL1_MEDIUM
: Use up to 8 GiB memory and 4 vCPUs for builds.BUILD_GENERAL1_LARGE
: Use up to 16 GiB memory and 8 vCPUs for builds, depending on your environment type.BUILD_GENERAL1_XLARGE
: Use up to 72 GiB memory and 36 vCPUs for builds, depending on your environment type.BUILD_GENERAL1_2XLARGE
: Use up to 144 GiB memory, 72 vCPUs, and 824 GB of SSD storage for builds. This compute type supports Docker images up to 100 GB uncompressed.BUILD_LAMBDA_1GB
: Use up to 1 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.BUILD_LAMBDA_2GB
: Use up to 2 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.BUILD_LAMBDA_4GB
: Use up to 4 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.BUILD_LAMBDA_8GB
: Use up to 8 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.BUILD_LAMBDA_10GB
: Use up to 10 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.
If you use
BUILD_GENERAL1_SMALL
:- For environment type
LINUX_CONTAINER
, you can use up to 4 GiB memory and 2 vCPUs for builds. - For environment type
LINUX_GPU_CONTAINER
, you can use up to 16 GiB memory, 4 vCPUs, and 1 NVIDIA A10G Tensor Core GPU for builds. - For environment type
ARM_CONTAINER
, you can use up to 4 GiB memory and 2 vCPUs on ARM-based processors for builds.
If you use
BUILD_GENERAL1_LARGE
:- For environment type
LINUX_CONTAINER
, you can use up to 16 GiB memory and 8 vCPUs for builds. - For environment type
LINUX_GPU_CONTAINER
, you can use up to 255 GiB memory, 32 vCPUs, and 4 NVIDIA Tesla V100 GPUs for builds. - For environment type
ARM_CONTAINER
, you can use up to 16 GiB memory and 8 vCPUs on ARM-based processors for builds.
For more information, see On-demand environment types in the AWS CodeBuild User Guide.
- environment_
type FleetEnvironment Type The environment type of the compute fleet.
- The environment type
ARM_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), Asia Pacific (Mumbai), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), EU (Frankfurt), and South America (São Paulo). - The environment type
ARM_EC2
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), South America (São Paulo), and Asia Pacific (Mumbai). - The environment type
LINUX_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), South America (São Paulo), and Asia Pacific (Mumbai). - The environment type
LINUX_EC2
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), South America (São Paulo), and Asia Pacific (Mumbai). - The environment type
LINUX_GPU_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), and Asia Pacific (Sydney). - The environment type
MAC_ARM
is available only in regions US East (Ohio), US East (N. Virginia), US West (Oregon), Europe (Frankfurt), and Asia Pacific (Sydney). - The environment type
WINDOWS_EC2
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), South America (São Paulo), and Asia Pacific (Mumbai). - The environment type
WINDOWS_SERVER_2019_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Sydney), Asia Pacific (Tokyo), Asia Pacific (Mumbai) and EU (Ireland). - The environment type
WINDOWS_SERVER_2022_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Sydney), Asia Pacific (Singapore), Asia Pacific (Tokyo), South America (São Paulo) and Asia Pacific (Mumbai).
For more information, see Build environment compute types in the AWS CodeBuild user guide .
- The environment type
- fleet_
proxy_ Fleetconfiguration Proxy Configuration Args - Information about the proxy configurations that apply network access control to your reserved capacity instances.
- fleet_
service_ strrole - The service role associated with the compute fleet. For more information, see Allow a user to add a permission policy for a fleet service role in the AWS CodeBuild User Guide .
- fleet_
vpc_ Fleetconfig Vpc Config Args - Information about the VPC configuration that AWS CodeBuild accesses.
- image_
id str - The Amazon Machine Image (AMI) of the compute fleet.
- name str
- The name of the compute fleet.
- overflow_
behavior FleetOverflow Behavior The compute fleet overflow behavior.
- For overflow behavior
QUEUE
, your overflow builds need to wait on the existing fleet instance to become available. - For overflow behavior
ON_DEMAND
, your overflow builds run on CodeBuild on-demand.
If you choose to set your overflow behavior to on-demand while creating a VPC-connected fleet, make sure that you add the required VPC permissions to your project service role. For more information, see Example policy statement to allow CodeBuild access to AWS services required to create a VPC network interface .
- For overflow behavior
- scaling_
configuration FleetScaling Configuration Input Args - The scaling configuration of the compute fleet.
- Sequence[Tag
Args] A list of tag key and value pairs associated with this compute fleet.
These tags are available for use by AWS services that support AWS CodeBuild compute fleet tags.
- base
Capacity Number - The initial number of machines allocated to the compute fleet, which defines the number of builds that can run in parallel.
- compute
Configuration Property Map - The compute configuration of the compute fleet. This is only required if
computeType
is set toATTRIBUTE_BASED_COMPUTE
. - compute
Type "BUILD_GENERAL1_SMALL" | "BUILD_GENERAL1_MEDIUM" | "BUILD_GENERAL1_LARGE" | "BUILD_GENERAL1_XLARGE" | "BUILD_GENERAL1_2XLARGE" | "ATTRIBUTE_BASED_COMPUTE" Information about the compute resources the compute fleet uses. Available values include:
ATTRIBUTE_BASED_COMPUTE
: Specify the amount of vCPUs, memory, disk space, and the type of machine.
If you use
ATTRIBUTE_BASED_COMPUTE
, you must define your attributes by usingcomputeConfiguration
. AWS CodeBuild will select the cheapest instance that satisfies your specified attributes. For more information, see Reserved capacity environment types in the AWS CodeBuild User Guide .BUILD_GENERAL1_SMALL
: Use up to 4 GiB memory and 2 vCPUs for builds.BUILD_GENERAL1_MEDIUM
: Use up to 8 GiB memory and 4 vCPUs for builds.BUILD_GENERAL1_LARGE
: Use up to 16 GiB memory and 8 vCPUs for builds, depending on your environment type.BUILD_GENERAL1_XLARGE
: Use up to 72 GiB memory and 36 vCPUs for builds, depending on your environment type.BUILD_GENERAL1_2XLARGE
: Use up to 144 GiB memory, 72 vCPUs, and 824 GB of SSD storage for builds. This compute type supports Docker images up to 100 GB uncompressed.BUILD_LAMBDA_1GB
: Use up to 1 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.BUILD_LAMBDA_2GB
: Use up to 2 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.BUILD_LAMBDA_4GB
: Use up to 4 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.BUILD_LAMBDA_8GB
: Use up to 8 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.BUILD_LAMBDA_10GB
: Use up to 10 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.
If you use
BUILD_GENERAL1_SMALL
:- For environment type
LINUX_CONTAINER
, you can use up to 4 GiB memory and 2 vCPUs for builds. - For environment type
LINUX_GPU_CONTAINER
, you can use up to 16 GiB memory, 4 vCPUs, and 1 NVIDIA A10G Tensor Core GPU for builds. - For environment type
ARM_CONTAINER
, you can use up to 4 GiB memory and 2 vCPUs on ARM-based processors for builds.
If you use
BUILD_GENERAL1_LARGE
:- For environment type
LINUX_CONTAINER
, you can use up to 16 GiB memory and 8 vCPUs for builds. - For environment type
LINUX_GPU_CONTAINER
, you can use up to 255 GiB memory, 32 vCPUs, and 4 NVIDIA Tesla V100 GPUs for builds. - For environment type
ARM_CONTAINER
, you can use up to 16 GiB memory and 8 vCPUs on ARM-based processors for builds.
For more information, see On-demand environment types in the AWS CodeBuild User Guide.
- environment
Type "WINDOWS_SERVER_2019_CONTAINER" | "WINDOWS_SERVER_2022_CONTAINER" | "LINUX_CONTAINER" | "LINUX_GPU_CONTAINER" | "ARM_CONTAINER" | "MAC_ARM" The environment type of the compute fleet.
- The environment type
ARM_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), Asia Pacific (Mumbai), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), EU (Frankfurt), and South America (São Paulo). - The environment type
ARM_EC2
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), South America (São Paulo), and Asia Pacific (Mumbai). - The environment type
LINUX_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), South America (São Paulo), and Asia Pacific (Mumbai). - The environment type
LINUX_EC2
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), South America (São Paulo), and Asia Pacific (Mumbai). - The environment type
LINUX_GPU_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), and Asia Pacific (Sydney). - The environment type
MAC_ARM
is available only in regions US East (Ohio), US East (N. Virginia), US West (Oregon), Europe (Frankfurt), and Asia Pacific (Sydney). - The environment type
WINDOWS_EC2
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), South America (São Paulo), and Asia Pacific (Mumbai). - The environment type
WINDOWS_SERVER_2019_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Sydney), Asia Pacific (Tokyo), Asia Pacific (Mumbai) and EU (Ireland). - The environment type
WINDOWS_SERVER_2022_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Sydney), Asia Pacific (Singapore), Asia Pacific (Tokyo), South America (São Paulo) and Asia Pacific (Mumbai).
For more information, see Build environment compute types in the AWS CodeBuild user guide .
- The environment type
- fleet
Proxy Property MapConfiguration - Information about the proxy configurations that apply network access control to your reserved capacity instances.
- fleet
Service StringRole - The service role associated with the compute fleet. For more information, see Allow a user to add a permission policy for a fleet service role in the AWS CodeBuild User Guide .
- fleet
Vpc Property MapConfig - Information about the VPC configuration that AWS CodeBuild accesses.
- image
Id String - The Amazon Machine Image (AMI) of the compute fleet.
- name String
- The name of the compute fleet.
- overflow
Behavior "QUEUE" | "ON_DEMAND" The compute fleet overflow behavior.
- For overflow behavior
QUEUE
, your overflow builds need to wait on the existing fleet instance to become available. - For overflow behavior
ON_DEMAND
, your overflow builds run on CodeBuild on-demand.
If you choose to set your overflow behavior to on-demand while creating a VPC-connected fleet, make sure that you add the required VPC permissions to your project service role. For more information, see Example policy statement to allow CodeBuild access to AWS services required to create a VPC network interface .
- For overflow behavior
- scaling
Configuration Property Map - The scaling configuration of the compute fleet.
- List<Property Map>
A list of tag key and value pairs associated with this compute fleet.
These tags are available for use by AWS services that support AWS CodeBuild compute fleet tags.
Outputs
All input properties are implicitly available as output properties. Additionally, the Fleet resource produces the following output properties:
Supporting Types
FleetComputeConfiguration, FleetComputeConfigurationArgs
- Disk int
- The amount of disk space of the instance type included in your fleet.
- Machine
Type Pulumi.Aws Native. Code Build. Fleet Compute Configurationmachine Type - The machine type of the instance type included in your fleet.
- Memory int
- The amount of memory of the instance type included in your fleet.
- VCpu int
- The number of vCPUs of the instance type included in your fleet.
- Disk int
- The amount of disk space of the instance type included in your fleet.
- Machine
Type FleetCompute Configurationmachine Type - The machine type of the instance type included in your fleet.
- Memory int
- The amount of memory of the instance type included in your fleet.
- VCpu int
- The number of vCPUs of the instance type included in your fleet.
- disk Integer
- The amount of disk space of the instance type included in your fleet.
- machine
Type FleetCompute Configurationmachine Type - The machine type of the instance type included in your fleet.
- memory Integer
- The amount of memory of the instance type included in your fleet.
- v
Cpu Integer - The number of vCPUs of the instance type included in your fleet.
- disk number
- The amount of disk space of the instance type included in your fleet.
- machine
Type FleetCompute Configurationmachine Type - The machine type of the instance type included in your fleet.
- memory number
- The amount of memory of the instance type included in your fleet.
- v
Cpu number - The number of vCPUs of the instance type included in your fleet.
- disk int
- The amount of disk space of the instance type included in your fleet.
- machine_
type FleetCompute Configurationmachine Type - The machine type of the instance type included in your fleet.
- memory int
- The amount of memory of the instance type included in your fleet.
- v_
cpu int - The number of vCPUs of the instance type included in your fleet.
- disk Number
- The amount of disk space of the instance type included in your fleet.
- machine
Type "GENERAL" | "NVME" - The machine type of the instance type included in your fleet.
- memory Number
- The amount of memory of the instance type included in your fleet.
- v
Cpu Number - The number of vCPUs of the instance type included in your fleet.
FleetComputeConfigurationmachineType, FleetComputeConfigurationmachineTypeArgs
- General
- GENERAL
- Nvme
- NVME
- Fleet
Compute Configurationmachine Type General - GENERAL
- Fleet
Compute Configurationmachine Type Nvme - NVME
- General
- GENERAL
- Nvme
- NVME
- General
- GENERAL
- Nvme
- NVME
- GENERAL
- GENERAL
- NVME
- NVME
- "GENERAL"
- GENERAL
- "NVME"
- NVME
FleetComputeType, FleetComputeTypeArgs
- Build
General1Small - BUILD_GENERAL1_SMALL
- Build
General1Medium - BUILD_GENERAL1_MEDIUM
- Build
General1Large - BUILD_GENERAL1_LARGE
- Build
General1Xlarge - BUILD_GENERAL1_XLARGE
- Build
General12xlarge - BUILD_GENERAL1_2XLARGE
- Attribute
Based Compute - ATTRIBUTE_BASED_COMPUTE
- Fleet
Compute Type Build General1Small - BUILD_GENERAL1_SMALL
- Fleet
Compute Type Build General1Medium - BUILD_GENERAL1_MEDIUM
- Fleet
Compute Type Build General1Large - BUILD_GENERAL1_LARGE
- Fleet
Compute Type Build General1Xlarge - BUILD_GENERAL1_XLARGE
- Fleet
Compute Type Build General12xlarge - BUILD_GENERAL1_2XLARGE
- Fleet
Compute Type Attribute Based Compute - ATTRIBUTE_BASED_COMPUTE
- Build
General1Small - BUILD_GENERAL1_SMALL
- Build
General1Medium - BUILD_GENERAL1_MEDIUM
- Build
General1Large - BUILD_GENERAL1_LARGE
- Build
General1Xlarge - BUILD_GENERAL1_XLARGE
- Build
General12xlarge - BUILD_GENERAL1_2XLARGE
- Attribute
Based Compute - ATTRIBUTE_BASED_COMPUTE
- Build
General1Small - BUILD_GENERAL1_SMALL
- Build
General1Medium - BUILD_GENERAL1_MEDIUM
- Build
General1Large - BUILD_GENERAL1_LARGE
- Build
General1Xlarge - BUILD_GENERAL1_XLARGE
- Build
General12xlarge - BUILD_GENERAL1_2XLARGE
- Attribute
Based Compute - ATTRIBUTE_BASED_COMPUTE
- BUILD_GENERAL1_SMALL
- BUILD_GENERAL1_SMALL
- BUILD_GENERAL1_MEDIUM
- BUILD_GENERAL1_MEDIUM
- BUILD_GENERAL1_LARGE
- BUILD_GENERAL1_LARGE
- BUILD_GENERAL1_XLARGE
- BUILD_GENERAL1_XLARGE
- BUILD_GENERAL12XLARGE
- BUILD_GENERAL1_2XLARGE
- ATTRIBUTE_BASED_COMPUTE
- ATTRIBUTE_BASED_COMPUTE
- "BUILD_GENERAL1_SMALL"
- BUILD_GENERAL1_SMALL
- "BUILD_GENERAL1_MEDIUM"
- BUILD_GENERAL1_MEDIUM
- "BUILD_GENERAL1_LARGE"
- BUILD_GENERAL1_LARGE
- "BUILD_GENERAL1_XLARGE"
- BUILD_GENERAL1_XLARGE
- "BUILD_GENERAL1_2XLARGE"
- BUILD_GENERAL1_2XLARGE
- "ATTRIBUTE_BASED_COMPUTE"
- ATTRIBUTE_BASED_COMPUTE
FleetEnvironmentType, FleetEnvironmentTypeArgs
- Windows
Server2019Container - WINDOWS_SERVER_2019_CONTAINER
- Windows
Server2022Container - WINDOWS_SERVER_2022_CONTAINER
- Linux
Container - LINUX_CONTAINER
- Linux
Gpu Container - LINUX_GPU_CONTAINER
- Arm
Container - ARM_CONTAINER
- Mac
Arm - MAC_ARM
- Fleet
Environment Type Windows Server2019Container - WINDOWS_SERVER_2019_CONTAINER
- Fleet
Environment Type Windows Server2022Container - WINDOWS_SERVER_2022_CONTAINER
- Fleet
Environment Type Linux Container - LINUX_CONTAINER
- Fleet
Environment Type Linux Gpu Container - LINUX_GPU_CONTAINER
- Fleet
Environment Type Arm Container - ARM_CONTAINER
- Fleet
Environment Type Mac Arm - MAC_ARM
- Windows
Server2019Container - WINDOWS_SERVER_2019_CONTAINER
- Windows
Server2022Container - WINDOWS_SERVER_2022_CONTAINER
- Linux
Container - LINUX_CONTAINER
- Linux
Gpu Container - LINUX_GPU_CONTAINER
- Arm
Container - ARM_CONTAINER
- Mac
Arm - MAC_ARM
- Windows
Server2019Container - WINDOWS_SERVER_2019_CONTAINER
- Windows
Server2022Container - WINDOWS_SERVER_2022_CONTAINER
- Linux
Container - LINUX_CONTAINER
- Linux
Gpu Container - LINUX_GPU_CONTAINER
- Arm
Container - ARM_CONTAINER
- Mac
Arm - MAC_ARM
- WINDOWS_SERVER2019_CONTAINER
- WINDOWS_SERVER_2019_CONTAINER
- WINDOWS_SERVER2022_CONTAINER
- WINDOWS_SERVER_2022_CONTAINER
- LINUX_CONTAINER
- LINUX_CONTAINER
- LINUX_GPU_CONTAINER
- LINUX_GPU_CONTAINER
- ARM_CONTAINER
- ARM_CONTAINER
- MAC_ARM
- MAC_ARM
- "WINDOWS_SERVER_2019_CONTAINER"
- WINDOWS_SERVER_2019_CONTAINER
- "WINDOWS_SERVER_2022_CONTAINER"
- WINDOWS_SERVER_2022_CONTAINER
- "LINUX_CONTAINER"
- LINUX_CONTAINER
- "LINUX_GPU_CONTAINER"
- LINUX_GPU_CONTAINER
- "ARM_CONTAINER"
- ARM_CONTAINER
- "MAC_ARM"
- MAC_ARM
FleetOverflowBehavior, FleetOverflowBehaviorArgs
- Queue
- QUEUE
- On
Demand - ON_DEMAND
- Fleet
Overflow Behavior Queue - QUEUE
- Fleet
Overflow Behavior On Demand - ON_DEMAND
- Queue
- QUEUE
- On
Demand - ON_DEMAND
- Queue
- QUEUE
- On
Demand - ON_DEMAND
- QUEUE
- QUEUE
- ON_DEMAND
- ON_DEMAND
- "QUEUE"
- QUEUE
- "ON_DEMAND"
- ON_DEMAND
FleetProxyConfiguration, FleetProxyConfigurationArgs
- Default
Behavior Pulumi.Aws Native. Code Build. Fleet Proxy Configuration Default Behavior - The default behavior of outgoing traffic.
- Ordered
Proxy List<Pulumi.Rules Aws Native. Code Build. Inputs. Fleet Proxy Rule> - An array of
FleetProxyRule
objects that represent the specified destination domains or IPs to allow or deny network access control to.
- Default
Behavior FleetProxy Configuration Default Behavior - The default behavior of outgoing traffic.
- Ordered
Proxy []FleetRules Proxy Rule - An array of
FleetProxyRule
objects that represent the specified destination domains or IPs to allow or deny network access control to.
- default
Behavior FleetProxy Configuration Default Behavior - The default behavior of outgoing traffic.
- ordered
Proxy List<FleetRules Proxy Rule> - An array of
FleetProxyRule
objects that represent the specified destination domains or IPs to allow or deny network access control to.
- default
Behavior FleetProxy Configuration Default Behavior - The default behavior of outgoing traffic.
- ordered
Proxy FleetRules Proxy Rule[] - An array of
FleetProxyRule
objects that represent the specified destination domains or IPs to allow or deny network access control to.
- default_
behavior FleetProxy Configuration Default Behavior - The default behavior of outgoing traffic.
- ordered_
proxy_ Sequence[Fleetrules Proxy Rule] - An array of
FleetProxyRule
objects that represent the specified destination domains or IPs to allow or deny network access control to.
- default
Behavior "ALLOW_ALL" | "DENY_ALL" - The default behavior of outgoing traffic.
- ordered
Proxy List<Property Map>Rules - An array of
FleetProxyRule
objects that represent the specified destination domains or IPs to allow or deny network access control to.
FleetProxyConfigurationDefaultBehavior, FleetProxyConfigurationDefaultBehaviorArgs
- Allow
All - ALLOW_ALL
- Deny
All - DENY_ALL
- Fleet
Proxy Configuration Default Behavior Allow All - ALLOW_ALL
- Fleet
Proxy Configuration Default Behavior Deny All - DENY_ALL
- Allow
All - ALLOW_ALL
- Deny
All - DENY_ALL
- Allow
All - ALLOW_ALL
- Deny
All - DENY_ALL
- ALLOW_ALL
- ALLOW_ALL
- DENY_ALL
- DENY_ALL
- "ALLOW_ALL"
- ALLOW_ALL
- "DENY_ALL"
- DENY_ALL
FleetProxyRule, FleetProxyRuleArgs
- Effect
Pulumi.
Aws Native. Code Build. Fleet Proxy Rule Effect - The behavior of the proxy rule.
- Entities List<string>
- The destination of the proxy rule.
- Type
Pulumi.
Aws Native. Code Build. Fleet Proxy Rule Type - The type of proxy rule.
- Effect
Fleet
Proxy Rule Effect - The behavior of the proxy rule.
- Entities []string
- The destination of the proxy rule.
- Type
Fleet
Proxy Rule Type - The type of proxy rule.
- effect
Fleet
Proxy Rule Effect - The behavior of the proxy rule.
- entities List<String>
- The destination of the proxy rule.
- type
Fleet
Proxy Rule Type - The type of proxy rule.
- effect
Fleet
Proxy Rule Effect - The behavior of the proxy rule.
- entities string[]
- The destination of the proxy rule.
- type
Fleet
Proxy Rule Type - The type of proxy rule.
- effect
Fleet
Proxy Rule Effect - The behavior of the proxy rule.
- entities Sequence[str]
- The destination of the proxy rule.
- type
Fleet
Proxy Rule Type - The type of proxy rule.
- effect "ALLOW" | "DENY"
- The behavior of the proxy rule.
- entities List<String>
- The destination of the proxy rule.
- type "DOMAIN" | "IP"
- The type of proxy rule.
FleetProxyRuleEffect, FleetProxyRuleEffectArgs
- Allow
- ALLOW
- Deny
- DENY
- Fleet
Proxy Rule Effect Allow - ALLOW
- Fleet
Proxy Rule Effect Deny - DENY
- Allow
- ALLOW
- Deny
- DENY
- Allow
- ALLOW
- Deny
- DENY
- ALLOW
- ALLOW
- DENY
- DENY
- "ALLOW"
- ALLOW
- "DENY"
- DENY
FleetProxyRuleType, FleetProxyRuleTypeArgs
- Domain
- DOMAIN
- Ip
- IP
- Fleet
Proxy Rule Type Domain - DOMAIN
- Fleet
Proxy Rule Type Ip - IP
- Domain
- DOMAIN
- Ip
- IP
- Domain
- DOMAIN
- Ip
- IP
- DOMAIN
- DOMAIN
- IP
- IP
- "DOMAIN"
- DOMAIN
- "IP"
- IP
FleetScalingConfigurationInput, FleetScalingConfigurationInputArgs
- Max
Capacity int - The maximum number of instances in the fleet when auto-scaling.
- Scaling
Type Pulumi.Aws Native. Code Build. Fleet Scaling Configuration Input Scaling Type - The scaling type for a compute fleet.
- Target
Tracking List<Pulumi.Scaling Configs Aws Native. Code Build. Inputs. Fleet Target Tracking Scaling Configuration> - A list of
TargetTrackingScalingConfiguration
objects.
- Max
Capacity int - The maximum number of instances in the fleet when auto-scaling.
- Scaling
Type FleetScaling Configuration Input Scaling Type - The scaling type for a compute fleet.
- Target
Tracking []FleetScaling Configs Target Tracking Scaling Configuration - A list of
TargetTrackingScalingConfiguration
objects.
- max
Capacity Integer - The maximum number of instances in the fleet when auto-scaling.
- scaling
Type FleetScaling Configuration Input Scaling Type - The scaling type for a compute fleet.
- target
Tracking List<FleetScaling Configs Target Tracking Scaling Configuration> - A list of
TargetTrackingScalingConfiguration
objects.
- max
Capacity number - The maximum number of instances in the fleet when auto-scaling.
- scaling
Type FleetScaling Configuration Input Scaling Type - The scaling type for a compute fleet.
- target
Tracking FleetScaling Configs Target Tracking Scaling Configuration[] - A list of
TargetTrackingScalingConfiguration
objects.
- max_
capacity int - The maximum number of instances in the fleet when auto-scaling.
- scaling_
type FleetScaling Configuration Input Scaling Type - The scaling type for a compute fleet.
- target_
tracking_ Sequence[Fleetscaling_ configs Target Tracking Scaling Configuration] - A list of
TargetTrackingScalingConfiguration
objects.
- max
Capacity Number - The maximum number of instances in the fleet when auto-scaling.
- scaling
Type "TARGET_TRACKING_SCALING" - The scaling type for a compute fleet.
- target
Tracking List<Property Map>Scaling Configs - A list of
TargetTrackingScalingConfiguration
objects.
FleetScalingConfigurationInputScalingType, FleetScalingConfigurationInputScalingTypeArgs
- Target
Tracking Scaling - TARGET_TRACKING_SCALING
- Fleet
Scaling Configuration Input Scaling Type Target Tracking Scaling - TARGET_TRACKING_SCALING
- Target
Tracking Scaling - TARGET_TRACKING_SCALING
- Target
Tracking Scaling - TARGET_TRACKING_SCALING
- TARGET_TRACKING_SCALING
- TARGET_TRACKING_SCALING
- "TARGET_TRACKING_SCALING"
- TARGET_TRACKING_SCALING
FleetTargetTrackingScalingConfiguration, FleetTargetTrackingScalingConfigurationArgs
- Metric
Type Pulumi.Aws Native. Code Build. Fleet Target Tracking Scaling Configuration Metric Type - The metric type to determine auto-scaling.
- Target
Value double - The value of
metricType
when to start scaling.
- Metric
Type FleetTarget Tracking Scaling Configuration Metric Type - The metric type to determine auto-scaling.
- Target
Value float64 - The value of
metricType
when to start scaling.
- metric
Type FleetTarget Tracking Scaling Configuration Metric Type - The metric type to determine auto-scaling.
- target
Value Double - The value of
metricType
when to start scaling.
- metric
Type FleetTarget Tracking Scaling Configuration Metric Type - The metric type to determine auto-scaling.
- target
Value number - The value of
metricType
when to start scaling.
- metric_
type FleetTarget Tracking Scaling Configuration Metric Type - The metric type to determine auto-scaling.
- target_
value float - The value of
metricType
when to start scaling.
- metric
Type "FLEET_UTILIZATION_RATE" - The metric type to determine auto-scaling.
- target
Value Number - The value of
metricType
when to start scaling.
FleetTargetTrackingScalingConfigurationMetricType, FleetTargetTrackingScalingConfigurationMetricTypeArgs
- Fleet
Utilization Rate - FLEET_UTILIZATION_RATE
- Fleet
Target Tracking Scaling Configuration Metric Type Fleet Utilization Rate - FLEET_UTILIZATION_RATE
- Fleet
Utilization Rate - FLEET_UTILIZATION_RATE
- Fleet
Utilization Rate - FLEET_UTILIZATION_RATE
- FLEET_UTILIZATION_RATE
- FLEET_UTILIZATION_RATE
- "FLEET_UTILIZATION_RATE"
- FLEET_UTILIZATION_RATE
FleetVpcConfig, FleetVpcConfigArgs
- Security
Group List<string>Ids - A list of one or more security groups IDs in your Amazon VPC.
- Subnets List<string>
- A list of one or more subnet IDs in your Amazon VPC.
- Vpc
Id string - The ID of the Amazon VPC.
- Security
Group []stringIds - A list of one or more security groups IDs in your Amazon VPC.
- Subnets []string
- A list of one or more subnet IDs in your Amazon VPC.
- Vpc
Id string - The ID of the Amazon VPC.
- security
Group List<String>Ids - A list of one or more security groups IDs in your Amazon VPC.
- subnets List<String>
- A list of one or more subnet IDs in your Amazon VPC.
- vpc
Id String - The ID of the Amazon VPC.
- security
Group string[]Ids - A list of one or more security groups IDs in your Amazon VPC.
- subnets string[]
- A list of one or more subnet IDs in your Amazon VPC.
- vpc
Id string - The ID of the Amazon VPC.
- security_
group_ Sequence[str]ids - A list of one or more security groups IDs in your Amazon VPC.
- subnets Sequence[str]
- A list of one or more subnet IDs in your Amazon VPC.
- vpc_
id str - The ID of the Amazon VPC.
- security
Group List<String>Ids - A list of one or more security groups IDs in your Amazon VPC.
- subnets List<String>
- A list of one or more subnet IDs in your Amazon VPC.
- vpc
Id String - The ID of the Amazon VPC.
Tag, TagArgs
Package Details
- Repository
- AWS Native pulumi/pulumi-aws-native
- License
- Apache-2.0
We recommend new projects start with resources from the AWS provider.