Hey all. I’m trying to deploy metaflow but I’m get...
# ask-metaflow
s
Hey all. I’m trying to deploy metaflow but I’m getting {“message”:”forbidden”}
1
I’m using the basic, low maintenance, aws stack from outerbounds
Didn’t change anything
I’m using an ec2 instance from another vpc to do my local work, and (hopefully) shipping compute to the cloud from there
Any idea what’s going on?
It looks like there are a lot of reasons api gateway would return that, and I’m not sure where to go
v
what command you run which produces the error?
s
Running a flow
I’m on my phone because my job bans slack
But it’s… Python <path to script> run
It checks the graph, pylints then says metaflow service error
Code 403
My user has the APIGatewayInvokeFullAccess policy
v
you used the default cloudformation template (or terraform)?
s
Cloud formation
And yeah I don’t change anything
I used the parameter to add a policy to workers, but that’s about it
Also securing the api
I used that parameter too
v
ok, did you receive the auth token as described here in "Additional Configuration"
s
Yup
And I’ve added that to my config
(The value)
v
ok, so you have
METAFLOW_SERVICE_AUTH_KEY
set, right?
👍 1
s
But the value is the same as the key so…
Yup. I set it in my conf, and the environment variable
v
when you say that the value is the same as the key, what do you mean? You should receive a separate value when you run
Copy code
aws apigateway get-api-key --api-key <YOUR_KEY_ID_FROM_CFN> --include-value | grep value
s
Nope. It’s the same
v
interesting
can you try the other method:
1. From the AWS Console, navigate to Services and select API Gateway from Networking & Content Delivery (or search for it in the search bar). Click on your API, select API Keys from the left side, select the API that corresponds to your Stack name, and click show next to API Key.
s
Yeah it’s the same
v
ok, we'll get back to you soon..
👍 1
s
Thanks! I appreciate it!
a
@square-accountant-83677 can you share the screenshot that shows the value being the same as the key with me in a DM?
s
I can’t. It’s my work stuff
But I assure you, the ID and the API key are identical
I tore down the stack and rebuilt it, and again they were the same
It doesn’t look like the key is associated to the api though
It looks like that was it!
a
were you able to identify the issue
s
Yeah the key wasn’t associated
Yeah this seems to have done it
among us party 1
Thanks for the help
v
cool, great to hear that you got it fixed. Was it something that we could improve with the CloudFormation template or was it something on your side?