paul-e-allen
paul-e-allen
I note that this is still a problem as of this date. It would be great to have it addressed.
Also, X-Forwarded-Proto doesn't actually look to be set properly to 'https', causing havoc with URLs constructed by Rails. For my containerized Rails application running in App Runner, it sees 'http'...
Are you sure about this issue? I tested a simple deployment and found that when I deleted the `Associated-with` and `Propagated-to` tags from the VPC, STNO updated the TGW Route...
I second this approach to add ARNs whenever they exist for a resource. In my case, I was specifically surprised that aws_ec2_vpcs didn't contain an ARN field.
I second this. Users need a way to prioritize the policy checks that fail.
I am also seeing similar behavior. I use `CASC_VAULT_APPROLE` and `CASC_VAULT_APPROLE_SECRET` and get the same 403 error. I too can login to the running container and use `curl` to login...