Supporting Terraform Provider 4

[npalm]

Thanks to @meMuszr in #444 the initial work is done to provide support for AWS Terraform provider 4. I have merged the PR in #460 to test and fix some minors. All the work is still under test. But would like to gather feedback from the community.

• Feel free to comment on PR feat: Support AWS provider 4 #460 and provide suggestions
• Look for people that can run a test on the PR?
• Look for feedback should we already bump the module to Terraform 4.x? You always have the option to use multiple providers if really need. Please comment on the issue.

[photosojourn]

Hey @npalm hope your well. Do you have an eta for this PR being merged? No major rush, but it would allow us to avoid a work around. Thanks for the great work!

[npalm]

Since upgrade have major impact, I have crated this issue. To give the community a bit of time to give feedback. If it helps I can tag this branch so you can already start using it.

[kayman-mk]

I constantly get a warning in Security Hub that I should use IMDSv2 for EC2 instances. May be it is worth to integrate this as well? Especially as all my executers failed after switching to AWS 4.x provider (see #445)

Security Hub issue: EC2.8 EC2 instances should use Instance Metadata Service Version 2 (IMDSv2)

IMDSv2 for EC2 in Terraform

[npalm]

I constantly get a warning in Security Hub that I should use IMDSv2 for EC2 instances. May be it is worth to integrate this as well? Especially as all my executers failed after switching to AWS 4.x provider (see #445)

Security Hub issue: EC2.8 EC2 instances should use Instance Metadata Service Version 2 (IMDSv2)

IMDSv2 for EC2 in Terraform

Added a solution based on your PR #445 see #490