Target Mode with Chef Server and Chef Automate It is not sufficient to provision remote devices via Target Mode but we also want an overview of node attributes, run history and changed resources. In this post we have a look at how to connect agentless resources with central servers to give us the much-needed visibility.
Getting around circular CloudFormation dependencies Several posts complain about the inability of CloudFormation to apply a Lambda event function to an S3 Bucket with an dynamically generated name. The standard UseCase is an S3 Bucket with a Lambda event notification. In this special case the Bucket has a dynamically generated name. This cannot be done by pure CloudFormation! How to work around this circular depency? Let me show you an easy way:
Agentless Provisioning with Chef One of the main points of criticism about Chef I heard over the last few years has been the need to have an agent deployed at remote machines. Sometimes that is not desired, sometimes it is not even possible. Due to this, configuring remote machines has become the stronghold of other tools - but a new feature of Chef changes the landscape fundamentally.
How to: CloudFormation Makro CloudFormation vermisst gegenüber Terraform einige Funktionen, die das Erstellen von Infrastruktur vereinfachen können. Das ist grundsätzlich korrekt, allerdings gibt es in CloudFormation die Möglichkeit, sich selber um den Einbau solcher Funktionen zu kümmern. Das geht mithilfe sogenannter CloudFormation Makros. CloudFormation Makros sind Funktionen, die wir per CloudFormation erstellen können und dann in weiteren CloudFormation Templates einbauen und verwenden können. Wir zeigen dies am Beispiel einer Count Funktion.
Introduction Recently I worked on a project with the Serverless Framework which I really like. I used it do define a serverless application for a customer that runs their workloads mostly on AWS but uses Azure DevOps to build and deploy resources. This came about because they were already building lots of .Net applications and are therefore used to VSTS, the former name of Azure DevOps. After recovering from the initial shock of having to use an Azure tool to deploy resources to AWS I gave it a chance (well, I didn’t really have a choice in the matter).
The serverless kingslayer? - Migration from serverless to CDK Last day I have been at a customer and suggested using the CDK for Infrastructure as code. He responded with a huge yes. He has worked his way through the CDK Intro Workshop aws-cdk-examples/typescript at master · aws-samples/aws-cdk-examples · GitHub and wanted to use it. Then we discussed a lambda function. The customer was using the serverless framework - like most of the people.
Was ist sind Managed Services der nächsten Generation? Die Cloud-Technologie verändert die traditionellen IT-Modelle auf verschiedene Weise - von der IT-Infrastruktur bis zur Entwicklungsmethode - und hat sogar Auswirkungen auf die Unternehmenskultur. Die Einführung von Cloud-Technologie führt somit auch zu einer neuen Art von IT-Serviceanforderungen, diese werden als Managed Services der nächsten Generation bezeichnet. Traditionelle Managed Services konzentrieren sich normalerweise auf: Patch Management Change Management Incident Management Business Continuity Security Access Management…etc .
Should we use CDK for the next project? The AWS CDK (Cloud Development Kit) is great - and still in beta - so the question for the next project would be: Should we use cdk or not? This post will look at the state of the cdk. Also we provide our CDK Templates updated to the CDK Version 0.38 if you want to get started.
