You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem with credentials aws account.
I created a role as required for the service, the plugin inside miro does not integrate and does not create schemes. I decided to do it via CLI, but I have a problem with the account not working. Maybe I'm doing something wrong, in the screens show the errors and what I enter.
Thanks for the answers!
The text was updated successfully, but these errors were encountered:
Hi @nonSpiritless, thanks for bringing this to our attention! We recently fixed an issue, so the integration should now work as expected. Please reuse the same role you have and let us know if it works for you! :)
The issue with the CLI method might stem from a different cause. The CLI tool depends on your terminal session's environment variables and uses the default AWS SDK auth methods. For example, if you can run commands like aws s3 ls in your terminal, you should also be able to run the cloud-data-import script.
Another suggestion is to set everything up in your terminal first. Then, when running the script, keep the AWS Profile option at its default setting, which is the automatic suggestion. Only change it if you have a specific AWS profile (differs from the role ARN) that you want to use.
Problem with credentials aws account.
I created a role as required for the service, the plugin inside miro does not integrate and does not create schemes. I decided to do it via CLI, but I have a problem with the account not working. Maybe I'm doing something wrong, in the screens show the errors and what I enter.
Thanks for the answers!
The text was updated successfully, but these errors were encountered: