-
Notifications
You must be signed in to change notification settings - Fork 34
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
Error "Configuration is not in effect" #9
Comments
hi, Did you set the -cors parameter when starting local dynamodb?
you can run |
Please let me know if your problem has been resolved. |
No I didn’t set the -cors parameter. Let me try with that. I will update
you.
Thanks.
…On Thursday, October 31, 2019, Yoya ***@***.***> wrote:
hi, Did you set the -cors parameter when starting local dynamodb?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#9?email_source=notifications&email_token=AA7XVFGDZ62EOCQZO3Y2DLTQRI3RVA5CNFSM4JG53PJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECWKDHQ#issuecomment-548184478>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA7XVFGUXZGGS2OOKSESD3DQRI3RVANCNFSM4JG53PJQ>
.
|
Hello, You can close this issue. Thanks once again. |
Very happy to help you |
Another way to overcome CORS trouble is to set the environment variable like the following in the compose.yml of localstack environment: |
Cors setup in local DynamoDB running in docker Initializing DynamoDB Local with the following configuration: |
Is there any other way to solve the problem? |
by the way, I can directly connect the dynamodb server by cmd: aws dynamodb get-item --table-name... |
I recommend another option to solve the cross-domain problem using a browser plugin. |
Hello,
I am trying to use this tool. I am able to run it and see the UI but when I try to add a connection to connect to local dynamodb then while applying the configuration I get an error as "Configuration is not in effect". Local dynamodb instance is running on localhost on port 8000. Please let me know how to fix this error and apply the configuration.
Thank you in advance.
Regards,
Shashikant
The text was updated successfully, but these errors were encountered: