YoyaTeam / dynamodb-manager

A Dynamodb admin & manager GUI for DynamoDB Local and remote.
https://dynamodb-manager.netlify.app
MIT License
130 stars 34 forks source link

Error "Configuration is not in effect" #9

Closed shashikantkulkarni closed 4 years ago

shashikantkulkarni commented 4 years ago

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.

Screenshot 2019-10-30 at 11 16 42 PM

Thank you in advance. Regards, Shashikant

taydy commented 4 years ago

hi, Did you set the -cors parameter when starting local dynamodb?

-cors value — Enables support for cross-origin resource sharing (CORS) for JavaScript. You must provide a comma-separated "allow" list of specific domains. The default setting for -cors is an asterisk (*), which allows public access.

you can run java -Djava.library.path=./DynamoDBLocal_lib -jar DynamoDBLocal.jar -sharedDb to set core *, or run java -Djava.l ibrary.path=./DynamoDBLocal_lib -jar DynamoDBLocal.jar -sharedDb -cors http://localhost:8080

taydy commented 4 years ago

Please let me know if your problem has been resolved.

shashikantkulkarni commented 4 years ago

No I didn’t set the -cors parameter. Let me try with that. I will update you. Thanks.

On Thursday, October 31, 2019, Yoya notifications@github.com 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 https://github.com/YoyaTeam/dynamodb-manager/issues/9?email_source=notifications&email_token=AA7XVFGDZ62EOCQZO3Y2DLTQRI3RVA5CNFSM4JG53PJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECWKDHQ#issuecomment-548184478, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7XVFGUXZGGS2OOKSESD3DQRI3RVANCNFSM4JG53PJQ .

shashikantkulkarni commented 4 years ago

Hello, It is working as per your suggestion. Thank you. Can you please add it in your documentation so it will help others if they face this issue.

You can close this issue.

Thanks once again.

taydy commented 4 years ago

Very happy to help you

timothyjeffcoat commented 2 years ago

Another way to overcome CORS trouble is to set the environment variable like the following in the compose.yml of localstack

environment:

First-Met commented 1 year ago

hi how to reslove this issue? thanks I have set the Param "- cors ",but didn't resloved. java -jar DynamoDBLocal.jar -sharedDb -cors '' -dbPath ./data -port 8001 Port: 8001 InMemory: false DbPath: ./data SharedDb: true shouldDelayTransientStatuses: false CorsParams: *

image

ArchanaNeog commented 1 year ago

Cors setup in local DynamoDB running in docker We can set the cors while running the docker instance as shown below docker run --name dynamodb -p 8000:8000 amazon/dynamodb-local -jar DynamoDBLocal.jar -cors http://localhost:8080

Initializing DynamoDB Local with the following configuration: Port: 8000 InMemory: false DbPath: null SharedDb: false shouldDelayTransientStatuses: false CorsParams: http://localhost:8080

Stephen0910 commented 10 months ago

Is there any other way to solve the problem? dynamodb is not deployed by me, so I can't change its parameters Also, it seems that the 2.x version of dynamodb doesn't work even after changing it Is it possible to access dynamodb without changing its environment parameters, but only changing the content of the project? Best wishes.

Stephen0910 commented 10 months ago

Is there any other way to solve the problem? dynamodb is not deployed by me, so I can't change its parameters Also, it seems that the 2.x version of dynamodb doesn't work even after changing it Is it possible to access dynamodb without changing its environment parameters, but only changing the content of the project? Best wishes.

by the way, I can directly connect the dynamodb server by cmd: aws dynamodb get-item --table-name... So I think this is a bug should be fixed in dynamodb-manager.

Stephen0910 commented 10 months ago

I recommend another option to solve the cross-domain problem using a browser plugin. https://chromewebstore.google.com/detail/cross-domain-cors/mjhpgnbimicffchbodmgfnemoghjakai

z-krish commented 3 months ago

ase let me know how to fix

if your dynamo is running in 8000, why cors of 8080 should be done?