umitbuyuksahin
commented
1 year ago -
The problem is that the created role for ci tests is removed by ci-isolation while the cleanup stack is running.
-
Using different permission policies for the created role such as protected-deny-changing-protected-resource-policy could not overcome this problem.
-
ci-isolation project claims that the cleanup stack deletes all resources in the AWS account except resources prefixed with protected- or persistent-. However, regardless of the prefix of the role name (protected- or persistent-), the role is removed by the ci-isolation.
-
A ticket is created in the ci-isolation about the bug of deleting a protected role: https://github.com/exasol/ci-isolation-aws/issues/19
ckunki
Currently the aws tests fail with
botocore.exceptions.ClientError: An error occurred (ValidationException) when calling the CreateAutoMLJob operation: Could not assume role ***. Please ensure that the role exists and allows principal 'sagemaker.amazonaws.com' to assume the role.