Welcome to the second blog post about our new 4DIdentity service. In the first blog post, we reviewed our motivation to create this internal service and its architecture. Brief summary: We use it to enable single sign-on for internal applications and future managed services. 4DIdentity is based on the Amazon Cognito service from AWS. We consciously chose to run it completely serverless, highly resilient, fully manageable and built using Infrastructure as Code (IaC).
In this blog post series, we want to give you a sneak peek into how we develop and maintain our applications. We have recently developed an internal service called 4DIdentity. This service acts as our central identity provider for internally used tools like ArgoCD and HashiCorp Vault. We also plan to use it in our future managed service offerings, so stay tuned! When developing the 4DIdentity service, we leveraged a set of best practices.
Yesterday was an exiting day for the swiss IT industry with the opening of the new swiss AWS region eu-central-2; AWS being the last of the three largest cloud providers to open a region in Switzerland. What will change for Swiss customers? Even though AWS has had a presence in Switzerland for quite a while now, Swiss customers had to use a non-local regions. This has now changed, and we believe that the Swiss AWS region will grow quickly; as many Swiss companies will move their workloads into the AWS cloud, many from other, local cloud providers, since the option now exists to keep data within Switzerland itself.
Once more a great and inspring event, where many contributors of #opensource presented their current work and projects. It was a success and we achieved our goals: attended the keynotes and many breakout sessions at the #cncf #kubecon 2022 in Valencia collected cool t-shirts and stickers got inspired by the community of #opensource enjoyed great food, drinks and the spirit of the city total steps count (4 days): 62'728 average hours of sleep: 5h helped to offset our flights at #myclimate
