Step 1
Skip to Step 5 if you came to this guide from the Cross-account role connection page.
Navigate to the ‘Account Manager’ tab.
Your Account Manager menu will appear as shown below if you don't have any accounts. Click the ‘Add environment’ button.
Your Account Manager menu will display as shown below if you have existing accounts. Click the ‘Add environment’ button.
Step 2
Click on the AWS (Amazon Web Services) button.
Step 3
Click on the ‘Cross Account Role’ (which allows access through IAM roles) button.
Step 4
You will be directed to the ‘Cross-account role connection’ page.
Step 5
In the first field, enter the Account name. You can use a specific name, or it will be named by default as ‘AWS,’ with the specific name not exceeding 32 characters.
Step 6
Next, select the Access type:
Read/write: Allows you to use all functions such as converting to spot, scheduling resources, removing unused resources, and right-sizing your resources.
Read-only: Allows you to only view your resources and possible actions but does not provide access to the main functionality.
In this case, we select the Read-only access type
Read only policy
Read only policy
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "VisualEditor0",
"Effect": "Allow",
"Action": [
"pricing:*",
"ce:DescribeCostCategoryDefinition",
"ce:GetRightsizingRecommendation",
"ce:GetCostAndUsage",
"ce:GetSavingsPlansUtilization",
"ce:GetReservationPurchaseRecommendation",
"ce:ListCostCategoryDefinitions",
"ce:GetCostForecast",
"ce:GetReservationUtilization",
"ce:GetSavingsPlansPurchaseRecommendation",
"ce:GetDimensionValues",
"ce:GetSavingsPlansUtilizationDetails",
"ce:GetCostAndUsageWithResources",
"ce:GetReservationCoverage",
"ce:GetSavingsPlansCoverage",
"ce:GetTags",
"ce:GetUsageForecast",
"cur:DescribeReportDefinitions",
"compute-optimizer:GetEBSVolumeRecommendations",
"compute-optimizer:GetLambdaFunctionRecommendations",
"ebs:ListSnapshotBlocks",
"ebs:ListChangedBlocks",
"bedrock:GetModelInvocationLoggingConfiguration",
"bedrock:ListProvisionedModelThroughputs",
"bedrock:GetProvisionedModelThroughput",
"bedrock:ListModelCustomizationJobs",
"bedrock:GetModelCustomizationJob",
"bedrock:ListCustomModels",
"bedrock:GetCustomModel",
"bedrock:ListKnowledgeBases",
"bedrock:GetKnowledgeBase",
"bedrock:ListAgents",
"bedrock:GetAgent",
"bedrock:ListDataSources",
"bedrock:GetDataSource",
"bedrock:ListAgentAliases",
"bedrock:GetAgentAlias",
"bedrock:ListAgentVersions",
"bedrock:GetAgentVersion",
"bedrock:ListAgentActionGroups",
"bedrock:GetAgentActionGroup",
"bedrock:ListAgentKnowledgeBases",
"bedrock:ListTagsForResource",
"memorydb:DescribeSnapshots",
"memorydb:DescribeSubnetGroups",
"memorydb:DescribeReservedNodes"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"s3:GetObject"
],
"Resource": "arn:aws:s3:::%bucket_name%/*"
}
]
}
Step 7
Then, select the Connection type (The chosen connection will be indicated by a white dot against a blue background.):
CloudFormation stack: ARN-role will be automatically created by the CloudFormation stack.
Manual: You will manually create a role using the External ID and Account ID below, giving you full control over creating policies and ARN roles.
Step 8
At the moment, we choose the CloudFormation stack.
Step 9
After selecting the CloudFormation stack, select the region where you want to place the S3 bucket with CUR and click “Launch now”. If you already have an S3 bucket with CUR in some regions, we will not create a new one, we will use your S3 bucket.
If you return to Uniskai while adding an account, you will see a pop-up window
Step 10
Sign in to the AWS Console.
Step 11
You will see the Quick Create stack page.
Step 12
Scroll down to the bottom of the page and select the checkboxes
Step 13
Navigate to the next page:
Step 14
Wait until the stack's status becomes “CREATE_COMPLETE” and return to Uniskai, the account will be added automatically. You can view the connected account on the Account Manager page.
