https://flyte.org logo
Join SlackCommunities
Powered by
Hi everyone! I'm trying out flyte, and trying to ...
# flyte-support
l
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
f
ohh you will have to expose the 169.169... service inside the 
demo container
i think @damp-lion-88352 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
d
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 @average-finland-92144
f
@damp-lion-88352 this is not deployment
do you know how can one connect to 
pyflyte serve agent
running locally from inside the 
demo sandbox
i think we have to create some service 
node port
right?
d
oh I didn't do this before, but there's a pr from domino did similar like this before
yes you are right
l
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).
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?) But, using FlyteFile still produces
Copy code
FlyteDataNotFoundException: USER:ValueError: error=Value error!  Received: <s3://bucket-name/flytesnacks/development/2EBN75OGVBTLKCEUPBWMOYUEQU======/fast540ddedb1c401185130ce24626d7b419.tar.gz>. File not found
Any idea?
d
I think you have to add something like this
Copy code
FLYTE_AWS_ENDPOINT="<http://localhost:30002/>";FLYTE_AWS_ACCESS_KEY_ID="minio";FLYTE_AWS_SECRET_ACCESS_KEY="miniostorage"
12 Views
Open in Slack
PreviousNext
Powered by