# ClickPipes failing on Kinesis in AWS us-east-1

- Provider: [ClickHouse Cloud](https://down.guide/clickhouse-cloud)
- Level: confirmed
- Impact: Degraded
- lasted 1d 5h
- started 2026-09-15 18:57 UTC
- us, us-east-1
- id: DWN-f938685a5f
- Official page: https://status.clickhouse.com/incidents/01M2K6X3SMPMBKJKK5FHA0M7ZB

## Updates from ClickHouse Cloud
### 2026-09-15 18:57 UTC: investigating
Currently investigating failures on AWS us-east-1 for customers using ClickPipes on Kinesis in this region.

### 2026-09-15 20:03 UTC: identified
The issue has been identified as a change on AWS related to Kinesis IAM permissions and appears to be currently isolated to us-east-1. While we work with AWS to mitigate this issue, we recommend to update your IAM policy to include a trailing wildcard (/\*) to the resource for the kinesis:RegisterStreamConsumer action like so:
\`\`\`
{
 "Effect": "Allow",
 "Action": \[
 "kinesis:RegisterStreamConsumer"
 \],
 "Resource": \[
 "arn:aws:kinesis:{REGION}:{ACCOUNT\_ID}:stream/{STREAM\_NAME}/\*"
 \]
}
\`\`\`
Once this is applied, you must restart your ClickPipe for the changes to take affect.

### 2026-09-15 22:45 UTC: identified
AWS has confirmed the issue on their end and are in the process of rolling back the change. The ETA for this rollback in us-east-1 is by end of day tomorrow. Signs of gradual recovery are expected in us-east-1 as the rollback progresses across AZs during this time. In the meantime, if your ClickPipe is still affected, please update your IAM policy as instructed in the previous status update.

### 2026-09-16 03:17 UTC: identified
AWS has confirmed that on September 15, 2026, beginning at 11:15 AM PDT, customers experienced elevated AccessDeniedException errors when calling the RegisterStreamConsumer API for Amazon Kinesis Data Streams (Kinesis) in the N. Virginia (us-east-1) Region. The root cause was a recent change that introduced a defect in how RegisterStreamConsumer requests are authorized, causing each request to be evaluated against the specific consumer resource (for example, arn:aws:kinesis: : :stream/ /consumer/ ) rather than the stream resource (for example, arn:aws:kinesis: : :stream/ ). As a result, IAM policies that granted kinesis:RegisterStreamConsumer only at the stream level, which previously succeeded and aligns with our published documentation, no longer matched the request and returned AccessDeniedException. 
AWS has begun rolling back this change in the affected Region, and expect calls that were previously permitted at the stream level to succeed again once the rollback completes on September 16, 2026, by 6:00 PM PDT. As a workaround, please update your IAM policy as instructed in the previous status update.

### 2026-09-16 15:21 UTC: identified
AWS has confirmed that on September 15, 2026, beginning at 11:15 AM PDT, customers experienced elevated AccessDeniedException errors when calling the RegisterStreamConsumer API for Amazon Kinesis Data Streams (Kinesis) in the N. Virginia (us-east-1) Region. The root cause was a recent change that introduced a defect in how RegisterStreamConsumer requests are authorized, causing each request to be evaluated against the specific consumer resource (for example, arn:aws:kinesis: : :stream/ /consumer/ ) rather than the stream resource (for example, arn:aws:kinesis: : :stream/ ). As a result, IAM policies that granted kinesis:RegisterStreamConsumer only at the stream level, which previously succeeded and aligns with our published documentation, no longer matched the request and returned AccessDeniedException.
AWS has begun rolling back this change in the affected Region, and expect calls that were previously permitted at the stream level to succeed again once the rollback completes on September 16, 2026, by 6:00 PM PDT. As a workaround, please update your IAM policy as instructed in the previous status update.

### 2026-09-17 00:43 UTC: resolved
This incident has been resolved. AWS has confirmed that the Enhanced Fanhout (EFO) Kinesis pipes in us-east-1 region are fully operational. Please contact ClickHouse Support if you experience any further issues:

From the builder: does your app depend on ClickHouse Cloud? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=clickhouse-cloud) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention ClickHouse Cloud.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-f938685a5f), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.