cloud-infrastructure

Describe the bug

When I create a Subnet using ec2.Subnet.from_subnet_attributes and don't specify a routeTableId, I'm getting the following warning:

[Warning at /euc1-dv-rest-alb-alb/subnet-0] No routeTableId was provided to the subnet at 'euc1-dv-rest-alb-alb/subnet-0'. Attempting to read its .routeTable.routeTableId will return null/undefined. (More info: https://github

Expected Behavior

rewriteTarget should work identical for websocket connections and none websocket connections

Current Behavior

For websocket connections, oauth2proxy does not seem to rewrite the request path before sending it to the upstream server.

Example:

...
server:
  BindAddress: 0.0.0.0:8081
  SecureBindAddress: ""
  TLS: null
upstreamConfig:
  upstreams:

Currently the machine sizes start at (and default to) m. This is fine, and a sane default for the intended use case, but not everyone needs (to pay for) 8 cores and 16GB of RAM to do something basic (like prototyping DVC/SSH features).

Right now the user can just manually specify something like aws + t2.micro ourselves but it defeats the purpose of having a generalized solution if the user