Step 1
Skip to Step 4 if you came to this guide from the Cross-account role connection page.
Navigate to the ‘Account Manager’ tab.
Your Account Manager menu will look like the picture below if you don't have any accounts. Click the ‘Add environment’ button.
Your Account Manager menu will display differently if you already have some accounts. Click the ‘Add environment’ button.
Choose AWS cloud service.
Step 2
Select ‘Cross Account Role.’
Step 3
You will be directed to the ‘Cross-account role connection’ page.
Step 4
In the first field, enter an Account name. You can use a specific name (up to 32 characters) or leave it as the default ‘AWS.’
Step 5
Choose the Access type (The selected type will be marked with a white dot on a blue background):
Read/write: This allows you to use all functions, such as converting to spot, scheduling resources, removing unused resources, and rightsizing your resources.
Read-only: This only lets you view your resources and possible actions, without the ability to use the main functionality.
In this case, we select the Read-only access type
Step 6
Select the Connection type (The selected type will be marked with a white dot on a blue background):
CloudFormation stack: The ARN role is automatically created by the CloudFormation stack.
Manual: You'll manually create a role using the External ID and Account ID.
In this case, we select the Manual connection type
At this moment, we've selected the Manual connection.
Do not refresh this page during account connection! It will change the External ID!
Step 7
Login to AWS Console.
Step 8
In the search field, type Cost and Usage Reports and click.
Step 9
After the page is loaded, click on the button Create report.
Step 10
Name your report, check to Include resource IDs and Refresh automatically boxes. Then click Next.
You can enter any name but with our prefix. Example: "psl-cur-{new-report}".
The part in {bold} can be changed
Step 11
Click Configure.
Step 12
Name S3 as psl-cur-%AWS-account-id% (paste your account ID instead of %AWS-account-id%), and select the region where you want to save the S3 bucket.
Step 13
Check the box The following default policy will be applied to your bucket and click Save.
Step 14
Name the S3 path prefix as psl-cur, and check the Overwrite existing report Radio button. Then check the Amazon Athena box and click Next.
Step 15
Scroll to the bottom of the page and click Create Report.
Step 16
Go back to Uniskai and click on the Open AWS CONSOLE button.
Step 17
Navigate to Policies on the sidebar and click Create policy.
Policy Read-only
Policy Read-only
{
"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 18
Get back to AWS select the JSON tab and paste the policy below, instead of
%bucket_name% enter the created S3 bucket name. Then click Next.
Step 19
Name your policy and scroll down.
Step 20
Click Create policy.
Step 21
Navigate to Roles on the sidebar and click Create role.
Step 22
Choose the AWS account entity and scroll down after that choose Another AWS account.
Step 23
Get back to Uniskai and find your generated Account ID and External ID.
Step 24
Paste your Account ID. Check Require external ID, and paste the External ID. Then click Next.
Step 25
Type the Policy name created on step 14 in the search bar and check it.
Step 26
Type ReadOnlyAccess in the search bar and check it. Then click Next.
Step 27
Come up with any Role name and scroll down.
Step 28
Click Create role.
Step 29
Click View role.
Step 30
Copy ARN-role.
Step 31
Paste ARN-role on Role ARN field in Uniskai. Now you can finally press Connect Account.
