Amazon Data Firehose

Connect

Activate your license key and start the emulator with the Vera launcher, as in Activate Pro, then run this in a terminal of its own, from an empty scratch directory. It gives the official AWS CLI dummy credentials and a config file of its own, so no AWS account is needed and your own AWS profile isn't touched.

export VERA_ENDPOINT="http://localhost:5003"
export AWS_ACCESS_KEY_ID=test AWS_SECRET_ACCESS_KEY=test
export AWS_REGION=us-east-1 AWS_DEFAULT_REGION=us-east-1
export AWS_SHARED_CREDENTIALS_FILE=/dev/null
export AWS_EC2_METADATA_DISABLED=true
export AWS_PAGER="" AWS_CLI_AUTO_PROMPT=off
unset AWS_PROFILE AWS_DEFAULT_PROFILE
unset AWS_SESSION_TOKEN AWS_SECURITY_TOKEN
unset AWS_WEB_IDENTITY_TOKEN_FILE AWS_ROLE_ARN AWS_ROLE_SESSION_NAME
unset AWS_CONTAINER_CREDENTIALS_FULL_URI
unset AWS_CONTAINER_CREDENTIALS_RELATIVE_URI
cat > vera-aws-config <<'EOF'
[default]
region = us-east-1
output = json
cli_binary_format = base64
s3 =
    addressing_style = path
EOF
export AWS_CONFIG_FILE="$PWD/vera-aws-config"

When you've finished every example in this terminal, close it and delete vera-aws-config, not before.

Use the AWS CLI’s firehose commands. The emulator serves the 2015-08-04 API over the AWS JSON protocol.

A delivery stream to S3 needs the ARN of an existing IAM role. In Vera 1.2.2, delivery to local S3 worked with a freshly created role, but bytes reached the bucket at once instead of respecting the configured buffering interval (see Limitations). The example below is a read-only check.

Example

List the delivery streams on the emulator. The command creates nothing, so there’s nothing to clean up.

aws --endpoint-url "$VERA_ENDPOINT" firehose list-delivery-streams

On an emulator with no delivery streams, the list is empty. These are selected fields:

Output (selected fields)

{
    "DeliveryStreamNames": [],
    "HasMoreDeliveryStreams": false
}

Supported features

• Listing delivery streams, with ListDeliveryStreams.
• Delivery to S3. In Vera 1.2.2, a delivery stream worked with a freshly created IAM role and wrote bytes to local S3. In a diagnostic run on Vera 1.2.0 preview, where a role record already existed, a Direct PUT stream with an extended S3 destination was created and read back ACTIVE. A record of example.net and a newline was put, the resulting object was listed and downloaded from the bucket, and it held exactly those 12 bytes. Deleting the object, the stream and the bucket worked.
• Also served, not checked in Vera 1.2.0 preview or Vera 1.2.0-rc.3: batch puts, updating a destination, encryption and tags.

Limitations

The main limits are below. A few more apply to every service, and the API coverage notes cover smaller differences.

• No buffering. In Vera 1.2.2, bytes reached local S3 at once instead of respecting the configured buffering interval. In the diagnostic run on Vera 1.2.0 preview, with buffering hints of 1 MiB and 60 seconds, the object was in the bucket at once.
• Only basic S3 delivery was observed. It doesn’t establish compression, Lambda transformation, other destinations, retries or per-record errors from PutRecordBatch.

API coverage

Every operation in AWS's published 2015-08-04 API (SDK model, botocore 1.43.105), and whether the emulator implements it. Availability combines the earlier implementation inventory with the dated observations below; checking a page's example does not verify every operation. Each note names its evidence first; an observation given without a build or date comes from earlier testing, on 3 November 2026. What the statuses mean

Operation	Status	Notes
CreateDeliveryStream	Implemented	Local observation: Vera 1.2.2, 8 November 2026 — worked with a freshly created IAM role. Local observation: Vera 1.2.0 preview, 5 November 2026 — In a diagnostic run that reused an existing role record, created a Direct PUT stream with an extended S3 destination.
DeleteDeliveryStream	Implemented	Local observation: Vera 1.2.0 preview, 5 November 2026 — In a diagnostic run that reused an existing role record, deleted the stream.
DescribeDeliveryStream	Implemented	Local observation: Vera 1.2.0 preview, 5 November 2026 — In a diagnostic run that reused an existing role record, returned the stream ACTIVE.
ListDeliveryStreams	Implemented	Local observation: Vera 1.2.0 preview, 5 November 2026 — Returned an empty DeliveryStreamNames list, with HasMoreDeliveryStreams false, on an emulator with no delivery streams.
ListTagsForDeliveryStream	Implemented
PutRecord	Known difference	Local observation: Vera 1.2.2, 8 November 2026 — with a freshly created IAM role, bytes reached local S3 at once instead of respecting the configured buffering interval. Local observation: Vera 1.2.0 preview, 5 November 2026 — In a diagnostic run that reused an existing role record, wrote the record's 12 bytes to the S3 destination at once, despite buffering hints of 1 MiB and 60 seconds, as in earlier testing.
PutRecordBatch	Implemented
StartDeliveryStreamEncryption	Implemented
StopDeliveryStreamEncryption	Implemented
TagDeliveryStream	Implemented
UntagDeliveryStream	Implemented
UpdateDestination	Implemented