Create an IAM User and IAM Access Key with Crossplane
<p>Hello! This is a continuation of my previous article that gives a brief overview on how to get started with <strong>Crossplane</strong>.</p>
<blockquote>
<p><a href="https://medium.com/@mumustafa899/manage-your-infrastructure-with-crossplane-%EF%B8%8F%EF%B8%8F-692c97c7d829" rel="noopener"><em>Manage your Infrastructure with Crossplane</em></a><em>.</em></p>
</blockquote>
<p>In this tutorial, we’ll cover the following key points:</p>
<ol>
<li>Understanding Providers and Provider Families</li>
<li>Installing the AWS IAM Provider and using it to create an IAM User</li>
<li>Getting Sensitive Data from Resources</li>
</ol>
<h1>Upbound Providers and Provider Family</h1>
<p>In the previous article, We observed how installing a provider enables specific Kubernetes Custom Resource Definitions (CRDs). These Kubernetes CRDs serve a similar purpose to resources in Terraform, allowing us to create and configure remote infrastructure. The AWS provider from Upbound installs around 900 Kubernetes CRDs representing resources from different AWS service such as <strong>IAM,S3, VPC, EC2, EBS</strong> etc. which puts unnecessary strain over the clusters. <strong>Upbound </strong>decided to divide these monolithic providers into smaller providers per service, which can be installed separately consuming less cluster resources.</p>
<p><a href="https://medium.com/@mumustafa899/create-an-iam-user-and-iam-access-key-with-crossplane-7257fcad1435"><strong>Website</strong></a></p>