This article gives a brief description of what you need to do with your AWS account and what information you are required to submit to Alphaus in order to enable the Hourly Report Analysis.
The information to be submitted to us after the whole setting are as follows. Please be noted to write down the necessary information at each stage in the setting process (You can still check the information after the setting is done).
- Ripple login ID (Email address)
- AWS account ID (12 digit numbers)
- Information of the created report
- Report name
- S3 bucket
- Report path prefix or report path
- IAM Role ARN
(eg. arn:aws:iam::xxxxxxxxxxxx:role/crossacounnt-access-for-alphaus)
Step 1. Create S3 bucket and Hourly Reports (optional)
First, you need to create Hourly Reports with an AWS account of which you will be sharing your billing information. Please do not include information that you do not wish us to view.
If you already have a report definition that meets the following criteria, you may skip this step.
Step 1-1. Create an S3 bucket
Create a bucket with any name from the S3 Console. The option can be the default. Please be reminded to make a note of the bucket name so that you can use it as the output destination for the report.
Step 1-2. Create an Hourly Report
From the AWS Management Console, open Billing and move to the Cost & Usage Reports Menu.
Now we are proceeding to create a report.
Fill in [Step 1] as follows, and proceed to the next step.
Report Name: arbitrary resources
Include Resource ID: Check
Automatic Refresh CUR: Check recommended
In [Step 2: Delivery Options], you may follow the following steps to include operations on your S3 bucket.
Click the S3 bucket name setting button, select an existing bucket in [Step 1/2: S3 Bucket Setting], check the policy confirmation in [Step 2/2: Confirm Policy], and save.
Confirm that "Valid Bucket" is displayed in the verification, and proceed with the following settings.
Report Path Prefix: Optional: Usage Time Detail: Hourly Report Versioning: Create New Mail Version: Enable Report Data Integration: Unchecked Compression Type: Select GZIP or ZIP *When Report Data Integration is enabled, it may not properly.
Confirm that the details displayed in [Step 3: Confirm] are correct and complete.
Step 2. Create an IAM role to delegate read permissions
Open the IAM Service on the AWS Management Console and move to the Roles and then Create Role Menu.
Under {Select Trusted Entity Type}, select Another AWS Account and enter the Alphaus account ID below;
Alphaus Account ID: 131920598436
On the Attach Permission Policy Menu, select Create Policy.
As the Create Policy Menu opens in a separate tab (window), select JSON as the input format and enter the policy with the following details.
Replace the
{replace_to_report_bucket}part of the resource with the bucket name you want to use for your report.
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:Get*",
"s3:List*"
],
"Resource": [
"arn:aws:s3:::{replace_to_report_bucket}",
"arn:aws:s3:::{replace_to_report_bucket}/*"
]
}
]
}Proceed to Check Policy and enter the following items to create a policy.
Name: Any (*Required)
Description: Optional
Go back to the Create Role Menu and refresh the list to see the policy you just created. If everything seems fine, enable the check and proceed to confirmation.
Click Next Step: Tags, and set the tag as you want.
In the Confirm menu, enter the following items:
Role Name: Any (*Required)
Role Description: Optional
Make sure that "Trusted Entity" and "Policies" are applied before creating a role.
Take a note of the ARN of the role you just created.
Hats off for your hard work!
You now have all the necessary information to register for a Ripple account.