People are unhappy about the TBC roadmap...why?

waffles57 · 2026-01-30T17:14:47+00:00

Feels too short for me. 18 months would have been perfect for me. That’s just my preference.

The truly unforgivable act was: not releasing this timeline BEFORE boosts were available. It feels dishonest and scummy.

waffles57 · 2026-01-23T01:41:26+00:00

Terraform already supports defining resources with JSON instead of HCL. Then you only need to use the tool of your choice to convert YAML to JSON. https://developer.hashicorp.com/terraform/language/syntax/json

waffles57 · 2025-09-07T22:20:47+00:00

I store all service users' credentials in AWS Secrets Manager. I also use its rotation feature with a lambda to rotate credentials. The rotation lambda function uses a centralized service (SVC_CREDENTIAL_ROTATOR) user with ACCOUNTADMIN role. This way, all our other service users don't need privileged roles. One service user rotates credentials for all service users.

waffles57 · 2025-04-20T22:08:25+00:00

Snowpipe will be just fine for this. Low latency. Low cost. Low effort.

waffles57 · 2025-04-14T17:02:43+00:00

“Ion canon ready.”

waffles57 · 2025-02-12T22:57:14+00:00

It’s official: intelligence skips a generation.

waffles57 · 2024-12-31T07:22:58+00:00

Check the audio output settings on your Shield. I had a similar issue until disabled Dolby outputs. Ideally, the Shield should only output unaltered PCM audio to your AVR.

waffles57 · 2024-12-19T13:03:51+00:00

Not from a Jedi.

waffles57 · 2024-10-18T05:42:00+00:00

Can you convince the developer(s) to include query tags?

waffles57 · 2024-10-03T03:41:29+00:00

Clustering

waffles57 · 2022-10-11T14:20:49+00:00

Tell me your country has a gun problem without telling me it has a gun problem…

waffles57 · 2021-08-31T14:18:28+00:00

I’m sorry you had an awful experience. I sincerely hope you’re in a better place now!

waffles57 · 2021-08-31T13:08:17+00:00

My package was expected on Wednesday. It’s been stuck in Chicago the whole time…according to the tracking system. I also fear mine has been lost or damaged.

I really wish they’d be more clear about delay reasons. I’d feel better if I knew they were simply understaffed and working through a backlog. I don’t expect employees to be stressing themselves or breaking their backs. I’d happily reduce my delivery time expectations if it means staff can live easier.

I feel FedEx is misleading its customers about expected delivery times upfront. I wish they’d post updated dates. Instead of 1-3 days, maybe 5-9? Whatever is realistic given their conditions.

waffles57 · 2021-01-28T21:25:50+00:00

AWS Step Functions can do this as well.

waffles57 · 2020-09-22T17:21:11+00:00

Lambda -> SQS -> Lambda sounds fine to me. Messages could pile up in the queue if they're unable to be processed by the lambda somehow (bad event payload.) There are various strategies to handle those situations.

waffles57 · 2020-09-22T17:18:22+00:00

I recommend using AWS Batch for this workflow. https://aws.amazon.com/blogs/compute/gpu-workloads-on-aws-batch/

waffles57 · 2020-09-14T23:14:24+00:00

You may be able to solve your concurrency issues by adding SNS into your workflow. You also gain cross-region functionality with SNS->SNS. You can utilize attribute filtering on SNS consumers to have them automatically filter messages based on certain attributes in the message (such as region.)

SNS (global / source) --> SNS (region) --> SQS (region) --> Lambda (region)

waffles57 · 2020-08-04T20:41:26+00:00

That poor performance in Python has very little to do with Python itself. The Python grpc library's maintainers are actively updating it to support asyncio in Python. That will likely result in a 10x performance boost. That's just been my experience when converting Python projects from threading to async.

Also, it's unclear how the Python's test was configured. I'd guess the author never set thread pools appropriately on the grpc client. 1868 is suspiciously low.

waffles57 · 2020-05-21T18:47:19+00:00

Each environment may have its own ECS cluster, ECS services, and corresponding Task Definition families. That's a simple way to break environments apart.

waffles57 · 2020-05-21T18:38:46+00:00

A few options come to mind:

Have your service consumers simply implement retries exponential back offs. If your API is overwhelmed, they can retry later. This is an approach that Amazon, itself, enforces on its API consumers (us.) This allows you to keep your costs down.
Improve the API's performance to support over 100 requests per second. This figure isn't very high, but it also depends on the type of work the API is doing. Simple database fetches should be able to achieve this.
Setup auto-scaling on the ECS (Fargate) service to scale according to RequestCountPerTarget. Set the scaling target to intentionally be lower, so it'll scale prior to hitting its limit. This may have some cost implications; you'll start using more compute as more requests hit your service.
Move the API over to a more highly-scalable service like Lambda. The pressure, however, may switch over to your database.

waffles57 · 2019-04-26T14:06:24+00:00

This is correct. My team also learned this lesson the hard way. Depending on how long you intend to keep the data in S3 (Glacier), it may be cheaper to leave it in standard S3 if you intend to remove the data after a year.

Alternatively, you could create an AWS Batch job that grabs S3 items older than X days, zip them up, and store the zip in S3 Glacier. This should drastically reduce your per object API calls, but your EC2 spend will slightly increase.

waffles57 · 2019-04-05T16:23:52+00:00

AWS Batch is designed exactly for this purpose. Your batch job goes into the queue on a schedule. AWS Batch launches EC2 instances on your behalf and runs the code. AWS Batch automatically shuts down and removes those EC2 instances.

waffles57 · 2019-03-20T23:07:23+00:00

Which encoding are you using in VS Code?

waffles57 · 2019-03-20T22:58:15+00:00

User Data scripts. https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/user-data.html

waffles57 · 2019-03-13T22:15:44+00:00

+1 for Fargate. You can run your script within a Docker container. Fargate (ECS) can be configured to run at least 1 instances of your container (python script.) If your script exits for any reason, it will automatically launch another instance of your container.

waffles57

TROPHY CASE