Compute

1# Pure Elastic Beanstalk LoadBalanced env, exactly as heroku-to-aws generate-terraform.md emits
2# it: NO standalone aws_lb / aws_lb_listener — EB provisions the ALB from the setting blocks
3# below (LoadBalancerType=application). The static policy checker (validate-terraform-policy.py)
4# only inspects standalone aws_lb_listener blocks, so it cannot see EB's ALB. This fixture MUST
5# be POLICY_OK — and it passes the ALB TLS/redirect rules VACUOUSLY (there is no listener to
6# inspect). It documents that EB-managed ALB posture is authoring-only, not gate-checked.
7
8resource "aws_elastic_beanstalk_application" "web" {
9  name = "${var.project_name}-web"
10}
11
12resource "aws_elastic_beanstalk_environment" "web" {
13  name                = "${var.project_name}-web"
14  application         = aws_elastic_beanstalk_application.web.name
15  solution_stack_name = data.aws_elastic_beanstalk_solution_stack.web.name
16  tier                = "WebServer"
17
18  setting {
19    namespace = "aws:elasticbeanstalk:environment"
20    name      = "EnvironmentType"
21    value     = "LoadBalanced"
22  }
23  setting {
24    namespace = "aws:elasticbeanstalk:environment"
25    name      = "LoadBalancerType"
26    value     = "application"
27  }
28  setting {
29    namespace = "aws:autoscaling:launchconfiguration"
30    name      = "InstanceType"
31    value     = var.instance_type_web
32  }
33}
34
35data "aws_elastic_beanstalk_solution_stack" "web" {
36  most_recent = true
37  name_regex  = "64bit Amazon Linux 2023 (.*) running Python 3.12"
38}