Summary
The user is setting up a Flyte demo on EC2 and is facing issues with pods not accessing the AWS metadata service. They seek assistance in creating a service config to enable traffic from the container to the host or suggest using host networking mode as a solution. They also want to connect to pyflyte serve agent running locally from the demo sandbox. After investigation, they found that the maximum hops for the metadata service was the issue, which allowed connection to the metadata API. Currently, they are struggling with S3 URLs as the demo is incorrectly trying to use MinIO, despite removing the configuration for it.
eric901201
I think you have to add something like this
FLYTE_AWS_ENDPOINT="<http://localhost:30002/>";FLYTE_AWS_ACCESS_KEY_ID="minio";FLYTE_AWS_SECRET_ACCESS_KEY="miniostorage"
lior.greenberg
I edited the config map to remove the minio stuff and now the internal data works with my s3 bucket (is there a more persistant way to do this outside the docker?)
Anyway, i still can't download s3 files from another bucket i have (the role attached has permissions), any idea?
lior.greenberg
after some digging around, the metadata service maximum hops was the problem, it has connection to the metadata API.
The problem now is using s3 urls, the demo is forcefully trying to use minio for some reason (i removed the config for it).
eric901201
yes you are right
eric901201
oh I didn't do this before, but there's a pr from domino did similar like this before
kumare
i think we have to create some service node port right?
kumare
do you know how can one connect to pyflyte serve agent running locally from inside the demo sandbox
kumare
<@U05FFAF4FC2> this is not deployment
eric901201
tbh, I didn't spend time study how delpoyment works (I'll find time to do it) but I think this will help https://github.com/davidmirror-ops/flyte-the-hard-way/tree/main cc <@U04H6UUE78B>
kumare
i think <@U05FFAF4FC2> knows how to create a service config that allows traffic from inside the container to route to the host. you can run in host networking mode
kumare
ohh you will have to expose the 169.169... service inside the demo container
lior.greenberg
Hi everyone!
I'm trying out flyte, and trying to set up my flyte demo (running on ec2) to work with aws resources, the pods don't seem to have access to AWS metadata service. Can anyone help out? tnx