> For the complete documentation index, see [llms.txt](https://docs.alphaus.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alphaus.cloud/wave-eng/mobingi-wave/introduction.md).

# Preparation

* This page explains things you need to be done on your AWS account for start using Mobingi Wave.
* After finishing preparation, you will need to give Mobingi the below informations.&#x20;

```
- AWS account ID (12 digit numbers).

- Information of the report you made.

    - Report name

    - S3 bucket

    - Report path prefix, or Report path

- ARN of IAM Role which allow the specific bucket.(Ex: arn:aws:iam::xxxxxxxxxxxx:role/crossacounnt-access-for-mobingi)
```

## Step 1 : Create S3 bucket and daily report (option) <a href="#step1" id="step1"></a>

* Create daily repot with the AWS account you want to share the billing information with Wave.
* You can skip if you already have the report definition with below conditions.

  `Time unit:` `Hourly`

  `Rsource IDsis included in the report.`

  `There is no object which Mobingi shouldn't see.(Since the access atuhority will be a whole bucket).`

### Step1-1: **Create S3 bucket**

* Create bucket with any name from S3 bucket. Option can leave as default.

  Please keep the bucket name for using it as output destination of report.

### Step1-2: Create daily report

* Choose **Billing** from AWS management console and move to **Reports**.

Click **Create report**.

![](/files/-LIOgRG3_avdKD30zae4)

* Fill out `Step 1: Select Content` same as below.
  * Report name: Any
  * Time unit: **Hourly**
  * Include: **Resource IDs**
  * Enable support for...: Optional

![](/files/-LNwmUKCPN2a-tHp6BHy)

* `Step2: Select Delivery Options` will be the following process.
  * Put S3 bucket name (you made at Step1-1)
  * Display and copy **Sample policy** (\* make sure to click after you entered S3 bucket name)

![](/files/-LNwm_N5JlakvI_PiQpw)

![](/files/-LIOjN11YZ8VXI-P4kT7)

* After copy **sample policy,** open the **S3 bucket which you create on step1-1** and open detail (\* we suggest to open the page with new window or new tab).
* On S3 page, go to **Permissions** >> **Bucket Policy.**
* Put the policy you copied at before into **Bucket policy editor** and Save.

![](/files/-LIOnVSCnSHb5s4vee-1)

Go back to `Step2: Select Delivery Options` and put below info.

* Report path prefix: Optional  (\*blank also works)&#x20;
* Compression: Optional

It shows **Valid Bucket** only when the bucket policy is correct.

Check your S3 again.

![](/files/-LNwmf-PVVBjsAW96zgi)

Check the info again and click **Review and Complete.**

![](/files/-LNwml6cxEDp0N4vglQS)

## Step 2 : Create IAM role for Mobingi <a href="#step2" id="step2"></a>

From AWS management console, select **IAM** service and click **Roles** >> **Create role.**

![](/files/-LIiFOMlOXismoU7Y_Tq)

Choose **Another AWS Account** at `Select type of trusted entity`and put Mobingi account ID.

* Mobingi Account ID: 131920598436

![](/files/-LIiGT4sBGfZ4xKWnQ9H)

Click **Create policy**.

![](/files/-LIiGvwlVshnEL6lGAek)

New tab or window will open. Choose JSON as input format and type the policy same as below. Make sure to change`{replace_to_report_bucket}` at "Resource" to **the bucket name you use for report.**

```bash
{
    "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}/*"
               ]
         }
   ]
}
```

![](/files/-LYdjugo94_Cm8941hZZ)

After fill the informations below, you can finish to create policy.

* Name: Any (\*required)
* Description: Option

![](/files/-LIiFgJCKNMA3R9_Zi3Y)

Go back to **Create Role** and refresh, the policy suppose to display on the list. Active the policy and move to review page. *\*\**

![](/files/-LIiI6Exnwh5jADTN7Dx)

At **Review**, fill the informations below.

* Role name: Any (\*required)
* Role description: Option

After check **Trusted entities** and **Policies** are correctly applied, click **Create role**.

![](/files/-LIiK5CyayelVEmWrwY1)

Keep the ARN of the role.
