Terraform code for Leverage Reference Architecture for AWS, designed under optimal configs for the most popular modern web and mobile applications needs.
Cost details (includes details of unsupported resources and skipped projects due to errors)
```
──────────────────────────────────
131 projects have no cost estimate changes.
Run the following command to see their breakdown: infracost breakdown --path=/path/to/code
──────────────────────────────────
2360 cloud resources were detected:
∙ 615 were estimated
∙ 1629 were free
∙ 116 are not supported yet, see https://infracost.io/requested-resources:
∙ 42 x aws_identitystore_group_membership
∙ 23 x aws_identitystore_user
∙ 10 x aws_guardduty_member
∙ 8 x aws_ssoadmin_permission_set
∙ 7 x aws_identitystore_group
∙ 5 x aws_fms_policy
∙ 5 x aws_s3_bucket_lifecycle_configuration
∙ 4 x aws_guardduty_detector
∙ 2 x aws_guardduty_organization_admin_account
∙ 2 x aws_guardduty_organization_configuration
∙ 2 x aws_organizations_delegated_administrator
∙ 1 x aws_eks_access_entry
∙ 1 x aws_fms_admin_account
∙ 1 x aws_organizations_organization
∙ 1 x aws_route53_resolver_firewall_domain_list
∙ 1 x aws_route53_resolver_firewall_rule
∙ 1 x aws_route53_resolver_firewall_rule_group
```
What?
The leverage CLI and ref-arch are compatible with both 1.3.5 and 1.5.0 terraform versions.
Why?
With the current pins, we are locking the layers to 1.3.(x >= 5) only.
Ref
https://github.com/binbashar/leverage/issues/272