-
Notifications
You must be signed in to change notification settings - Fork 579
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
instance.json #642
Comments
Hi! Do you have AWS credentials you are using that are stored in your environment? Let me try this as well and make sure something didn't recently break. |
I do not, I saw the "Running locally" section in the readme and wasn't sure where I need to put that info. |
Got it! There are 2 options to do this, one with docker and one on your machine. I personally use Docker but have plans to improve the devex for building natively as well.
P.S. One tip on running docker to develop locally. First run it (notice the http envvar and the volume)
Then jump into it:
|
Thank you for the help. Now, when running invoke build, I get botocore.exceptions.NoCredentialsError: Unable to locate credentials Then the code just stops, were the 2 access key from before not the credentials? |
I'm also running on windows if that changes things |
Ok that means the credentials are not being saved or loaded - please see here for information on how to set this for every environment, https://boto3.amazonaws.com/v1/documentation/api/latest/guide/credentials.html |
when I do echo %AWS_ACCESS_KEY% or set AWS_ACCESS_KEY I see my key in the env, doesn't that mean it is saved/loadable? my whole procedure atm is |
Got it. I actually have a windows VM sitting around so let me spin that up and get back to you here. |
Same problem on Mac, tried both build-arg and env variable |
@Name404Error @Elentary the two envvars you need are this:
These can also be set in the
Similarly, these can be passed to a docker environment like this:
If none of these options are working for you, you can always download the instances.json file for any of the services directly from the website:
|
I'm experiencing the same issue trying to spin up locally on Mac. Here are my steps so far:
Could this be something to do with the permissions of the AWS User? I've created a new IAM user whose credentials I'm using with the following permissions: Perhaps there's a permissions set or other AWS setup that I'm missing? |
That's almost certainly what's happening. In the log output you should see an Access Denied error but here is the boto3 call that |
@EverettBerry Is there an example of a permission set for the IAM user that will allow spinning up localdev? The project README.md says all you need to run locally are the permissions I listed above, but that doesn't seem to actually cover what's required. Alternatively maybe I can remove elasticache from my local instance since I don't need that currently for my use case. |
I believe the permission would be: |
I also created this pull request a while back which should make it even easier to run locally using docker-compose, which is shipped as part of the Docker application on macOS. |
@cristim sorry for the delay here. I'm planning to merge these changes this month. |
Believe this was resolved in #713 |
I was trying to run the code locally and when I typed Invoke build it gave a error saying no instance.json. I was wondering what this file is and how do I get/generate it.
The text was updated successfully, but these errors were encountered: