Telegram RegisterThe public register of Telegram
Telegram profile photo for AWS - What's new RSS feed.

Channel

AWS - What's new RSS feed.

@awscloud

On this record: Growth · Engagement · Posts · Citations · Cite this entry

160subscribers

-3 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001005959832
TypeChannel
Username@awscloud
CreatedBetween 1 September 2015 and 31 December 2015 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live5 September 2026
Measurements held3
Confirmed unchanged4 times, most recently 5 September 2026
On Telegramt.me/awscloud

Growth

160163161.56 August 2026 — 163 subscribers8 August 2026 — 163 subscribers15 August 2026 — 160 subscribers6 August 202615 August 2026
3 measurements spanning 9 days, net -3. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 160–163 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 03:14160-3
8 Aug 2026, 16:31163no change
6 Aug 2026, 15:03163first reading

Engagement

20 posts held, back to 7 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

8 Aug 2026, 07:25 UTC12 viewsread 8 August 2026

Recent Announcements Amazon VPC IPAM now supports BGP route protection monitoring and delegated RPKI for BYOIP prefixes

8 Aug 2026, 01:24 UTC12 viewsread 8 August 2026

Recent Announcements Amazon EC2 R8i and R8i-Flex instances are now available in Europe (Milan) region

8 Aug 2026, 01:24 UTC12 viewsread 8 August 2026

Recent Announcements Amazon Timestream for InfluxDB now supports backup and restore

8 Aug 2026, 01:24 UTC12 viewsread 8 August 2026

Recent Announcements Amazon Cognito now available as a skill in the Agent Toolkit for AWS

8 Aug 2026, 01:24 UTC12 viewsread 8 August 2026

Recent Announcements Amazon Bedrock AgentCore adds memory, policy, and harness in AWS GovCloud (US-West)

8 Aug 2026, 01:24 UTC10 viewsread 8 August 2026

Recent Announcements Amazon GameLift Servers now supports 21 new EC2 instance types

8 Aug 2026, 01:24 UTC10 viewsread 8 August 2026

Recent Announcements Amazon OpenSearch Service announces additional upgrade runway for existing domains and support dates for additional versions

8 Aug 2026, 01:24 UTC10 viewsread 8 August 2026

Recent Announcements Amazon OpenSearch UI now supports Network Access Control

8 Aug 2026, 01:24 UTC11 viewsread 8 August 2026

Recent Announcements Amazon Connect Customer adds one-click drill-down on real-time metrics dashboards

7 Aug 2026, 19:23 UTC13 viewsread 8 August 2026

Recent Announcements AWS IAM Identity Center supports one-click multi-Region option for new organization instances

7 Aug 2026, 19:23 UTC13 viewsread 8 August 2026

Recent Announcements AWS Parallel Computing Service is now in scope for FedRAMP, SOC, ISO, CSA STAR, and PCI

7 Aug 2026, 19:23 UTC13 viewsread 8 August 2026

Recent Announcements AWS WAF now supports a Salt Security managed rule group for API and MCP threat detection

Showing the 12 most recent of 20 posts we hold for @awscloud. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Mentions

Named by 4 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 15 August 2026 — this entry's latest reading, not the date you are reading this.

“AWS - What's new RSS feed.” (@awscloud), 160 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/awscloud.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.