Day 15 of my 30-Day Terraform Challenge was all about understanding how Terraform works across different provider ecosystems.
Today I explored three areas:
- AWS multi-provider modules
- Docker
- Kubernetes on EKS
Multi-Provider Modules
One of the biggest lessons from today was learning how reusable Terraform modules handle provider aliases.
Instead of defining providers inside the module, the root configuration passes them in. This makes modules much more reusable across:
- regions
- accounts
- environments
I used this pattern to deploy AWS resources across multiple regions and better understand how Terraform maps resources to the correct provider instance.
Docker with Terraform
I also worked with the Docker provider to define a local nginx container using Terraform.
This was a nice reminder that Terraform is not limited to cloud infrastructure — it can also manage local containerized workloads and other platforms through providers.
EKS and Kubernetes
The most advanced part of today was provisioning an EKS cluster and configuring the Kubernetes provider to deploy workloads into it.
I successfully created the EKS infrastructure, but I also ran into a very realistic issue:
the Kubernetes provider timed out when trying to reach the cluster API endpoint.
That challenge helped me understand an important real-world distinction:
- provisioning infrastructure is one step
- connecting workloads to it is another
Key Takeaways
Today helped me understand:
- why
configuration_aliasesmatters - how providers are passed into modules
- how Terraform can work with AWS, Docker, and Kubernetes in one workflow
- why EKS troubleshooting often goes beyond just “Terraform code”
Even though Kubernetes deployment was not fully completed, this was one of the most practical learning days so far.
Top comments (0)