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
Hello.
I´m working in a refactor of a project using DynamoRM in lambdas and it works fine. But in my refactor, I'm facing error while use that in cross account (lambda with lib in account B accessing Dynamo in account A).
If I do it directly with boto3, passing the proper roles created to it, it works fine.
I tried set/override boto3 configurations of DynamoRM but without success, and did not found any documentation of how do it (or if is possible).
Can you guys can answer me if is possible do it, and if yes, how, please?
If need more information about it (current code, tests done, error, etc), please let me know.
The text was updated successfully, but these errors were encountered:
@WyllianNeo I recently faced this and was able to get it to work by patching the properties on the DynamoTable3 object on initialization to force my role name to be used:
EDIT: Realizing now that this setup was used when an aws config file is present that specifies the profile details. This might not work for your use case.
Hello.
I´m working in a refactor of a project using DynamoRM in lambdas and it works fine. But in my refactor, I'm facing error while use that in cross account (lambda with lib in account B accessing Dynamo in account A).
If I do it directly with boto3, passing the proper roles created to it, it works fine.
I tried set/override boto3 configurations of DynamoRM but without success, and did not found any documentation of how do it (or if is possible).
Can you guys can answer me if is possible do it, and if yes, how, please?
If need more information about it (current code, tests done, error, etc), please let me know.
The text was updated successfully, but these errors were encountered: