We're trying to use Atlassian Performance Testing Framework with AWS and so far stuck at the provisioning stage:
1) we generate AWS access token with "aws sts get-session-token" call, user do have full administrative access to the AWS resources.
2) public network node and worker nodes are deployed fine
3) bitbucket data center cluster nodes fails to deploy failing to create IAM roles "BitbucketFileServerRole" and "BitbucketClusterNodeRole" with the "InvalidClientTokenId" error message.
I've noticed that by default testing framework expects "awscli-saml-auth" scripts to generate client tokens, however those scripts are not part of the package. Might it be the reason of the issue? Do we have to use SAML authentication to access AWS in order for deployment to work?
e3/provisioning/ProvisionStack.py needs to pass along a "RoleARN" when it calls self._aws.cloud_formation.create_stack(). Like so:
self._aws.cloud_formation.create_stack(
Capabilities=['CAPABILITY_IAM'],
RoleARN='arn:aws:iam::654321012345:role/myRole',
Parameters=template.generate_parameters(),
// etc...
The role needs to be associated with CloudFormation (e.g., "Choose the service that will use this role." during the IAM -> "Create Role" dialog in AWS Management Console).
Drilldown on the role after you've created it to get its ARN.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.