Hello CloudMakers!

I have some exciting news to share with you all. I am thrilled to announce that I have been nominated as an AWS Ambassador! 🤩 For those of you who may not be familiar with this, let me provide some background.

An AWS Ambassador is an employee of AWS Partners, passionate about contributing to the community, and interested in working closely with customers implementing AWS Workloads. AWS Ambassadors are considered an extension of the AWS team; they are recognized leaders in the AWS community and are dedicated to helping others learn about AWS through community engagement, content creation, and speaking engagements. As an ambassador, I will have the opportunity to collaborate with other like-minded individuals, help to shape the future of the AWS community and provide guidance to those who are just starting out on their AWS journey.

There are just 275 AWS Ambassadors in the world and I am honored to have been nominated for this role! I am looking forward to sharing my journey with you all.

And now, back to business! Today we shall see:

• how to write Terraform code for unsupported resources

• Lambda anti-pattern to avoid carefully

• sync 10,000 Argo CD applications in one shot

Enjoy!

Writing Terraform for unsupported resources: Terracurl

Terraform is a really powerful tool for automating the creation and management of infrastructure resources across multiple cloud providers and platforms. To do this, it uses something called a "provider" which is like a wrapper around the target APIs, allowing Terraform to communicate with them. However, there may be times when the target API has a resource that isn't implemented in the Terraform provider yet. When that happens, you can still use Terraform with a provider called TerraCurl, which allows you to make API calls in your Terraform code. Managed API calls store the response in the state file, and unmanaged API calls make the API call every time Terraform is run. TerraCurl is designed to help in situations where the platform-native provider doesn't support the resource you need, but it's not meant to replace the platform-native providers, which are still the preferred option.

Please avoid these Lambda anti-patterns

Serverless technologies are supposed to make cloud development faster, cheaper, and more reliable, but if you design your serverless app poorly, it could actually end up being the opposite. AWS Lambda is considered the most useful building block for serverless apps in AWS, but you can’t always use it, and sometimes… you shouldn’t. This article contains an interesting section about Lambda anti-patterns that is worth reading!

Sync 10,000 Argo CD Applications in One Shot 😵

Some fellow engineers conducted experiments on the scalability of Argo CD, specifically looking at how many Argo CD Applications could be supported while maintaining reasonable performance. They found that with thousands of Argo CD Applications, CPU performance easily became a bottleneck, causing syncing delays from upstream git repositories to downstream Kubernetes clusters. To address this issue, they tried various solutions such as reducing computational requirements, increasing computing power, and expecting longer syncing delays. Ultimately, they were able to sync 10,000 Argo CD applications in 35 minutes! I found very interesting this article about their experience and insights towards achieving these numbers.

Thank you for reading my newsletter!

If you liked it, please invite your friends to subscribe!

If you were forwarded this newsletter and liked it, you can subscribe for free here:

Have you read an article you liked and want to share it? Send it to me and you might see it published in this newsletter!

Interested in old issues? You can find them here!