Using "--internal-alb-allow-vpc-ingress" with "copilot env deploy"

[rverpillot]

I'm trying to convert current scripts to create copilot environment to the new environment deployment feature of copilot, but I can't figure out how to translate the flag "--internal-alb-allow-vpc-ingress". When I enable this flag in "copilot env init", the environment manifest generated doesn't seem to use it, and I can't find anything in the documentation about it.

[efekarakus]

Hi Regis! 👋

Apologies, looks like we forgot to translate that flag in the manifest file 🤦
I believe what you are looking for is this field: https://aws.github.io/copilot-cli/docs/manifest/environment/#http-private-security-groups-ingress

type: Environment

http:
  private:
    security_groups:
      ingress: # Enable incoming traffic within the VPC to the internal load balancer.
        from_vpc: true

Hope this helps!

[rverpillot]

Hi Efe!

It works ! But why did you named it ingress.from_vpc ("Enable traffic from within the VPC to the internal load balancer") wheras --internal-alb-allow-vpc-ingress meant "Allow internal ALB ingress from ports 80 and 443" ??

However, it makes the job. Thank you.

[efekarakus]

I'm glad it worked!

Oh is the comment confusing? They were meant to say the same thing 😂 Both of them result ingress from within the VPC on ports 80 and 443.
We decided to name from_* to establish a pattern in the manifests:

<field>:
   from_vpc:
   from_tags: