Open Yivensky opened 3 days ago
First of all: Good idea to allow non-"/"-path roles in the register account dialog. Will add it in one of the next releases.
Regarding updates: There is no safe update path of an existing deployment. The only way would be to update the Amplify code in your repo, zip & upload it to S3 and re-execute the CodeBuild project for Amplify deployment. But this will be at your own risk, it is not a documented/safe update path.
Hello, It is hardcoded that the role must be in the path / but for security reasons I add high permissive role in another path and restricted them by using SCP. However, the interface doesn't allow me to add the AWS Account because he don't find the role, because it's not in the path /
I know where I can change the code (change regex in the input and allow /, and type for exemple mypath/myrolename it would not break the code) but I am pretty bad with make and react etc...to update the deployment
My question is : In the future, for next releases, how can I update my deployment with new version of this tools and keep my settings? i tried to make deploy again to get new .zip, and create a new deployment in my amplify app and use amplify.zip, I broke the webpage
THank you