AWS Amplify (Twitter) RT @mauerbac: Wanted to make a final call for this tweet! I'm starting to reach out to folks today :) Please DM if able to help

Channel
AWS Community Builders
@awscommunitybuilders
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
148subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001357872558 |
|---|---|
| Type | Channel |
| Username | @awscommunitybuilders |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/awscommunitybuilders |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 14:13 | 148 | -1 |
| 15 Aug 2026, 01:36 | 149 | -1 |
| 8 Aug 2026, 20:00 | 150 | no change |
| 7 Aug 2026, 04:09 | 150 | first reading |
Engagement
20 posts held, back to 22 September 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 2 November 2023. An engagement rate over an empty window would be a number about nothing.
Recent posts
AWS Amplify (Twitter) Dynamic navigation made easy! Check out the new Breadcrumbs component in AWS Amplify UI. It's perfect for creating intuitive user journeys in your apps. 🧭 go.aws/46W3gCe
AWS Amplify (Twitter) Learn how to build a high-performance, low-maintenance blog using the new AWS Amplify Contentful integration. 📝 Score an A+ on the Lighthouse performance scale with ease! go.aws/3Q31dFH
AWS Amplify (Twitter) Exciting news from the Amplify UI Library team! 🚀 Introducing 8 new React UI components and enhancements to 2 others. Get ready to build feature-rich apps that are performant, themeable, responsive, and accessible! 💻 go.aws/3M7kc0Z
AWS Amplify (Twitter) RT @focusotter: My new superpower 🦸🏽♂️ is combining @AWSAmplify with the L3 AppSync construct and the CDK. All of my code is in TypeScript and I use intellisense to navigate AWS services for me. Learn how I get my apps live on the web when combining these tools together youtube.com/6-Z7xJCp-Zw
AWS Amplify (Twitter) Harness the power of GraphQL and AWS to streamline your data lake access. This article lays down a blueprint for integrating AWS AppSync and AWS Lake Formation! 🛠️📈 go.aws/3Q2YA6N
AWS Amplify (Twitter) Explore the key differences between SSG and SSR apps and how to deploy either approach using AWS Amplify 👀 go.aws/3tE3kIR
AWS Amplify (Twitter) We're hanging out at ViteConf 2023, an immersive online event hosted by StackBlitz today! Come join us! Don't miss out on this opportunity to learn about the latest trends and advancements in web development! Get your free tickets here: go.aws/3Q5PxU0
AWS Amplify (Twitter) RT @focusotter: I'm crashing the party for @AWSAmplify office hours! come hang and try and stump me with your AppSync questions while I dive into the new L3 construct! discord.gg/Xky6dAeXm6?event=…
AWS Amplify (Twitter) 🌟 NEW: Amplify GraphQL API as a CDK construct 🌟 📄 Single source-of-truth for API & data 🚀 Access to L2 and L1 constructs 🛠️ Query & mutations w/o cold starts 🔄 PubSub-capable 💻 Client library codegen 🥳 Parity w/ GraphQL transformer Learn more: go.aws/3Q6aqP6
AWS Amplify (Twitter) RT @mauerbac: 📢 Amplify Studio users... i'm looking to chat with you! Curious to get your feedback and tell you about new capabilities. If you have experience with Studio, please reach out or comment below 🙏
AWS Amplify (Twitter) Learn how to deploy a SSG Next.js app to Amplify 🛠️ go.aws/3PZXTMM
Showing the 12 most recent of 20 posts we hold for @awscommunitybuilders. 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
Names
Channels on the register whose handles appear in this channel's posts.
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.
Handles this channel named that no longer answer
- Dead references
- 3
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 3
- vacant every time we have ever looked
@awscommunitybuilders named 3 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 2 posts, 9 August 2026 – 9 August 2026
named in 2 posts, 9 August 2026 – 9 August 2026
named in 2 posts, 9 August 2026 – 9 August 2026
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“AWS Community Builders” (@awscommunitybuilders), 148 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/awscommunitybuilders.
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.