nodomain

terraform state pull | grep provider | grep registry.terraform.io/- | uniq | cut -d"\\" -f2 | cut -d"\"" -f2 | sort | uniq \
  | while IFS= read -r line; do terraform state replace-provider -auto-approve ${line} ${line/-/hashicorp} ; done

nodomain

IAM policy to allow Continuous Integration user to deploy to AWS Elastic Beanstalk

IAM policy that we attach to CI users so that our CI server can deploy new versions of our applications to our EB environments without giving them too many permissions. When some permissions are missing, deploys may fail with the useless and misleading ERROR event log

Service:AmazonCloudFormation, Message:TemplateURL must reference a valid S3 object to which you have access.

(Notice that in many cases the error has nothing to do with S3 but can be caused by any missing permissions, for instance autoscaling:SuspendProcesse. Yes, it sucks.)

The policy can certainly be tightened more, it is not the most restrictive policy that works. As Kyle points out, the full EC2 rights are likely the biggest problem.

nodomain

root@pi:/home/pi# cat /var/log/dnsmasq | grep microsoft | grep 192.168.10.20 | cut -d" " -f7 | sort | uniq
activation.playready.microsoft.com
blob.weather.microsoft.com
c1.microsoft.com
c.microsoft.com
crl.microsoft.com
c.s-microsoft.com
cs.microsoft.com
c.urs.microsoft.com
displaycatalog.md.mp.microsoft.com

nodomain

Keybase proof

I hereby claim:

• I am nodomain on github.
• I am nodomain (https://keybase.io/nodomain) on keybase.
• I have a public key whose fingerprint is 0B15 D3A5 247C 3684 F2AC 50C2 8100 9D89 2FB4 A3DE

To claim this, I am signing this object:

nodomain

# m h  dom mon dow   command
* */3 * * *<--->/usr/bin/cronic /home/pi/bin/websitemonitor.sh http://url.to/monitor/