---
title: "AWS Cloud Usage"
slug: "amazon-web-services-aws"
updated: 2023-04-17T20:23:05Z
published: 2023-04-17T20:23:05Z
canonical: "docs.gogenuity.com/amazon-web-services-aws"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gogenuity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# AWS Cloud Usage

AWS Permissions Documentation

Step 1: Login to AWS Console

![](https://lh3.googleusercontent.com/6WVh3D4wdnWgQRj07SUSpIobqZgvYXw3ZWkgqL1o8wQNErfseBgypSecdREIDRVPUZkOxRVoCroIzbqEsldigHurfG6XUHuJQHORDTD5eqW-0GXxdHFEAKn9slmRJnOnVQ)

Step 2: Click on Services from top Navigation bar and **search for IAM**

![](https://lh6.googleusercontent.com/mLtv7KVRjEXPSJzTI7iJwMx1cRn43BeElgQlpSm4NCOMLI3Udi9wNDi0UK49urLUwF7UL8fXUO9R9DwHbkKU4AXtl_QCG44KfYRdhCKQD6puummvCpxoi62WkfQIvLWI_w)

Step 3: Go to Identity and Access Management (IAM) console

Step 4: Go to Policies tab

![](https://lh5.googleusercontent.com/G9h7d8hXew-DKR9eOFCc8E05m8dgaL7KYKCIXUppps89dFHD082Nt-febb5wO8KHQusYGGy6FK29Q1dsvzQ4N4ilvrLdyYgQAjEXN9W-uKO61r3BM2LCjqL4pi4fettUJw)

Step 5: Create new policy by clicking Create policy

Step 6: Add Billing service and give Read permissions

![](https://lh3.googleusercontent.com/Cvgu20KWAAlVLtxxVRoCjwSpMTOnn6prh6d9H-HftMQzIOE8fedJWOSJy5bUi7joA8mhg9HwdUG31dDTJcpjuLGIGCHymnrj8i3LjBs-8uzY5dX8C-GjlLeL9u-6oWml5g)

Step 7: We also need to add Cost Explorer Service in this policy, so next step is to click Add additional permissions

![](https://lh4.googleusercontent.com/ASqNK7zf6msNnIKI79I4iM78_E3a_aJ-oEjguKNdFhbUwQMKiS13CfOF1Yk4bw5kElVy_J_Dv_QYJ_106DgDH3E_DW6nkyA8BFx6UK5qi9nLS99N2A3aoi-qwyAsMrGlBA)

Step 8: Now add Cost Explorer Service with Read, write and list permissions

![](https://lh6.googleusercontent.com/uqt-DfiEC6Vhp1qUW5ZTEzojnTaSxfXXFNgI0q4dY_UJHXBICWXmt1vwnh1bjNFySByI0k8wZ1t_03Om8vT-Nf6bV-NTFQVos-X0R-eFNni4Ze966VBBdRfLVAyGdNeOxg)

Step 9: **Review the policy** and give any name to it (For example: billing_policy)

![](https://lh6.googleusercontent.com/7GLhEEPtqq5CC7bsIb0S0qiBXKAkmATIFfATjv6ql_YJ8x4fbf3vQHbblHa9aZbvCiPz45KKcXlTFA24XS9omvHBndcieeUfH2lhPzK54O7k_EWqoUamyYt0lZTn6X9aDw)

Step 10: Once the policy is created, add a User with the newly created policy.

Step 11: To create a User, click on “User” tab from IAM console.

![](https://lh5.googleusercontent.com/5fq22W1fF9UEoqhpuXaIgytlTiQxr5CnAc7ez1BqGtE9I7ZfREE47DIWTxwKE05uIhIVnhDTUfbCQV8ISBSeCYaXSx2ckRkmxLiT3LSja3xpZPWDhp1lvuEg-ph6ic4Aww)

Step 12: Click on Add user

Step 13: Add the user name and he **must have programmatic access**.

![](https://lh3.googleusercontent.com/dQJlPrHWceY5qouB3_vtUJnQnGiSt1Uv4kP7I-cv-xfB_sqavgMJLaKTxh2_Ijjc0Cz_MzOQNrVDpFAhLkwWgFWOrzDuWA4t5A6r6VhomNJBmWAfDNYfZzFTTI20tdSSfQ)

Step 14: The next step is to add permissions to the user.

Step 15: Select the newly created policy from “Attach existing policies directly” tab

![](https://lh6.googleusercontent.com/EHgPGy1tbRBGhHK0ZNtxTFzlfSW7WLtjSWQR1U2twaAc9qaYZakc1NYXY_cRfKOXYxH6fR_DjaZj_GrISDzvlUCWnsalOrYEa73pyb_3mB9o0XNRido8RNAznxrh0e1dTw)

Step 16: Adding tags to a user is optional.

Step 17: Review user details and confirm adding the new user.

Step 18: Once the user is created, it’ll give you the Access Key and Secret Key

![](https://lh5.googleusercontent.com/MdOwNdftZjJ5oTQexg0k24UqDUWWi1D0XPQEwvio6zyDItCdZ_NabBys55U5mlirXsWHsCPia-UQU-ImJpad9gIrs4FFpHKC2KxTuIPTTKzF24e_OreTTemhJVM_YW41Aw)

Step 19: Next step is to ensure that Cost explorer is enabled for the users

Step 20: Go to “My Account” from the top navigation bar of AWS console

![](https://lh3.googleusercontent.com/NEBh49RqJov0faAUwY2T3yY3ahGrUPzw2GEN7wG52QbDlN16ajUKM-xdi1ih0Xwa7fsgztTENOkX6hXTyx8cCuO1FheQiY9OzLCUi7JYvW4BkZvXcAtiBK2DFIarT6fWhg)

Step 21: Activate the IAM access to billing information

![](https://lh4.googleusercontent.com/yAtf6Ck6UJz44GnWMa3vfJSWtAn0rBaRTj5eMbWfJ7CR9Kf5zFTfj9uqj9b1BsoHxFeDaIq5vP-MkxRmJLSYgTTQz8cBUUZW2Zo4pHV6PCZaN6cYcK5xE0nIDJah7JyJ5Q)

Step 22: The last thing you need to identify is to detect the Default Region of your AWS account. Mostly, the default account is “ US East (N. Virginia) -- us-east-1”.

For more information on how to detect the AWS region, please read [https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-plan-region.html](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-plan-region.html)

This completes the process to create permissions and a user for integrating AWS with Genuity. **Please note,** if you make any changes after the generation of the keys, the integration will not work. Access keys can be obtained from your AWS console by navigating to IAM Service > Users > Select particular user > Security credentials.