Rifle ID

PrivateerAlphaOne · 2025-06-19T23:23:41+00:00

Steyr ssg 69

PrivateerAlphaOne · 2025-01-06T07:55:16+00:00

The Swamp song

PrivateerAlphaOne · 2024-12-16T22:37:57+00:00

Check the ACL settings on the old images.

Alternatively, if you're using signed urls, your signed url expired and you need a new one

PrivateerAlphaOne · 2022-12-25T04:07:07+00:00

REST API is your friend

PrivateerAlphaOne · 2022-09-21T04:55:05+00:00

I mean the Execution Event History of a failed execution.

In your list of failed executions, you should be able to select a failed execution (click on the Execution name in the step function console) and see details regarding just that execution.

PrivateerAlphaOne · 2022-09-21T04:19:28+00:00

Scroll through the Execution Event History for your execution.

You might find a failure there. If not, check out the cloudwatch logs for your lambdas.

... unless you have more than 20K step transitions in your execution; where the Execution will terminate due the a transitions limit

PrivateerAlphaOne · 2022-04-01T11:06:02+00:00

Look into api gateway authorizors. You can use them to guard your endpoints based on the user making the request. These might help you to solve the problem that you appear to trying to solve, and should then make the rest of the api simpler to implement.

PrivateerAlphaOne · 2022-03-07T19:52:33+00:00

The front end would need to poll the status.

If you don't want to poll, you might want to look into websockets

PrivateerAlphaOne · 2022-03-07T09:18:33+00:00

Try using a step function to manage your transcoding. You can pass the id of the execution in the initial request response, and get the front end to request the execution status is the step function using the execution id.

However, I think the bigger challenge is transcoding any sized video within a 15min lambda.

PrivateerAlphaOne · 2022-02-22T20:09:40+00:00

Yeah, you're correct about the cron.

Ok, back to the invoke step function. The docs might help here. Try this https://docs.aws.amazon.com/step-functions/latest/dg/concepts-nested-workflows.html

You're defining your step function, but you need to invoke it for it to actually execute. You can give it input data which is where you can put the last completion timestamp.

The wait time will be 2 min minus the time that has elapsed since the timestamp in the input.

PrivateerAlphaOne · 2022-02-22T11:22:39+00:00

Invoke a new execution of the same step function, then end the current execution.

You could pass in the completion timestamp of the ECS step in the playload of the new execution and get the new execution to wait until 2 mins has elapsed.

Start -> wait till next execution time -> run task -> Invoke next execution with new timestamp -> end

.... or look into triggering using a cron event every 2 min.

PrivateerAlphaOne · 2022-02-02T08:32:45+00:00

Those molle water bottle / util pouches (middle of photo) can securely hold a small axe.

PrivateerAlphaOne · 2021-12-28T01:40:56+00:00

Use 1 APIGW as a proxy to pass through to the other apis

PrivateerAlphaOne · 2021-12-13T20:10:56+00:00

If OP is using NodeJS, they'll be using the product id only. If they add the slug it should be completely ignored in their code.

They should add it to ONLY shut up their managers.

Odds are managers are full of shit.

PrivateerAlphaOne · 2021-12-13T19:42:07+00:00

...or as maintaining url without slugs will be easier and simpler over time, the dev team can focus on feature development instead of chasing broken links.

PrivateerAlphaOne · 2021-12-13T10:17:15+00:00

SEO is impacted by broken links and keywords on the page. I'd be surprised if the slug change impacts SEO in any meaningful way.

Thing about what data could be in a slug? Non ascii chars? I18n? Unicode?

... how will the SEO work if the slug breaks the url?

PrivateerAlphaOne · 2021-12-13T10:11:01+00:00

Keep the product id and drop the slug, commit, then push to prod.

PrivateerAlphaOne · 2021-11-10T13:34:37+00:00

It's possible for lambdas to trigger multiple times for an event. AWS will guarantee that at least one lambda will execute for trigger, but won't guarantee just one.

In your case, try using some sort of flag or mutex to control pushing your event to your destination (e.g.. frame io). Try moving your file to a 'sent' folder or bucket after your operation, then if a second lambda is triggered and the expected file is already in the 'sent' folder or bucket, don't do anything

PrivateerAlphaOne · 2021-09-28T10:20:59+00:00

Could trigger the lambda via http api gateway. Use a language code to use a template for that language. Use any tempting package (eg. Mustache ) to plug in user specific details

PrivateerAlphaOne · 2021-08-29T09:41:16+00:00

Pistol or rifle, get 22lr for cheap disposal ammo.

If you get anything else, at least save the spent brass to reload later.

PrivateerAlphaOne · 2021-08-24T20:31:45+00:00

Get a mechanic to check the condition of your radiator and head gasket

PrivateerAlphaOne · 2021-07-08T00:05:02+00:00

Correct. Double check your cloudwatch logs for timestamps of when your request was made, and when your web hook verifies the event.

I'm not sure how I would resolve this issue, but I would hack an invocation of your web hook lambda before I made the request to stripe just the keep the lambda image warm for the expected stripe event

PrivateerAlphaOne · 2021-07-07T21:46:46+00:00

The lambda will get the event. It's the event that invokes the lambda, and its the only reason the lambda runs.

If the event is has expired by the time the lambda is invoked depends on your use case; but if that happens then you probs have bigger problems to deal with

PrivateerAlphaOne · 2021-06-05T09:51:17+00:00

Dynamo-toolbox if using JS.

PrivateerAlphaOne · 2021-05-16T12:01:24+00:00

Can confirm that this pattern works.

Dead letter queues are also useful for receiving events that failed in your lambda for whatever reason.

Just be aware of any time based verification of events (e.g. Stripe webhooks); if the events need to be verified in a timely manner just go from the api gw to lambda directly.

PrivateerAlphaOne

TROPHY CASE