Amazon ECS Client
Amazon Elastic Container Service (Amazon ECS) is a fully managed container orchestration service that helps you deploy, manage, and scale containerized applications.
You can find more information about ECS at the Amazon ECS website.
| The Amazon ECS extension is based on AWS Java SDK 2.x. It’s a major rewrite of the 1.x code base that offers two programming models (Blocking & Async). |
The Quarkus extension supports two programming models:
-
Blocking access using URL Connection HTTP client (by default), the Apache HTTP Client or the AWS CRT-based HTTP client
-
Asynchronous programming based on JDK’s
CompletableFutureobjects and the Netty HTTP client or the AWS CRT-based HTTP client
In this guide, we see how you can get your REST services to use Amazon ECS locally and on AWS.
Prerequisites
To complete this guide, you need:
-
JDK 21+ installed with
JAVA_HOMEconfigured appropriately -
an IDE
-
Apache Maven 3.8.1+
-
Docker, to run Amazon ECS locally with Dev Services and to run the tests
-
Optionally, GraalVM or Mandrel installed to build a native executable
No AWS account is required: Dev Services and the local Floci container provide everything you need. You only need an AWS account and the AWS Command Line Interface if you want to deploy to AWS.
Provision Amazon ECS locally via Dev Services
The easiest way to start working with Amazon ECS is to run a local instance using Dev Services. Dev Services starts a Floci container in dev and test modes, and configures the client to use it, so you don’t need an AWS account.
The container listens on a random port, so you never hard-code an endpoint.
It is labelled quarkus-dev-service-floci and shared between the Quarkus applications running in dev mode.
Refer to Dev Services for Amazon Services for the provider selection, the container configuration and the init scripts.
Dev Services does not check that the selected stack emulates Amazon ECS. If none of the supported stacks does, disable Dev Services with quarkus.ecs.devservices.enabled=false and use your AWS account or set endpoint-override.
|
Provision Amazon ECS locally manually
You can also set up a local version of Amazon ECS manually, first start a Floci container:
docker run --rm --name floci --publish 4566:4566 -d floci/floci:latest-compatThis starts a Floci instance that is accessible on port 4566. Floci exposes all the services it emulates on this single endpoint.
The latest-compat image ships the AWS CLI, already configured to target the local endpoint.
Run the provisioning commands of this guide inside the container, with docker exec floci aws ….
You do not need to install or configure the AWS CLI on your host.
You can check the region, the credentials and the endpoint used inside the container:
docker exec floci env | grep AWS_The CLI uses the region us-east-1, the credentials test / test, and the endpoint http://localhost:4566 seen from inside the container.
An application running on the host reaches Floci at http://localhost:4566; an application running in another container must use the container name, for example http://floci:4566, and the containers must share a Docker network.
Creating the Maven project
First, we need a new project. Create a new project with the following command:
mvn io.quarkus.platform:quarkus-maven-plugin:4.0.0.Beta1:create \
-DprojectGroupId=org.acme \
-DprojectArtifactId=amazon-ecs-quickstart \
-DclassName="org.acme.ecs.QuarkusEcsSyncResource" \
-Dpath="/sync" \
-Dextensions="rest-jackson,amazon-ecs"
cd amazon-ecs-quickstartThis command generates a Maven structure importing the Quarkus REST and Amazon ECS Client extensions.
After this, the amazon-ecs extension has been added to your pom.xml, along with quarkus-rest and quarkus-rest-jackson.
The Amazon ECS extensions are a component of the Quarkus platform, and the generated pom.xml already imports their BOM through it, which is the recommended setup.
Due to differing release schedules, the Quarkus platform may not include the latest Quarkus Amazon Services release.
If you need features from a newer release, replace the generated quarkus-amazon-services-bom import with the Quarkus Amazon Services BOM:
<dependency>
<groupId>io.quarkiverse.amazonservices</groupId>
<artifactId>quarkus-amazon-services-bom</artifactId>
<version>4.0.0.Beta3</version>
<type>pom</type>
<scope>import</scope>
</dependency>The command also generates a QuarkusEcsSyncResourceTest class and a QuarkusEcsSyncResourceIT class that call the hello endpoint of the generated resource.
The next section replaces that resource: delete these two files, or update them to match the endpoints you create.
Using the Amazon ECS client
The extension exposes the synchronous and asynchronous Amazon ECS clients of the AWS SDK as CDI beans, so you only need to inject them.
Edit the org.acme.ecs.QuarkusEcsSyncResource REST resource created by the previous command to inject the synchronous client:
package org.acme.ecs;
import jakarta.inject.Inject;
import jakarta.ws.rs.Path;
import software.amazon.awssdk.services.ecs.EcsClient;
@Path("/sync")
public class QuarkusEcsSyncResource {
@Inject
EcsClient client;
// Call the client from your endpoints
}To inject several clients with different configurations, refer to the named clients support.
Configuring Amazon ECS clients
Both Amazon ECS clients (sync and async) are configurable via the application.properties file that can be provided in the src/main/resources directory.
Additionally, you need to add to the classpath a proper implementation of the sync client. By default, the extension uses the URL connection HTTP client, so
you need to add a URL connection client dependency to the pom.xml file:
<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>url-connection-client</artifactId>
</dependency>If you want to use the Apache HTTP client instead, configure it as follows:
quarkus.ecs.sync-client.type=apacheAnd add the following dependency to the application pom.xml:
<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>apache-client</artifactId>
</dependency>If you want to use the AWS CRT-based HTTP client instead, configure it as follows:
quarkus.ecs.sync-client.type=aws-crtAnd add the following dependency to the application pom.xml:
<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>aws-crt-client</artifactId>
</dependency>If you provisioned a local Amazon ECS instance manually (for example Floci), configure the client to use it as follows:
quarkus.ecs.endpoint-override=http://localhost:4566 (1)
quarkus.ecs.aws.region=us-east-1 (2)
quarkus.ecs.aws.credentials.type=static (3)
quarkus.ecs.aws.credentials.static-provider.access-key-id=test-key
quarkus.ecs.aws.credentials.static-provider.secret-access-key=test-secret| 1 | Override the Amazon ECS client to use Floci instead of the actual AWS service. When it is set, Dev Services does not start a local stack for Amazon ECS. |
| 2 | Floci defaults to us-east-1 |
| 3 | The static credentials provider lets you set the access-key-id and secret-access-key directly |
If you want to work with an AWS account, you need an AWS account with access to Amazon ECS and the AWS Command Line Interface, then remove or comment out the endpoint-override and the static credentials properties above.
By default, the Amazon ECS client extension uses the default credentials provider chain that looks for credentials in this order:
-
Java System Properties -
aws.accessKeyIdandaws.secretAccessKey -
Environment Variables -
AWS_ACCESS_KEY_IDandAWS_SECRET_ACCESS_KEY -
Credential profiles file at the default location (
~/.aws/credentials) shared by all AWS SDKs and the AWS CLI -
Credentials delivered through the Amazon ECS if the
AWS_CONTAINER_CREDENTIALS_RELATIVE_URIenvironment variable is set and the security manager has permission to access the variable, -
Instance profile credentials delivered through the Amazon EC2 metadata service
And the region from your AWS CLI profile will be used.
|
Without Dev Services never starts in production mode. |
Next steps
Packaging
Packaging your application is as simple as ./mvnw clean package.
It can then be run with java -jar target/quarkus-app/quarkus-run.jar.
With GraalVM or Mandrel installed, you can also create a native executable binary:
./mvnw clean package -DnativeWithout GraalVM or Mandrel, build the native executable inside a container:
./mvnw clean package -Dnative -Dquarkus.native.container-build=trueDepending on your system, that will take some time.
Run the native executable with ./target/amazon-ecs-quickstart-1.0.0-SNAPSHOT-runner.
Dev Services does not start in production mode, so you need to make sure that your application.properties file is configured to use your AWS account or a local stack.
To use a local Floci instance, pass the endpoint and the credentials on the command line:
|
java \
-Dquarkus.ecs.endpoint-override=http://localhost:4566 \
-Dquarkus.ecs.aws.region=us-east-1 \
-Dquarkus.ecs.aws.credentials.type=static \
-Dquarkus.ecs.aws.credentials.static-provider.access-key-id=test-key \
-Dquarkus.ecs.aws.credentials.static-provider.secret-access-key=test-secret \
-jar target/quarkus-app/quarkus-run.jarSee the Packaging applications guide for more details.
Going asynchronous
Thanks to the AWS SDK v2.x used by the Quarkus extension, you can use the asynchronous programming model out of the box.
Create a org.acme.ecs.QuarkusEcsAsyncResource REST resource that will be similar to our QuarkusEcsSyncResource but using the asynchronous client:
package org.acme.ecs;
import jakarta.inject.Inject;
import jakarta.ws.rs.Path;
import software.amazon.awssdk.services.ecs.EcsAsyncClient;
@Path("/async")
public class QuarkusEcsAsyncResource {
@Inject
EcsAsyncClient client;
// Call the client from your endpoints
}The methods of the asynchronous client return CompletableFuture objects, which you can turn into Mutiny Uni instances with Uni.createFrom().completionStage(…).
To enable the asynchronous client, you also need to add the Netty HTTP client dependency to the pom.xml:
<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>netty-nio-client</artifactId>
</dependency>If you want to use the AWS CRT-based HTTP client instead, configure it as follows:
quarkus.ecs.async-client.type=aws-crtAnd add the following dependency to the application pom.xml:
<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>aws-crt-client</artifactId>
</dependency>Configuration Reference
Configuration property fixed at build time - All other configuration properties are overridable at runtime
Configuration property |
Type |
Default |
|---|---|---|
List of execution interceptors that will have access to read and modify the request and response objects as they are processed by the AWS SDK. The list should consists of class names which implements Environment variable: |
list of string |
|
OpenTelemetry AWS SDK instrumentation will be enabled if the OpenTelemetry extension is present and this value is true. Environment variable: |
boolean |
|
Type of the sync HTTP client implementation Environment variable: |
|
|
Type of the async HTTP client implementation Environment variable: |
|
|
If a local AWS stack should be used. (default to true) If this is true and endpoint-override is not configured then a local AWS stack will be started and will be used instead of the given configuration. The local AWS stack is provided by the stack provider configured with Environment variable: |
boolean |
|
Generic properties that are pass for additional container configuration. Environment variable: |
Map<String,String> |
|
The dev services stack provider to use for this service. If not specified, the global setting from quarkus.aws.devservices.provider is used. Supported values: "floci", "localstack", "ministack", "moto" This allows per-service override of the global stack selection. Environment variable: |
|
|
Type |
Default |
|
The endpoint URI with which the SDK should communicate. If not specified, an appropriate endpoint to be used for the given service and region. Environment variable: |
||
The amount of time to allow the client to complete the execution of an API call. This timeout covers the entire client execution except for marshalling. This includes request handler execution, all HTTP requests including retries, unmarshalling, etc. This value should always be positive, if present. Environment variable: |
||
The amount of time to wait for the HTTP request to complete before giving up and timing out. This value should always be positive, if present. Environment variable: |
||
Whether the Quarkus thread pool should be used for scheduling tasks such as async retry attempts and timeout task. When disabled, the default sdk behavior is to create a dedicated thread pool for each client, resulting in competition for CPU resources among these thread pools. Environment variable: |
boolean |
|
Type |
Default |
|
An Amazon Web Services region that hosts the given service. It overrides region provider chain with static value of region with which the service client should communicate. If not set, region is retrieved via the default providers chain in the following order:
See Environment variable: |
Region |
|
Configure the credentials provider that should be used to authenticate with AWS. Available values:
Environment variable: |
|
|
Type |
Default |
|
Whether this provider should fetch credentials asynchronously in the background. If this is Environment variable: |
boolean |
|
Whether the provider should reuse the last successful credentials provider in the chain. Reusing the last successful credentials provider will typically return credentials faster than searching through the chain. Environment variable: |
boolean |
|
Type |
Default |
|
AWS Access key id Environment variable: |
string |
|
AWS Secret access key Environment variable: |
string |
|
AWS Session token Environment variable: |
string |
|
Type |
Default |
|
The name of the profile that should be used by this credentials provider. If not specified, the value in Environment variable: |
string |
|
Type |
Default |
|
Whether the provider should fetch credentials asynchronously in the background. If this is true, threads are less likely to block when credentials are loaded, but additional resources are used to maintain the provider. Environment variable: |
boolean |
|
The amount of time between when the credentials expire and when the credentials should start to be refreshed. This allows the credentials to be refreshed *before* they are reported to expire. Environment variable: |
|
|
The maximum size of the output that can be returned by the external process before an exception is raised. Environment variable: |
|
|
The command that should be executed to retrieve credentials. Command and parameters are seperated list entries. Environment variable: |
list of string |
|
Type |
Default |
|
The name of custom AwsCredentialsProvider bean. Environment variable: |
string |
|
Type |
Default |
|
The maximum amount of time to establish a connection before timing out. Environment variable: |
|
|
The amount of time to wait for data to be transferred over an established, open connection before the connection is timed out. Environment variable: |
|
|
TLS key managers provider type. Available providers:
Environment variable: |
|
|
Path to the key store. Environment variable: |
path |
|
Key store type. See the KeyStore section in the https://docs.oracle.com/javase/8/docs/technotes/guides/security/StandardNames.html#KeyStore[Java Cryptography Architecture Standard Algorithm Name Documentation] for information about standard keystore types. Environment variable: |
string |
|
Key store password Environment variable: |
string |
|
TLS trust managers provider type. Available providers:
Environment variable: |
|
|
Path to the key store. Environment variable: |
path |
|
Key store type. See the KeyStore section in the https://docs.oracle.com/javase/8/docs/technotes/guides/security/StandardNames.html#KeyStore[Java Cryptography Architecture Standard Algorithm Name Documentation] for information about standard keystore types. Environment variable: |
string |
|
Key store password Environment variable: |
string |
|
Type |
Default |
|
The amount of time to wait when acquiring a connection from the pool before giving up and timing out. Environment variable: |
|
|
The maximum amount of time that a connection should be allowed to remain open while idle. Environment variable: |
|
|
The maximum amount of time that a connection should be allowed to remain open, regardless of usage frequency. Environment variable: |
||
The maximum number of connections allowed in the connection pool. Each built HTTP client has its own private connection pool. Environment variable: |
int |
|
Whether the client should send an HTTP expect-continue handshake before each request. Environment variable: |
boolean |
|
Whether the idle connections in the connection pool should be closed asynchronously. When enabled, connections left idling for longer than Environment variable: |
boolean |
|
Configure whether to enable or disable TCP KeepAlive. Environment variable: |
boolean |
|
Enable HTTP proxy Environment variable: |
boolean |
|
The endpoint of the proxy server that the SDK should connect through. Currently, the endpoint is limited to a host and port. Any other URI components will result in an exception being raised. Environment variable: |
||
The username to use when connecting through a proxy. Environment variable: |
string |
|
The password to use when connecting through a proxy. Environment variable: |
string |
|
For NTLM proxies - the Windows domain name to use when authenticating with the proxy. Environment variable: |
string |
|
For NTLM proxies - the Windows workstation name to use when authenticating with the proxy. Environment variable: |
string |
|
Whether to attempt to authenticate preemptively against the proxy server using basic authentication. Environment variable: |
boolean |
|
The hosts that the client is allowed to access without going through the proxy. Environment variable: |
list of string |
|
Type |
Default |
|
The maximum amount of time that a connection should be allowed to remain open while idle. Environment variable: |
|
|
The maximum number of allowed concurrent requests. Environment variable: |
int |
|
The amount of time to wait when initially establishing a connection before giving up and timing out. Environment variable: |
|
|
Enable HTTP proxy Environment variable: |
boolean |
|
The endpoint of the proxy server that the SDK should connect through. Currently, the endpoint is limited to a host and port. Any other URI components will result in an exception being raised. Environment variable: |
||
The username to use when connecting through a proxy. Environment variable: |
string |
|
The password to use when connecting through a proxy. Environment variable: |
string |
|
Configure whether to enable or disable TCP KeepAlive. Environment variable: |
boolean |
|
Time between TCP keepalive packets being sent to the peer. Environment variable: |
|
|
Time to wait for a keepalive response before considering the connection timed out. Environment variable: |
|
|
Number of keepalive probes allowed to fail before the connection is considered lost. Environment variable: |
int |
|
Type |
Default |
|
The maximum number of allowed concurrent requests. For HTTP/1.1 this is the same as max connections. For HTTP/2 the number of connections that will be used depends on the max streams allowed per connection. Environment variable: |
int |
|
The maximum number of pending acquires allowed. Once this exceeds, acquire tries will be failed. Environment variable: |
int |
|
The amount of time to wait for a read on a socket before an exception is thrown. Specify Environment variable: |
|
|
The amount of time to wait for a write on a socket before an exception is thrown. Specify Environment variable: |
|
|
The amount of time to wait when initially establishing a connection before giving up and timing out. Environment variable: |
|
|
The amount of time to wait when acquiring a connection from the pool before giving up and timing out. Environment variable: |
|
|
The maximum amount of time that a connection should be allowed to remain open, regardless of usage frequency. Environment variable: |
||
The maximum amount of time that a connection should be allowed to remain open while idle. Currently has no effect if Environment variable: |
|
|
Whether the idle connections in the connection pool should be closed. When enabled, connections left idling for longer than Environment variable: |
boolean |
|
Configure whether to enable or disable TCP KeepAlive. Applicable only to netty-nio client. Environment variable: |
boolean |
|
Type |
Default |
|
The maximum amount of time that a connection should be allowed to remain open while idle. Environment variable: |
|
|
The maximum number of allowed concurrent requests. Environment variable: |
int |
|
The amount of time to wait when initially establishing a connection before giving up and timing out. Environment variable: |
|
|
Enable HTTP proxy Environment variable: |
boolean |
|
The endpoint of the proxy server that the SDK should connect through. Currently, the endpoint is limited to a host and port. Any other URI components will result in an exception being raised. Environment variable: |
||
The username to use when connecting through a proxy. Environment variable: |
string |
|
The password to use when connecting through a proxy. Environment variable: |
string |
|
Configure whether to enable or disable TCP KeepAlive. Environment variable: |
boolean |
|
Time between TCP keepalive packets being sent to the peer. Environment variable: |
|
|
Time to wait for a keepalive response before considering the connection timed out. Environment variable: |
|
|
Number of keepalive probes allowed to fail before the connection is considered lost. Environment variable: |
int |
|
The HTTP protocol to use. Environment variable: |
|
|
The SSL Provider to be used in the Netty client. Default is Environment variable: |
|
|
The maximum number of concurrent streams for an HTTP/2 connection. This setting is only respected when the HTTP/2 protocol is used. Environment variable: |
long |
|
The initial window size for an HTTP/2 stream. This setting is only respected when the HTTP/2 protocol is used. Environment variable: |
int |
|
Sets the period that the Netty client will send This setting is only respected when the HTTP/2 protocol is used. Environment variable: |
|
|
Enable HTTP proxy. Environment variable: |
boolean |
|
The endpoint of the proxy server that the SDK should connect through. Currently, the endpoint is limited to a host and port. Any other URI components will result in an exception being raised. Environment variable: |
||
The hosts that the client is allowed to access without going through the proxy. Environment variable: |
list of string |
|
TLS key managers provider type. Available providers:
Environment variable: |
|
|
Path to the key store. Environment variable: |
path |
|
Key store type. See the KeyStore section in the https://docs.oracle.com/javase/8/docs/technotes/guides/security/StandardNames.html#KeyStore[Java Cryptography Architecture Standard Algorithm Name Documentation] for information about standard keystore types. Environment variable: |
string |
|
Key store password Environment variable: |
string |
|
TLS trust managers provider type. Available providers:
Environment variable: |
|
|
Path to the key store. Environment variable: |
path |
|
Key store type. See the KeyStore section in the https://docs.oracle.com/javase/8/docs/technotes/guides/security/StandardNames.html#KeyStore[Java Cryptography Architecture Standard Algorithm Name Documentation] for information about standard keystore types. Environment variable: |
string |
|
Key store password Environment variable: |
string |
|
Enable the custom configuration of the Netty event loop group. This option is only available when using Quarkus 3.x. With Quarkus 4, the AWS SDK always uses its own event loop. Environment variable: |
boolean |
|
Number of threads to use for the event loop group. If not set, the default Netty thread count is used (which is double the number of available processors unless the Environment variable: |
int |
|
The thread name prefix for threads created by this thread factory used by event loop group. The prefix will be appended with a number unique to the thread factory and a number unique to the thread. If not specified it defaults to Environment variable: |
string |
|
Whether the default thread pool should be used to complete the futures returned from the HTTP client request. When disabled, futures will be completed on the Netty event loop thread. Environment variable: |
boolean |
|
|
About the Duration format
To write duration values, use the standard You can also use a simplified format, starting with a number:
In other cases, the simplified format is translated to the
|
|
About the MemorySize format
A size configuration option recognizes strings in this format (shown as a regular expression): If no suffix is given, assume bytes. |