terraform-provider-azuread VS terraform-provider-aws

There are different Terraform Providers that enable Terraform to interact with Microsoft Azure. The most common one are Azure Stack, AzureDevops, AzureRM, AzAPI and AzureAD.. In this tutorial, we use the AzureRM Terraform Provider. Let's create a Terraform file for the AzureRM Terraform Provider.

It can be for anything. Here is the provider for Azure Active Directory. It looks like it has over a million downloads this week alone so someone is using it..

Since the provider doesnt currently support licensing on [users directly](https://github.com/hashicorp/terraform-provider-azuread/issues/745) i think the only other option is to create a group that maintains specific licenses for user-members... however, that seems to be pay-walled behind Business Premium or azure ad p1

Not officially supported yet: https://github.com/hashicorp/terraform-provider-azuread/issues/68

The support for privileged identity management in Terraform is very limited. One open issue that tracks it is https://github.com/hashicorp/terraform-provider-azuread/issues/547

Source: https://github.com/hashicorp/terraform-provider-azuread/blob/main/internal/services/directoryroles/directory_role_resource.go

I haven't particularly worked with this, but if you're looking for things to see before doing, I would recommend looking at the examples provided by Microsoft: https://docs.microsoft.com/en-us/azure/developer/terraform/ and read through the provider documentation to see the individual pieces: https://registry.terraform.io/providers/hashicorp/azuread/latest/docs

⚠ There is currently an issue where the additional_configuration block order causes differences when applying the Terraform configuration without making any changes.

For Terraform, instead, a new version of the AWS module supports a dedicated resource.

If we check the support for the Terraform AWS Provider here (state for the date of publishing this article), we will see that the service is not yet fully supported. Last week, after more than half a year, support for creating a policy store was added. Additionally, we have the configuration to add template policies. However, the identity source is in the form of a PR draft, and there is no PR yet for the ability to create policies.

https://github.com/hashicorp/terraform-provider-aws/issues/3...

The size is what you get when you add every single AWS Go client into one binary.

Each service client like 1-2MB. But when you have 200 services....

Issue with EC2 Instance Metadata running inside Container

Well, at least we now have a promising lead. Some diligent googling and browsing through Github issues in the AWS provider project yielded no directly related findings. However, I did come across a few recent bug reports about the recent change AWS made regarding the treatment of public buckets. And interestingly, they described precisely the behavior I was encountering.

Latest version of TF but seems to be same Issue as this which has already been submitted : https://github.com/hashicorp/terraform-provider-aws/issues/10611

Look at this; I think the provider is just screwed up: https://github.com/hashicorp/terraform-provider-aws/issues/28672