<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Iam on Dev &amp; Platform Engineering Hub</title><link>https://rhidayat.work/topics/iam/</link><description>Recent content in Iam on Dev &amp; Platform Engineering Hub</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Rachmat Hidayat</copyright><lastBuildDate>Sun, 09 Aug 2026 17:20:00 +0000</lastBuildDate><atom:link href="https://rhidayat.work/topics/iam/index.xml" rel="self" type="application/rss+xml"/><item><title>Crossplane Ep 2: Providers and Credentials</title><link>https://rhidayat.work/series/crossplane/fundamental/02-providers-and-credentials/</link><pubDate>Sun, 09 Aug 2026 17:20:00 +0000</pubDate><guid>https://rhidayat.work/series/crossplane/fundamental/02-providers-and-credentials/</guid><description>Crossplane is useless on its own. To orchestrate AWS, Azure, or GCP, we must install Providers. In this episode, we install the official Upbound AWS Provider, configure Kubernetes Secrets to store our IAM credentials, and bind them to a ProviderConfig.</description></item><item><title>Terraform Ep 2: Providers, Plugins, and Secure Authentication</title><link>https://rhidayat.work/series/terraform/fundamental/02-providers-and-authentication/</link><pubDate>Sun, 09 Aug 2026 09:20:00 +0000</pubDate><guid>https://rhidayat.work/series/terraform/fundamental/02-providers-and-authentication/</guid><description>Terraform itself cannot create an AWS EC2 instance. It relies on &amp;lsquo;Providers&amp;rsquo; (plugins) to translate HCL code into cloud-specific API calls. In this episode, we connect Terraform to AWS and establish a secure, production-grade authentication mechanism.</description></item></channel></rss>