-
Notifications
You must be signed in to change notification settings - Fork 764
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Instruction to setup on AWS is not clear #44
Comments
@Jeffwan - Thanks for trying out Metaflow!
These issues will be fixed promptly in the next release. |
@Jeffwan Thanks indeed for the thoughtful feedback. |
I really like the design and feel of Metaflow so far! I'd like to get it working with AWS, and I'm also having trouble with configuration as well. I exported the environment variable:
but when I run I made sure that Also, I ran Thanks for your help! |
@anishpdalal Yes, there is a bug report for this. It should be fixed in the next release, which is scheduled in the next couple of days. Can you prepend |
Yes that worked thanks! |
@anishpdalal Yeah, you got it. The instruction needs to be improved. Same on the code side, for this case, probably check if there's no protocols, use |
Goes hand-in-hand with Netflix/metaflow-tools#3 and addresses #44
Great work! Thanks |
Goes hand-in-hand with Netflix/metaflow-tools#3 and addresses Netflix/metaflow#44
I can not successfully finish the aws setup. I use CloudFormation Template here https:/Netflix/metaflow-tools/tree/master/aws/cloudformation and it gives me all the resources I need to use here.
When I do
metaflow configure aws
, As I understand, I need to put output resources arns there. But I noticePlease enter the job queue to use for batch: -> Queue name or ARN?
Please enter the IAM role to use for the container to get AWS S3 access -> Is it
ECSJobRole
from CF outputs?Please enter the URL for your metadata service: -> Is it the
ServiceUrl
? There's another oneInternalServiceUrl
.Please enter the default container image to use -> Can not find any instruction here. I assume we at least need to have python env for the base container image?
Please enter the container registry -> should be
<account_id>.dkr.ecr.us-west-2.amazonaws.com
I would suggest to improve the doc here.
https://docs.metaflow.org/metaflow-on-aws/deploy-to-aws
The text was updated successfully, but these errors were encountered: