sdk-test-java

sdk-test-java

Compatibility tests for Floci using the AWS SDK for Java v2 (2.31.8).

Runs 352 tests across 17 test classes against a live Floci instance — no mocks.

Services Covered

Test class	Description
SsmTest	Parameter Store — put, get, path, tags
SqsTest	Queues, send/receive/delete, DLQ, visibility
SnsTest	Topics, subscriptions, publish, SQS delivery
S3Test	Buckets, objects, tagging, copy, multipart, batch delete
DynamoDbTest	Tables, CRUD, batch, TTL, tags, streams
DynamoDbScanConditionTests	Scan filter and condition expressions
LambdaTest	Create/invoke/update/delete functions
IamTest	Users, roles, policies, access keys
StsTest	GetCallerIdentity, AssumeRole, GetSessionToken
SecretsManagerTest	Create/get/put/list/delete secrets, versioning, tags
KmsTest	Keys, aliases, encrypt/decrypt, data keys, sign/verify
CloudWatchTest	PutMetricData, ListMetrics, GetMetricStatistics, alarms
CloudFormationVirtualHostTests	Virtual host style S3 access via CloudFormation
ApigwSfnJsonataCrudlTests	API Gateway + Step Functions JSONata CRUDL integration
ApiGatewayV2WebSocketAndExtendedOpsTest	API GW v2 WebSocket APIs, Update ops, Route/Integration Responses, Models, Tagging
Ec2Tests	EC2 instances, VPCs, security groups, subnets
AppSyncTest	GraphQL API CRUDL, data sources, resolvers, functions, types, API keys, tags, schema validation
EcsTests	ECS clusters, task definitions, services

Adding a New Test

Create a standard JUnit 5 test class in src/test/java/com/floci/test/. Tests run against a live Floci instance using real AWS SDK clients.

Requirements

• Java 17+
• Maven

Running

# All tests
mvn test -q

# Specific test class
mvn test -Dtest=S3Test

# Via just (from compatibility-tests/)
just test-java

Configuration

Variable	Default	Description
FLOCI_ENDPOINT	http://localhost:4566	Floci emulator endpoint
AWS_REGION	us-east-1	Region the TestFixtures clients sign for

AWS credentials are always test / test. Setting AWS_REGION=cn-north-1 (with Floci started with FLOCI_DEFAULT_REGION=cn-north-1) runs the suite in the China partition; the nightly Partition Compatibility workflow does exactly that, and tolerates only the failures listed in .github/ci/compat-partition-allowlist-cn-north-1.txt. Tests that build their own client with an explicit region keep that region.

STS presigned identity checks

StsPresignedIdentityTest checks user and role identity over HTTP/1.1 and HTTP/2. Valid identity requests run in both modes. Forged signatures and changed bodies are sent only when signature checking is enabled. To check signature refusal, start Floci with FLOCI_AUTH_VALIDATE_SIGNATURES=true and pass the same setting to this test:

FLOCI_AUTH_VALIDATE_SIGNATURES=true mvn test -Dtest=StsPresignedIdentityTest

The test setting must match the server setting; it does not configure the server. The enabled mode also checks missing and incorrect temporary-session tokens.

Metric filter publishing checks

CloudWatchLogsMetricFilterTest and CloudFormationLogsMetricFilterTest run with the rest of the suite. Against a server on another port:

# From compatibility-tests/sdk-test-java
FLOCI_ENDPOINT=http://127.0.0.1:18084 ../../mvnw test \
  -Dtest=CloudWatchLogsMetricFilterTest,CloudFormationLogsMetricFilterTest

The publishing tests read their expected values from src/test/resources/cloudwatchlogs/metric-filter-publishing-aws.json, a byte-identical copy of the root fixture recorded from AWS. MetricFilterFixturePackagingTest checks the copy loads from the classpath, and the root CloudWatchLogsMetricFilterFixturePackagingTest fails when either SDK module copy drifts from the root file. The SDK selects the CloudWatch JSON protocol; MetricFilterQueryAssertions signs the same reads as legacy form-encoded Query requests, so GetMetricStatistics and GetMetricData on both wire formats are asserted against every statistic the fixture records (Sum, SampleCount, Minimum, Maximum). Reads poll for the sample, since the server publishes it shortly after PutLogEvents returns. Passing these tests shows Floci matches the recorded values; it is not live AWS verification. For the opt-in replay against AWS see ../sdk-test-python/README.md.

Docker

docker build -t floci-sdk-java .
docker run --rm --network host floci-sdk-java

# Custom endpoint (macOS/Windows)
docker run --rm -e FLOCI_ENDPOINT=http://host.docker.internal:4566 floci-sdk-java