create_express_gateway_service¶
Operation¶
create_express_gateway_service
async
¶
create_express_gateway_service(request: CreateExpressGatewayServiceInput | CreateExpressGatewayServiceInputDict, /, *, plugins: list[Plugin] | None = None) -> CreateExpressGatewayServiceOutput
create_express_gateway_service(*, plugins: list[Plugin] | None = None, **kwargs: Unpack[CreateExpressGatewayServiceInputDict]) -> CreateExpressGatewayServiceOutput
Creates an Express service that simplifies deploying containerized web applications on Amazon ECS with managed Amazon Web Services infrastructure. This operation provisions and configures Application Load Balancers, target groups, security groups, and auto-scaling policies automatically.
Specify a primary container configuration with your application image and basic settings. Amazon ECS creates the necessary Amazon Web Services resources for traffic distribution, health monitoring, network access control, and capacity management.
Provide an execution role for task operations and an infrastructure role for managing Amazon Web Services resources on your behalf.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
plugins
|
list[Plugin] | None
|
A list of callables that modify the configuration dynamically. Changes made by these plugins only apply for the duration of the operation execution and will not affect any other operation invocations. |
None
|
Returns:
| Type | Description |
|---|---|
CreateExpressGatewayServiceOutput
|
An instance of |
Input¶
Pass the input fields as keyword arguments, or pass a model or dictionary as the first positional argument. Pass plugins separately as a keyword argument.
Model¶
CreateExpressGatewayServiceInput
dataclass
¶
Bases: _SerdeShape
Dataclass for CreateExpressGatewayServiceInput structure.
Attributes¶
cluster
class-attribute
instance-attribute
¶
cluster: str | None = ...
The short name or full Amazon Resource Name (ARN) of the cluster on
which to create the Express service. If you do not specify a cluster,
the default cluster is assumed.
cpu
class-attribute
instance-attribute
¶
cpu: str | None = ...
The number of CPU units used by the task. This parameter determines the CPU allocation for each task in the Express service. The default value for an Express service is 256 (.25 vCPU).
cpu_architecture
class-attribute
instance-attribute
¶
cpu_architecture: str | None = ...
The CPU architecture that the task runs on. If you don't specify a
value, the default is X86_64.
Valid values:
-
X86_64- The x86 64-bit architecture. -
ARM64- The 64-bit ARM architecture.
Ensure that the container image you specify supports the architecture
you choose. The operating system family for an Express service is always
LINUX.
You can't specify cpuArchitecture together with taskDefinitionArn.
execution_role_arn
class-attribute
instance-attribute
¶
execution_role_arn: str | None = ...
The Amazon Resource Name (ARN) of the task execution role that grants the Amazon ECS container agent permission to make Amazon Web Services API calls on your behalf. This role is required for Amazon ECS to pull container images from Amazon ECR, send container logs to Amazon CloudWatch Logs, and retrieve sensitive data from Amazon Web Services Systems Manager Parameter Store or Amazon Web Services Secrets Manager.
The execution role must include the AmazonECSTaskExecutionRolePolicy
managed policy or equivalent permissions. For Express services, this
role is used during task startup and runtime for container management
operations.
health_check_path
class-attribute
instance-attribute
¶
health_check_path: str | None = ...
The path on the container that the Application Load Balancer uses for health checks. This should be a valid HTTP endpoint that returns a successful response (HTTP 200) when the application is healthy.
If not specified, the default health check path is /ping. The health
check path must start with a forward slash and can include query
parameters. Examples: /health, /api/status, /ping?format=json.
infrastructure_role_arn
class-attribute
instance-attribute
¶
infrastructure_role_arn: str | None = ...
The Amazon Resource Name (ARN) of the infrastructure role that grants Amazon ECS permission to create and manage Amazon Web Services resources on your behalf for the Express service. This role is used to provision and manage Application Load Balancers, target groups, security groups, auto-scaling policies, and other Amazon Web Services infrastructure components.
The infrastructure role must include permissions for Elastic Load Balancing, Application Auto Scaling, Amazon EC2 (for security groups), and other services required for managed infrastructure. This role is only used during Express service creation, updates, and deletion operations.
memory
class-attribute
instance-attribute
¶
memory: str | None = ...
The amount of memory (in MiB) used by the task. This parameter determines the memory allocation for each task in the Express service. The default value for an express service is 512 MiB.
network_configuration
class-attribute
instance-attribute
¶
network_configuration: ExpressGatewayServiceNetworkConfiguration | None = ...
The network configuration for the Express service tasks. This specifies the VPC subnets and security groups for the tasks.
For Express services, you can specify custom security groups and subnets. If not provided, Amazon ECS will use the default VPC configuration and create appropriate security groups automatically. The network configuration determines how your service integrates with your VPC and what network access it has.
primary_container
class-attribute
instance-attribute
¶
primary_container: ExpressGatewayContainer | None = ...
The primary container configuration for the Express service. This defines the main application container that will receive traffic from the Application Load Balancer.
The primary container must specify at minimum a container image. You can also configure the container port (defaults to 80), logging configuration, environment variables, secrets, and startup commands. The container image can be from Amazon ECR, Docker Hub, or any other container registry accessible to your execution role.
scaling_target
class-attribute
instance-attribute
¶
scaling_target: ExpressGatewayScalingTarget | None = ...
The auto-scaling configuration for the Express service. This defines how the service automatically adjusts the number of running tasks based on demand.
You can specify the minimum and maximum number of tasks, the scaling metric (CPU utilization, memory utilization, or request count per target), and the target value for the metric. If not specified, the default target value for an Express service is 60.
service_name
class-attribute
instance-attribute
¶
service_name: str | None = ...
The name of the Express service. This name must be unique within the specified cluster and can contain up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens. The name is used to identify the service in the Amazon ECS console and API operations.
If you don't specify a service name, Amazon ECS generates a unique name for the service. The service name becomes part of the service ARN and cannot be changed after the service is created.
tags
class-attribute
instance-attribute
¶
The metadata that you apply to the Express service to help categorize and organize it. Each tag consists of a key and an optional value. You can apply up to 50 tags to a service.
task_definition_arn
class-attribute
instance-attribute
¶
task_definition_arn: str | None = ...
The Amazon Resource Name (ARN) of a task definition to use to create the Express Gateway service. This allows you to manage your own task definition, giving you more control over the service configuration such as adding sidecar containers.
The task definition must have a container named Main with a single TCP
port mapping that includes a container port and port name. The task
definition must also have FARGATE compatibility.
If you provide a task definition ARN, you cannot also specify
primaryContainer, executionRoleArn, taskRoleArn, cpu, memory,
or cpuArchitecture.
task_role_arn
class-attribute
instance-attribute
¶
task_role_arn: str | None = ...
The Amazon Resource Name (ARN) of the IAM role that containers in this task can assume. This role allows your application code to access other Amazon Web Services services securely.
The task role is different from the execution role. While the execution role is used by the Amazon ECS agent to set up the task, the task role is used by your application code running inside the container to make Amazon Web Services API calls. If your application doesn't need to access Amazon Web Services services, you can omit this parameter.
Dictionaries¶
CreateExpressGatewayServiceInputDict
¶
Bases: TypedDict
Dictionary form of CreateExpressGatewayServiceInput.
Attributes¶
cluster
instance-attribute
¶
cluster: str | None
The short name or full Amazon Resource Name (ARN) of the cluster on
which to create the Express service. If you do not specify a cluster,
the default cluster is assumed.
cpu
instance-attribute
¶
cpu: str | None
The number of CPU units used by the task. This parameter determines the CPU allocation for each task in the Express service. The default value for an Express service is 256 (.25 vCPU).
cpu_architecture
instance-attribute
¶
cpu_architecture: str | None
The CPU architecture that the task runs on. If you don't specify a
value, the default is X86_64.
Valid values:
-
X86_64- The x86 64-bit architecture. -
ARM64- The 64-bit ARM architecture.
Ensure that the container image you specify supports the architecture
you choose. The operating system family for an Express service is always
LINUX.
You can't specify cpuArchitecture together with taskDefinitionArn.
execution_role_arn
instance-attribute
¶
execution_role_arn: str | None
The Amazon Resource Name (ARN) of the task execution role that grants the Amazon ECS container agent permission to make Amazon Web Services API calls on your behalf. This role is required for Amazon ECS to pull container images from Amazon ECR, send container logs to Amazon CloudWatch Logs, and retrieve sensitive data from Amazon Web Services Systems Manager Parameter Store or Amazon Web Services Secrets Manager.
The execution role must include the AmazonECSTaskExecutionRolePolicy
managed policy or equivalent permissions. For Express services, this
role is used during task startup and runtime for container management
operations.
health_check_path
instance-attribute
¶
health_check_path: str | None
The path on the container that the Application Load Balancer uses for health checks. This should be a valid HTTP endpoint that returns a successful response (HTTP 200) when the application is healthy.
If not specified, the default health check path is /ping. The health
check path must start with a forward slash and can include query
parameters. Examples: /health, /api/status, /ping?format=json.
infrastructure_role_arn
instance-attribute
¶
The Amazon Resource Name (ARN) of the infrastructure role that grants Amazon ECS permission to create and manage Amazon Web Services resources on your behalf for the Express service. This role is used to provision and manage Application Load Balancers, target groups, security groups, auto-scaling policies, and other Amazon Web Services infrastructure components.
The infrastructure role must include permissions for Elastic Load Balancing, Application Auto Scaling, Amazon EC2 (for security groups), and other services required for managed infrastructure. This role is only used during Express service creation, updates, and deletion operations.
memory
instance-attribute
¶
memory: str | None
The amount of memory (in MiB) used by the task. This parameter determines the memory allocation for each task in the Express service. The default value for an express service is 512 MiB.
network_configuration
instance-attribute
¶
network_configuration: ExpressGatewayServiceNetworkConfiguration | ExpressGatewayServiceNetworkConfigurationDict | None
The network configuration for the Express service tasks. This specifies the VPC subnets and security groups for the tasks.
For Express services, you can specify custom security groups and subnets. If not provided, Amazon ECS will use the default VPC configuration and create appropriate security groups automatically. The network configuration determines how your service integrates with your VPC and what network access it has.
primary_container
instance-attribute
¶
primary_container: ExpressGatewayContainer | ExpressGatewayContainerDict | None
The primary container configuration for the Express service. This defines the main application container that will receive traffic from the Application Load Balancer.
The primary container must specify at minimum a container image. You can also configure the container port (defaults to 80), logging configuration, environment variables, secrets, and startup commands. The container image can be from Amazon ECR, Docker Hub, or any other container registry accessible to your execution role.
scaling_target
instance-attribute
¶
scaling_target: ExpressGatewayScalingTarget | ExpressGatewayScalingTargetDict | None
The auto-scaling configuration for the Express service. This defines how the service automatically adjusts the number of running tasks based on demand.
You can specify the minimum and maximum number of tasks, the scaling metric (CPU utilization, memory utilization, or request count per target), and the target value for the metric. If not specified, the default target value for an Express service is 60.
service_name
instance-attribute
¶
service_name: str | None
The name of the Express service. This name must be unique within the specified cluster and can contain up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens. The name is used to identify the service in the Amazon ECS console and API operations.
If you don't specify a service name, Amazon ECS generates a unique name for the service. The service name becomes part of the service ARN and cannot be changed after the service is created.
tags
instance-attribute
¶
The metadata that you apply to the Express service to help categorize and organize it. Each tag consists of a key and an optional value. You can apply up to 50 tags to a service.
task_definition_arn
instance-attribute
¶
task_definition_arn: str | None
The Amazon Resource Name (ARN) of a task definition to use to create the Express Gateway service. This allows you to manage your own task definition, giving you more control over the service configuration such as adding sidecar containers.
The task definition must have a container named Main with a single TCP
port mapping that includes a container port and port name. The task
definition must also have FARGATE compatibility.
If you provide a task definition ARN, you cannot also specify
primaryContainer, executionRoleArn, taskRoleArn, cpu, memory,
or cpuArchitecture.
task_role_arn
instance-attribute
¶
task_role_arn: str | None
The Amazon Resource Name (ARN) of the IAM role that containers in this task can assume. This role allows your application code to access other Amazon Web Services services securely.
The task role is different from the execution role. While the execution role is used by the Amazon ECS agent to set up the task, the task role is used by your application code running inside the container to make Amazon Web Services API calls. If your application doesn't need to access Amazon Web Services services, you can omit this parameter.
Output¶
CreateExpressGatewayServiceOutput
dataclass
¶
Bases: _SerdeShape
Dataclass for CreateExpressGatewayServiceOutput structure.
Attributes¶
response_metadata
class-attribute
instance-attribute
¶
Metadata about the response that produced this output. Use this to recover the request identifiers a service's support team needs in order to investigate a call. Members of the metadata are individually optional.
service
class-attribute
instance-attribute
¶
service: ECSExpressGatewayService | None = ...
The full description of your Express service following the create operation.