Akira Renbokoji

11/02/2022, 10:19 PM
Hello, how do I go about setting "host" to the AWS Service Discovery for the gRPC server? workspace.yaml
 - grpc_server:
    host:  <|>
    port: 4266
    location_name: "grpc_server"
Is the above acceptable or do I need to grab the IP address from the Discovery Service then feed it into "workspace.yaml"? Edit: Turns out you can just use the namespace as host. For anyone struggling to access your Dagster site and reload the repo, you have to add your gRPC port and the HTTP port (80) to the security group associated with your Dagster setup. AWS has a Route Analyzer that you can use to see if the daemon can reach the gRPC server. That helped me the most.


11/03/2022, 8:02 AM
You can set it like your example; shouldn’t need to add the gRPC ports to the dagster setup though, just make sure the dagster security group and grpc security group can connect to each other, at least in my setup. You don’t need to your gRPC services to the internet so I’d avoid opening too many ports there.

Akira Renbokoji

11/03/2022, 4:32 PM
Thanks for the response. I just came back to say the name space works as is. It was an issue with ports being blocked in the security group as you said.