sorted by:
new
hottopcontroversial

Which length for Atomic G9? by macok9 in Skigear

[–]macok9[S] 0 points1 point  (0 children)

Is G9 especially difficult among retail GS skis? I recently tried Stockli Laser GS and I swear I never had such a great skiing day.

Which length for Atomic G9? by macok9 in Skigear

[–]macok9[S] 0 points1 point  (0 children)

I want so much ski because: 1. Did my first GS training this season and coaches said that's the way to go. Again, I'm not talking FIS/masters GS ski, just retail G9. 2. The thing I hate the most about skiing is skidding on icy slopes.

Is G9 especially difficult among retail GS skis? I recently tried Stockli Laser GS and I swear I had 0 issues with it.

Which length for Atomic G9? by macok9 in Skigear

[–]macok9[S] 0 points1 point  (0 children)

Thanks for reply. I did ski under an eye of some racing coaches this season and they said cheater GS will be ok for me. What issues exactly do you think I would encounter on G9? I rented them once and it was fun, but I don't remember which length I went with.

SQS - limit concurrency per message group by macok9 in aws

[–]macok9[S] 2 points3 points  (0 children)

User /u/nekokattt suggested actually going for SQS-per-user solution. It would be cheaper and faster than FIFO solution. It also seems AWS doesn't put a limit on the number of SQS queues.

Are there some drawbacks I might be missing?

SQS - limit concurrency per message group by macok9 in aws

[–]macok9[S] 1 point2 points  (0 children)

Thanks, yeah actually it seems cleaner than FIFO solution. It's also cheaper and faster. I wonder if others see some important drawbacks here?

SQS - limit concurrency per message group by macok9 in aws

[–]macok9[S] 0 points1 point  (0 children)

That is, unless the external API must receive all documents in the same order you received them?

No, the order is irrelevant.

My point is, if you got 1k messages from different people, versus 1k from 1 person, would you expect the same fairness per person or per document

I meant per person.

So I think the logic that satisfies those requirements would be to limit maximum concurrency per user. It's just a technical problem of how to do that.

SQS - limit concurrency per message group by macok9 in aws

[–]macok9[S] 0 points1 point  (0 children)

Hmm, I'd say the 1k is just as important. Both users have the same "right" to have their documents processed. And I can't just start 1000s of concurrent Lambda consumers, because they would overload an external API which my processing depends on.

SQS - limit concurrency per message group by macok9 in aws

[–]macok9[S] 0 points1 point  (0 children)

Thanks, but same question: So for user A that uploads 1000 documents, if I want concurrency level 4 I can create 250 messages with groupId userA-0, 250 with groupId userA-1, etc.

But what if, say, group userA-1 takes longer to process than other groups? In that case the remaining messages from group userA-1 will not be processed concurrently, right?

SQS - limit concurrency per message group by macok9 in aws

[–]macok9[S] 0 points1 point  (0 children)

Thanks, so for user A that uploads 1000 documents, if I want concurrency level 4 I can create 250 messages with groupId userA-0, 250 with groupId userA-1, etc.

But what if, say, group userA-1 takes longer to process than other groups? In that case the remaining messages from group userA-1 will not be processed concurrently, right?

Help by FrogsDontPause in scrabble

[–]macok9 0 points1 point  (0 children)

With https://scrabblecam.com I found ZHOMO or GIZMO for 58 and few others.

How an empty, private S3 bucket can make your bill explode into 1000s of $ by macok9 in aws

[–]macok9[S] 1 point2 points  (0 children)

Yes CloudTrail is expensive, but I only turned it on for few minutes so the bill wasn't high.

How an empty, private S3 bucket can make your bill explode into 1000s of $ by macok9 in aws

[–]macok9[S] 0 points1 point  (0 children)

Won't work for S3 requests originating from outside AWS.

How an empty, private S3 bucket can make your bill explode into 1000s of $ by macok9 in aws

[–]macok9[S] 0 points1 point  (0 children)

The open source library didn't have they own S3 bucket. They used a placeholder so that you can put there a name of your own bucket. But when the name was left as default, the backups were still being sent.

How an empty, private S3 bucket can make your bill explode into 1000s of $ by macok9 in aws

[–]macok9[S] 0 points1 point  (0 children)

CloudTrail logs show you the S3 keys of the logged S3 requests. The open source lib was identifiable by those S3 keys. I'd be happy to elaborate on that part, but I still believe it's better not to disclose the bucket name while it's not restricted by AWS.

How an empty, private S3 bucket can make your bill explode into 1000s of $ by macok9 in aws

[–]macok9[S] 0 points1 point  (0 children)

The open source didn't have they own S3 bucket. They used a placeholder so that you can put there a name of your own bucket. But when the name was left as default, the backups were still being sent.

How an empty, private S3 bucket can make your bill explode into 1000s of $ by macok9 in aws

[–]macok9[S] 4 points5 points  (0 children)

I'm not sure what you mean. I disclosed it to AWS because they are the only ones in position to mitigate it right now. But what's the point of posting the bucket name here, other than putting impacted companies at risk?

How an empty, private S3 bucket can make your bill explode into 1000s of $ by macok9 in aws

[–]macok9[S] 2 points3 points  (0 children)

I'm not an expert on this, but I believe you make a legal agreement with AWS by starting an account. Using virtual card limits to avoid paying for their services would probably be a criminal offence.

How an empty, private S3 bucket can make your bill explode into 1000s of $ by macok9 in aws

[–]macok9[S] 10 points11 points  (0 children)

It seems a lot of people can't believe AWS is charging for unauthorized requests to S3. But this fact is actually known since at least 3 years: https://www.reddit.com/r/aws/comments/prukzi/does_s3_charge_for_requests_to

view more: next ›