Blog
Connecting GitLab as an AWS Identity Provider and Improving CI/CD and Security
In a previous blog post we documented our first attempt. Having learnt a bit more, this updated blog post describes our latest setup. Configuring GitLab as an Identity Provider (IdP) for AWS Our GitLab instance was previously running on a non-standard port which prevented us from using it as an IdP for AWS. We have since moved to using the standard HTTPS port and setup the IdP connection. The process was pretty straight-forward:
Creating an Event Calendar in Crystal Reports
Introduction Our recent project involved developing a Crystal Report for use with the event management software, Momentus, aimed at displaying booked events within a specified date range in a monthly/yearly calendar format. This report provides a clear overview of their availability at a glance. The following details the steps and considerations involved in achieving this dynamic solution. Requirements The report needed to: Display event context such as Budget Status (UDF) by text and Event Manager by colour.
Deploying to AWS Amplify and Lambda from Self Managed GitLab CI/CD
NOTE: Things have changed. See the latest setup in the updated blog post. Wanting to automate all of our deployments, we had to “find a way”. After some iteration, here are the final solutions. This assumes you have created the app in the AWS console and just want to be able to deploy new releases. Amplify AWS Amplify doesn’t have support for self managed GitLab instances yet. This issue is tracked on AWS Amplify Github.