Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
giuseppe-trisciuoglio avatar

Aws Sdk Java V2 Core

  • 1.6k installs
  • 311 repo stars
  • Updated June 22, 2026
  • giuseppe-trisciuoglio/developer-kit

aws-sdk-java-v2-core is an agent skill that provides aws sdk for java 2.x client configuration, credential resolution, http client tuning, timeout, retry, and testing patterns. use when creating or hardening aws service

About

aws-sdk-java-v2-core is an agent skill from giuseppe-trisciuoglio/developer-kit that provides aws sdk for java 2.x client configuration, credential resolution, http client tuning, timeout, retry, and testing patterns. use when creating or hardening aws service clients, wiring spring b. # AWS SDK for Java 2.x Core Patterns ## Overview Use this skill to set up AWS SDK for Java 2.x clients with production-safe defaults. It focuses on the decisions that matter most: - how credentials and region are resolved - how to configure sync and async HTTP clients - how to apply timeouts, retries, lifecycle management, and tests Keep `SKILL Developers invoke aws-sdk-java-v2-core during ship/testing work for testing & qa tasks. The skill documents triggers, prerequisites, and step-by-step workflows grounded in SKILL.md.

  • AWS SDK for Java 2.x Core Patterns
  • Use this skill to set up AWS SDK for Java 2.x clients with production-safe defaults.
  • It focuses on the decisions that matter most:
  • how credentials and region are resolved
  • how to configure sync and async HTTP clients

Aws Sdk Java V2 Core by the numbers

  • 1,596 all-time installs (skills.sh)
  • +55 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #458 of 2,184 Testing & QA skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

aws-sdk-java-v2-core capabilities & compatibility

Capabilities
aws sdk for java 2.x core patterns · use this skill to set up aws sdk for java 2.x cl · it focuses on the decisions that matter most: · how credentials and region are resolved · how to configure sync and async http clients
Use cases
orchestration
From the docs

What aws-sdk-java-v2-core says it does

Use this skill to set up AWS SDK for Java 2.x clients with production-safe defaults.
SKILL.md
It focuses on the decisions that matter most:
SKILL.md
- how credentials and region are resolved
SKILL.md
npx skills add https://github.com/giuseppe-trisciuoglio/developer-kit --skill aws-sdk-java-v2-core

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1.6k
repo stars311
Security audit3 / 3 scanners passed
Last updatedJune 22, 2026
Repositorygiuseppe-trisciuoglio/developer-kit

What it does

Provides AWS SDK for Java 2.x client configuration, credential resolution, HTTP client tuning, timeout, retry, and testing patterns. Use when creating or hardening AWS service clients, wiring Spring B

Who is it for?

Developers working on testing & qa during ship tasks.

Skip if: Tasks outside Testing & QA scope described in SKILL.md.

When should I use this skill?

Provides AWS SDK for Java 2.x client configuration, credential resolution, HTTP client tuning, timeout, retry, and testing patterns. Use when creating or hardening AWS service clients, wiring Spring B

What you get

Completed testing & qa workflow aligned with SKILL.md steps.

  • Configured AWS service client code
  • Builder pattern boilerplate

Files

SKILL.mdMarkdownGitHub ↗

AWS SDK for Java 2.x Core Patterns

Overview

Use this skill to set up AWS SDK for Java 2.x clients with production-safe defaults.

It focuses on the decisions that matter most:

  • how credentials and region are resolved
  • how to configure sync and async HTTP clients
  • how to apply timeouts, retries, lifecycle management, and tests

Keep SKILL.md focused on setup and delivery flow. Use the references/ files for deeper API details and expanded examples.

When to Use

  • Creating or hardening AWS SDK for Java 2.x service clients
  • Wiring Spring Boot beans for AWS integration
  • Debugging auth, region, or credential issues
  • Choosing between sync (S3Client, DynamoDbClient) and async (S3AsyncClient, SqsAsyncClient) clients

Instructions

1. Select the service client type

  • Sync clients (S3Client, DynamoDbClient) for request/response flows
  • Async clients (S3AsyncClient, SqsAsyncClient) for concurrency, streaming, or backpressure
  • Reuse one client per service and configuration profile

2. Configure credential and region resolution

Use DefaultCredentialsProvider with environment-aware defaults:

  • local dev: shared AWS config, SSO, or environment variables
  • CI/CD: web identity or injected environment variables
  • AWS runtime: ECS task roles, EKS IRSA, or EC2 instance profiles

Override only for multi-account access, test isolation, or profile switching.

Verify: Call StsClient.getCallerIdentity() at startup to confirm credentials resolve.

3. Configure HTTP client, timeouts, and retries

Set production values explicitly:

  • API call timeout and attempt timeout
  • connection timeout and max connections or concurrency
  • retry strategy aligned with service quotas and idempotency

Use ApacheHttpClient for sync and NettyNioAsyncHttpClient for async.

Verify: Confirm timeouts and retry behavior under failure conditions.

4. Wire clients as application-level dependencies

In Spring Boot:

  • expose clients as @Bean singletons
  • inject through constructors
  • keep credential and region in configuration files

Verify: Check clients are not created inside hot execution paths.

Close custom HTTP clients and SDK clients during shutdown if lifecycle is not managed automatically.

5. Handle failures at integration boundaries

At the boundary layer:

  • catch SdkException or service-specific exceptions
  • distinguish retryable failures from auth, quota, and validation failures
  • log request context, never secrets or raw credentials

6. Run integration tests before shipping

  • verify region and caller identity in the target environment
  • run tests against LocalStack, Testcontainers, or a sandbox account
  • use @PostConstruct in Spring Boot configuration to fail fast on startup if credentials are missing
StsClient stsClient = StsClient.builder().build();
GetCallerIdentityResponse identity = stsClient.getCallerIdentity();
// Logs: Successfully authenticated as: {identity.arn()}

Examples

Example 1: Spring Boot sync client with explicit HTTP and timeout settings

@Configuration
public class AwsClientConfiguration {

    @Bean
    S3Client s3Client() {
        return S3Client.builder()
            .region(Region.of("eu-south-2"))
            .credentialsProvider(DefaultCredentialsProvider.create())
            .httpClientBuilder(ApacheHttpClient.builder()
                .maxConnections(100)
                .connectionTimeout(Duration.ofSeconds(3)))
            .overrideConfiguration(ClientOverrideConfiguration.builder()
                .apiCallAttemptTimeout(Duration.ofSeconds(10))
                .apiCallTimeout(Duration.ofSeconds(30))
                .build())
            .build();
    }
}

Example 2: Async client for high-concurrency workloads

SqsAsyncClient sqsAsyncClient = SqsAsyncClient.builder()
    .region(Region.US_EAST_1)
    .credentialsProvider(DefaultCredentialsProvider.create())
    .httpClientBuilder(NettyNioAsyncHttpClient.builder()
        .maxConcurrency(200)
        .connectionTimeout(Duration.ofSeconds(3))
        .readTimeout(Duration.ofSeconds(20)))
    .overrideConfiguration(ClientOverrideConfiguration.builder()
        .apiCallTimeout(Duration.ofSeconds(30))
        .build())
    .build();

Best Practices

  • Default to DefaultCredentialsProvider unless a project requirement says otherwise.
  • Keep region selection explicit for server-side services.
  • Reuse SDK clients instead of constructing them per request.
  • Tune retries with service quotas and idempotency in mind.
  • Put business mapping on top of the SDK, not inside controllers.
  • Keep integration tests close to the configuration that creates the clients.
  • Move deep service-specific examples to dedicated skills such as S3, DynamoDB, Bedrock, or Secrets Manager.

Constraints and Warnings

  • Do not embed access keys or session tokens in source code, examples, or configuration files.
  • Static credentials are acceptable only for tightly scoped local tests.
  • Missing region or invalid credential resolution often fails only at first call, so verify startup assumptions explicitly.
  • Async clients require lifecycle management for the underlying HTTP resources.
  • Excessive retries can amplify throttling and increase latency.
  • Proxy, TLS, and metric publisher APIs can vary by chosen HTTP stack and SDK version; adapt examples to the versions already used by the project.

References

  • references/api-reference.md
  • references/best-practices.md
  • references/developer-guide.md

Related Skills

  • aws-sdk-java-v2-secrets-manager
  • aws-sdk-java-v2-s3
  • aws-sdk-java-v2-dynamodb
  • aws-sdk-java-v2-bedrock

Related skills

How it compares

Pick aws-sdk-java-v2-core over service-specific skills when you need foundational ClientBuilder setup before integrating any AWS Java SDK v2 service.

FAQ

What does aws-sdk-java-v2-core do?

Provides AWS SDK for Java 2.x client configuration, credential resolution, HTTP client tuning, timeout, retry, and testing patterns. Use when creating or hardening AWS service clients, wiring Spring B

When should I use aws-sdk-java-v2-core?

During ship testing work for testing & qa.

Is aws-sdk-java-v2-core safe to install?

Review the Security Audits panel on this listing before production use.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.