A long time coming, no more databases, VPS or wordpress installs. This move to Hugo has been a fun train of Terraforming an AWS S3 static site behind Cloudfront for TLS. Setting up Hugo to publish to S3 Doing this all in GitHub Actions. So far it’s just the content. Media and comments still need to be figured out. I still haven’t figured out the home page either. You can check it all out on GitHub.

If you’re deploying an AWS PowerShell Lambda (which is PowerShell Core 6.0) in a build pipeline, you’ll likely come across the fact that the older PowerShell docker images don’t have Dotnet Core installed. The .NET Core 3.0 .NET Core 3.0 SDK Docker images now contain PowerShell Core, but since AWS still uses .NET Core 2.1 which is in Long Term Support, you’re out of luck. Therefore if you’re deploying your lambda from your CI pipeline using docker, then you need a build environment which has:

A large increase in melanoma has been experienced in countries where chemical sunscreens are in use. This has been seen in the last decade in places such as Australia where promotion of sunscreens has been ongoing. In 1992 Queensland had more incidences of melanoma per capita than any other place on Earth.1 Not to be joked about is the result of applying sunscreen to your skin, which as an organ absorbs chemicals.

Amazon Web Services yesterday announced they now have Amazon Machine images available for Windows Server 2016. This includes Nano Server, a perfect solution for a roll your own IaaS server to host your .NET Core APIs. Windows Server 2016 Nano Server -A cloud-native, minimal install that takes up a modest amount of disk space and boots more swiftly than the Datacenter version, while leaving more system resources (memory, storage, and CPU) available to run apps and services.

Find yourself creating the same AWS Cloudformation stack a lot during testing? Wasting too much time repeating typing in tags? A simple post today with a quick solution. Put your stack tags and parameters into json files and use this bash wrapper script to create the cloudformation stack. This script wraps the aws cloudformation create-stack command, but lets you create the stacks again and again with different names. The benefit is the parameters and tags are pre-defined.

When you are building Windows Server 2012 R2 base images (vSphere Templates) using packer on vSphere (using vmware-iso packer builder); the process usually relies on the windows server to get an IP address automatically via DHCP. This allows the packer builder to then communicate to the server over WinRM and complete the provisioning. What happens when there is no DHCP available in your vSphere VM Network? The easy solution is to have the bootstrap of the windows server set a static IP for the server.

After being asked to use Visual Studio 2015 for F#{.tweet-hashtag} Development, I decided it’s way more lightweight to to develop it on my Mac using Sublime Text 3. Software you need installed: Install Mono on your Mac Of course Sublime Text 3 And the best package manager for Sublime, Package Control. Install (using package control) these packages with package control in Sublime Text: F# – Gives you syntax Highlighting F-Sharp – Autocomplete, tooltips, definitions, etc.

You’ve downloaded your purchased Windows 10 ISO from Microsoft, and you’ve managed to create a bootable UEFI USB stick. Now you’ve decided to run Windows 10 in VMWare Fusion Pro on your Mac. Yet the USB stick can NOT be booted from. There is a solution. VMWare fusion has some (unsupported) EFI options you can enable to effect a USB boot. First you’ll want to create a Windows 10 VM in VMWare Fusion.

I’ve been trying to find a production platform for Edda, the Netflix OSS app for tracking AWS resources. The application is written in Scala, which gets compiled as Java bytecode. The build toolset used by Netflix is gradle, and they deploy the application for testing into Jetty. Jetty can be used in a production environment, but the setup that comes with the build set with Edda is not really designed with a production server in mind.

Now the madness with ADFS2 SAML assertions via WS-Trust 1.3 – and how they are not valid for use with Amazon Web Services (AWS). lexx:saml$ aws sts assume-role-with-saml --role-arn $role --principal-arn $principal --saml-assertion $assertion<br /> A client error (InvalidIdentityToken) occurred when calling the AssumeRoleWithSAML operation: Responses must contain SubjectConfirmatonData with a Recipient and NotOnOrAfter This failed due to a missing Recipient attribute on the SubjectConfirmationData element. Of course; I can’t modify the assertion to add the missing Recipient; as the SAML token is signed: