One of my goals for this year was to write 3 blog posts. This is my third post. One could argue that a year in review kind of content is cheating, just something to beat the goal I set; or that I’m following the trend, after all everyone and everything is doing a 2023 retrospective now. And I could agree with that. It is partly true. But it is also true that I’ve done it anyway, in my own mind, remembering the nice things that happened and the things I set out to do but didn’t. And I think it’s a good thing to remember your year. Just like we do at the end of our Scrum Sprints: think about what went well and you want to do more of, but also what was not good so that you can improve on the bad things.
Posts for: #Aws
Unit tests for AWS CDK
I recently started using AWS CDK in a project that I’m now contributing to at work. It is a new experience for me, this tool. I’ve turned a blind eye to it for some time as a result of bad experiences in the past. Not with AWS CDK itself, mind you, but with the concept.
The basic premise of AWS CDK is that you can use the power of a programming language to describe your infrastructure.
AWS CLI with Okta SSO
Summary
This page explains how to authenticate AWS CLI with Okta SSO. These instructions assume the use of fish shell.
Pre-requisites
Have these tools installed before proceeding:
How to
Configure an IDP account under the alias my-account:
$ saml2aws configure \
--idp-account my-account \
--idp-provider Okta \
--url https://example.okta.com/home/amazon_aws/0a1b2c/000 \
--username [email protected] \
--role arn:aws:iam::1234567890:role/my-role \
--region eu-central-1
The command above will create a new entry in the file ~/.saml2aws. The file
should look like this: