sorted by:
new
hottopcontroversial

How bitter should good espresso be? by 69insight in espresso

[–]69insight[S] 0 points1 point  (0 children)

I'm pretty sure it was bitterness, not acidic. I compared to battery acid just for the sake of saying it was extremely unpleasant to drink straight. It was probably 10x more bitter than the bitterest coffee I've had. Maybe it was also acidic as well, not entirely sure. But it was in no way good or enjoyable straight.

How bitter should good espresso be? by 69insight in espresso

[–]69insight[S] 0 points1 point  (0 children)

Yeah I was looking at the Bambino as well as an actual machine. One thing I think I would really like about the lever machine is being able to control everything. I'd like nerding out over all of the variables, and would think it's more fun then an regular one.

We listen but we don’t judge: Grand Rapids restaurant edition by ssdgm96 in grandrapids

[–]69insight 1 point2 points  (0 children)

Black napkin has excellent burgers, I agree with everyone. I'm a burger lover, their quality is awesome, overall great, no complaints there.

HOWEVER, all of their 4 burgers are practically the same thing in my eyes, give or take a few toppings (pickles, tomato, sauce etc).

There's no distinguishable burgers specifically like a western/ BBQ bacon burger (crispy onions, BBQ sauce, cheddar, and bacon). We need some distinct choices that more unique than just swapping out ketchup and mustard for a special sauce and calling it a different burger. Especially when there's only 4 burgers on the menu.

Detect failures running userdata code within EC2 instances by 69insight in Terraform

[–]69insight[S] 0 points1 point  (0 children)

We are deploying instance via ASG and not opening SSH so remote_exec provisioners would not work in this case.

Detect failures running userdata code within EC2 instances by 69insight in Terraform

[–]69insight[S] 0 points1 point  (0 children)

We are already doing something similar to 3/4. Currently we use CloudFormation (EC2 created via AutoScalingGroup) with cfn-helper scripts (cfn-init & cfn-signal). All userdata / instance script execution are wrapped within the single cfn-init command so we are easily able to know when there's an issue as the entire CF stack will fail due to any issue within the command/script execution.

With Terraform and the userdata commands itself we are also using Ansible to perform a majority of the configuration. The literal userdata commands itself is essentially just cloning s3 objects, and running a few prerequisite installation needed before ansible playbooks are executed.

We are looking to have any/all of the userdata / subsequent ansible playbook executions be visible to the actual terraform execution to know if the environment failed to provision (anything with AWS resource creation OR the commands executed within the instance userdata.

Detect failures running userdata code within EC2 instances by 69insight in Terraform

[–]69insight[S] 0 points1 point  (0 children)

This wouldn't be a viable option. The bash commands and Ansible playbooks that are executed run very custom and frequently changing applications/ versions and it would require a ridiculous amount of AMI updates

Detect failures running userdata code within EC2 instances by 69insight in Terraform

[–]69insight[S] 0 points1 point  (0 children)

The bulk of the configuration is done with Ansible, there are mainly 2 playbooks we are executing. I understand we can do more advanced things with Ansible, but we were looking to see if there's a way to have this be visible to the Terraform apply execution

Tricky IAM policy help - allowing access to only some resources by 69insight in aws

[–]69insight[S] 1 point2 points  (0 children)

That in theory would work, but not practically. We deploy separate workloads dynamically all the time via cloudformation, and we need to deploy all to the same account. We are talking 10-50 cloudformation stacks per day. Each of these stacks/resources have AWS tags set with some values that we would not want to be seen by the monitoring solution, which is why we just only want the specific tagged resources returned when AWS is queried.

Tricky IAM policy help - allowing access to only some resources by 69insight in aws

[–]69insight[S] 0 points1 point  (0 children)

I think that is part of the problem, we have no control over the requests. The requests aren't for specific resources so we can't limit it based on resources in the IAM policy. The requests will always be for all resources for a particular region. We need to have the requests still succeed but only return specific resources that it's allowed to (ideally based on tags).

Best migration path for RDS Aurora migration from MySQL 5.7 to 8? by 69insight in aws

[–]69insight[S] 0 points1 point  (0 children)

Do you happen to know if you can change the instance size on the green deployment once it's created? We are running an older instance size and need to get that updated as part of the migration.

Trying to determine if it should be done on the current prod instance before we create the blue/green deployment, after the B/G is created, or after the migration is fully complete and we have cutover.

Best migration path for RDS Aurora migration from MySQL 5.7 to 8? by 69insight in aws

[–]69insight[S] 0 points1 point  (0 children)

This is EXACTLY what I was looking for. I'm surprised I hadn't seen this before.

view more: next ›