James Miller

38 Followers
259 Following
60 Posts
@mikebroberts That works really well for a DynamoDB sort key (ULID is great too)! Highly recommend. Make sure the implementation you use implements the monotonicity portion of the spec, otherwise you'll see ordering issues, particularly noticeable in tests.
maybe_so/lib/maybe_so/core_ext at main · planningcenter/maybe_so

Ruby boolean type casting. Contribute to planningcenter/maybe_so development by creating an account on GitHub.

GitHub
Per-message retention here is backed by DynamoDB TTLs. Such an under-appreciated database feature that is handled flawlessly in DynamoDB and S3. Deleting data should always be this easy!
https://mastodon.social/@hotsock/113306554563559417
Now we're talking. Brings the Serverless minimum/idle cost from $90 down to $6/mo. 👏
https://awscommunity.social/@awswhatsnew/113274165372229506
What’s New on AWS (@[email protected])

Announcing Amazon ElastiCache for Valkey https://aws.amazon.com/about-aws/whats-new/2024/10/amazon-elasticache-valkey Today, Amazon ElastiCache announces support for Valkey with Serverless priced 33% lower and node-based priced 20% lower than other supported engines. With ElastiCache Serverless for Valkey, customers can create a cache in under a minute and get...

AWSCommunity.social
Is this an AWS permissions oversight? If you can write to any CloudWatch Logs log stream, you're implicitly granted account-wide CloudWatch Metrics publishing permissions - any metrics in any namespaces. Just write logs to the stream using CloudWatch embedded metric format. Doesn't seem to be any way to lock this down. https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Embedded_Metric_Format_Specification.html
Specification: Embedded metric format - Amazon CloudWatch

Explains the format of the specification for CloudWatch embedded metric format.

Does it matter? Def not. But it’s funny to consider that the duration portion of the bill for issuing JWTs would be cut in half if I could shave off 1/5 of a millisecond. Maybe with Graviton3/4! #awswishlist
Weird discovery - seems it’s darn near impossible to get AWS Lambda invocations to run (billable) in less than 1ms, even if they’re doing absolutely nothing (Go / provided.al2023 / arm64). I can consistently get 1.08-1.2ms, but all that time is pre-handler overhead.
Along with @hotsock earlier this week, I released a pre-built CloudFormation stack where you can invoke a Lambda function that signs JWTs with secure key custody in either KMS or Parameter Store. https://github.com/hotsock/jwt-issuer
GitHub - hotsock/jwt-issuer: Issue JSON Web Tokens (JWTs) securely from Lambda in your AWS account using either KMS or Parameter Store for key custody.

Issue JSON Web Tokens (JWTs) securely from Lambda in your AWS account using either KMS or Parameter Store for key custody. - hotsock/jwt-issuer

GitHub

I've been working on @hotsock for a long time - today it's released! 🚀

It's a privacy-focused real-time messaging service that runs in your AWS account.

Use it for chat, real-time updates, multiplayer use cases, doc collaboration, etc!

Stand up your own CloudFormation stack with just 2 CloudShell CLI commands in any of the 22 supported regions around the world! Plus it has a perpetual free tier for 1M WebSocket messages per month. Check it out!

https://www.hotsock.io/blog/hotsock-v1.0/

#serverless #aws #iac

Hotsock v1.0 Released! | Hotsock

Real-time functionality is a core expectation in modern applications. Whether you're building complex user interfaces, showing messages and typing indicators for a chat product, keeping player moves up-to-date in a collaborative game, or one of endless other multi-player use cases, instant feedback is crucial for a great user experience.

@nateberkopec Isn't it the exact same chip? Only difference appears to be the memory allocation.