Skip to content
Cloud8 logo default
  • PRODUCT
  • PRICING
  • SUPPORT
  • CONTACT US
  • LOGIN
  • PRODUCT
  • PRICING
  • SUPPORT
  • CONTACT US
  • LOGIN

Avançado

  • Creation of unified annual budgets

Best Practices

  • How to integrate Slack into Best Practices
  • How to monitor memory and swap with SSM
  • AWS Bucket S3 Topic Notification
  • Best Practices: Password and Credential Monitoring
  • Best Practices: Custom Rule Notifications via AWS S3
  • Best Practices: Microsoft Teams Support

Charging

  • AWS account suspension: tips and what to do

Cloud8 Academy

  • Configuring Budgets on Cloud8
  • Best Practices for Using Tags (Playbook)

Concepts

  • Security groups
  • Access key
  • Cloud Computing
  • Cloud Control Panel – AWS, Azure, GCP, Huawei and Oracle
  • Cost model: pay per use
  • Additional disks
  • Snapshot
  • Cloud server image or template
  • Comparison: Automation via Cloud8 vs “homemade” automation
  • FINOPS: Data Integration and Enhancement Flow (Infographic)
  • Difference between RI Applied vs RI in Cloud8 Panel

Credentials

  • How to use IAM Role to integrate your security with Cloud8
  • Security credentials for public clouds
  • Connecting OCI Providers to Cloud8 – Full Tutorial
  • Credential for Huawei Cloud
  • Best Practices: Enabling user monitoring in Azure

Features

  • How to integrate Cloud8 with Cloud Storages
  • How to export data to cloud storages
  • FinOps Analytics: Cloud Cost Analysis
  • Cost Analysis Dashboards
  • Monitoring the creation of new resources in Cloud8
  • Creating and managing Cost Management Exports
  • Configuring GCP SSO and SAML
  • Backup with “Lock/Unlock” governance
  • Tracking Consumption Patterns with Invoice – Annual from Cloud8
  • Monitoring the creation of new resources in Cloud8
  • Configuring GCP SSO and SAML
  • Using Cloud Pricing on Cloud8

First Steps

  • Connecting GCP Providers to Cloud8 – Full tutorial
  • Connecting AWS Providers to Cloud8 – Full Tutorial
  • How to manage more than one AWS account
  • Hot to enable cloud cost estimates monitoring
  • Connecting Azure Enterprise Agreement providers to Cloud8 – Full tutorial
  • Creating a New Account on Amazon Cloud (AWS)
  • Connecting OCI Providers to Cloud8 – Full Tutorial
  • Cloud8 Users and Profiles
  • Onboarding: getting started on Cloud8

MSP / Reseller

  • White label at no additional cost
  • MSP: Configuring costs
  • MSP: Configuring markup

Primeiros Passos

  • Security credentials for public clouds
  • Connecting Azure providers to Cloud8 – Complete tutorial
  • Connecting MongoDB providers in Cloud8

Services

  • FinOps: Tags and Usage
  • Using Cloud8 Insights
  • Audit logs
  • Cloud usage statistics
  • Managers on Cloud8 – Resource management on AWS, Azure and GCP
  • Alerts
  • Using Automations in Cloud8
  • Multiple Users – Multiuser Panel
  • Cloud aggregator control panel
  • Automated backup of cloud servers
  • Cloud cost control, alerts and reports
  • ECS / Fargate support on Workflow
  • Detailed Costs Report
  • Enabling Azure AD SSO in the Cloud8 Dashboard
  • Workflow: How to reset tasks periodically
  • Add TAGs with CSV file
  • How to install Metricbeat component on AKS
  • RDS reports with grouping by ID
  • Kubernetes Cost Support
  • How to install Metricbeat component on GKE clusters
  • Enabling MFA in the Cloud8 Dashboard
  • FinOps: Cost Anomaly Reports and Charts
  • How to install the Metricbeat component in OKE
  • How to install Metricbeat component on EKS
  • FinOps: Reverse API
  • FinOps: Tag Sharing and Prorating
  • FinOps: Tag Sanitization, Compliance and MultiCloud
  • FinOps: Tagged / Untagged
  • FinOps: Tags / Labels / Resource Groups
  • FinOps: Reports, Alerts and Budgets
  • S3 Lambda Notification Processor (deploy via CLI)

Troubleshooting

  • I subscribed Amazon and I still can’t access Cloud8
  • How is the cloud cost estimate calculated?
  • I created a security group through the AWS console and it still doesn’t appear in Cloud8
  • I exported the cloud server usage report. What do the fields mean?
  • Cloud8 and Amazon don’t monitor my cloud server’s memory?

Tutoriais / FAQ

  • How to integrate Cloud8 with Cloud Storages
  • How to export data to cloud storages
  • FAQ – Enable cost monitoring per pipeline in Data Factory
  • FAQ – How to test the SSO configuration?
  • Creation of unified annual budgets
  • Backup, DR, and Vault Copy with KMS

Tutorials

  • How to access a Windows server in the Amazon AWS cloud
  • How to access a Linux server
  • How to create a cloud server
  • How to integrate Slack into Best Practices
  • How to configure scheduling for script execution in AWS
  • How to configure scheduling by Tags / Labels
  • Configure vault copy at AWS (cross account) with KMS
  • How to configure the Scheduler for script execution on OCI
  • Workflow: How to reset tasks periodically
  • How to install Metricbeat component on AKS
  • How to install Metricbeat component on GKE clusters
  • How to install Metricbeat component on EKS
  • How to install the Metricbeat component in OKE
  • FinOps: Cost Anomaly Reports and Charts
  • Group data in Pivot Table
  • FinOps: Tag Sanitization, Compliance and MultiCloud
  • S3 Lambda Notification Processor (deploy via CLI)
  • Best Practices: Microsoft Teams Support
View Categories
  • Home
  • Docs
  • Features

How to integrate Cloud8 with Cloud Storages

9 min read

0:00 / 9:33
  • View as Markdown Open this page as plain Markdown (opens in a new tab)
  • Open in ChatGPT Ask questions about this page (opens in a new tab)
  • Open in Claude Ask questions about this page (opens in a new tab)
  • Open in Google AI Studio Ask questions about this page (Google account required) (opens in a new tab)

Cloud8 is a platform that centralizes and enriches data from multiple accounts and multiple cloud providers, making it easier to analyze and visualize data both independently and in a unified way. To help our clients integrate this data into their own BI systems, custom reports, or dashboards, we offer the ability to export data to storage accounts from major cloud providers.

Below you will find the necessary steps to create this integration with Amazon AWS, Google GCP, and Microsoft Azure. Jump directly to:


Cloud8 Integration with AWS S3 Bucket

Cloud8 Integration with Azure Storage Account

Cloud8 Integration with GCP Cloud Storage

Exporting Cloud8 data to a Cloud Storage Account (all supported providers)


How to integrate with an AWS S3 Bucket? #

Below is the step-by-step guide to integrating an S3 Bucket with your Cloud8 account.

  • Find the “Integrations” option in the sidebar menu;
  • Create a new integration of the “S3 Bucket” Type;
  • Specify the AWS-defined S3 Bucket name in the “Bucket” field;
  • Configure the access pair, IAM Role ARN, and External ID provided by AWS. This credential must have permissions to write, read, list, and delete files in the Bucket, according to the policy described in Required permissions in the S3 Bucket below;
  • Fill in the remaining information and finalize by clicking Save
  • This integration also works in Best Practices and “Reports” – you can create a report to be exported
AWS S3 Integration (Bucket)

Required permissions in the S3 Bucket #

The IAM Role informed in the integration needs permission to write, read, list, and delete files in the destination Bucket. The permission is granted on the IAM Role, not on the Bucket: it is the same role used in the connection from the AWS provider to Cloud8.

To attach the policy to the role in the AWS Console:

  1. Go to IAM → Roles and locate the role used by Cloud8;
  2. Under the Permissions tab, click Add permissions → Create inline policy;
  3. Select the JSON editor, clear the existing content, and paste the policy below, replacing NOME-DO-BUCKET with your S3 Bucket name;
  4. Click Next, give the policy a name (e.g., cloud8-export-s3), and finalize by clicking Create policy.

If you prefer to reuse the same policy across other roles, create it in IAM → Policies → Create policy and then attach it to the role.

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "s3:DeleteObjectVersion",
        "s3:PutObject",
        "s3:DeleteObject",
        "s3:GetObject"
      ],
      "Resource": [
        "arn:aws:s3:::NOME-DO-BUCKET/*"
      ]
    },
    {
      "Effect": "Allow",
      "Action": [
        "s3:ListBucket"
      ],
      "Resource": [
        "arn:aws:s3:::NOME-DO-BUCKET"
      ]
    }
  ]
}

Attention: the two blocks have different Resources on purpose. File actions (PutObject, GetObject, DeleteObject, DeleteObjectVersion) apply to objects inside the Bucket, which is why there is a /* at the end. Meanwhile, ListBucket applies to the Bucket itself, without the /*.

When you click Save, Cloud8 writes a test file to the Bucket to validate access. If the policy is not attached to the role, the integration will not be saved and the error “is not authorized to perform: s3:PutObject […] because no identity-based policy allows the s3:PutObject action” will appear.

Optional model: reading all Buckets #

If you already want to grant Cloud8 read access to all Buckets in the account, reusing the same role for other platform features and configurations, use the model below instead of the previous policy. It keeps writing and deleting files restricted to the export Bucket while granting read-only access to the others. Replace NOME-DO-BUCKET with your export Bucket name:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "ListarBuckets",
      "Effect": "Allow",
      "Action": [
        "s3:ListAllMyBuckets"
      ],
      "Resource": "*"
    },
    {
      "Sid": "LerTodosOsBuckets",
      "Effect": "Allow",
      "Action": [
        "s3:ListBucket",
        "s3:GetBucketLocation"
      ],
      "Resource": "arn:aws:s3:::*"
    },
    {
      "Sid": "LerArquivosDeTodosOsBuckets",
      "Effect": "Allow",
      "Action": [
        "s3:GetObject"
      ],
      "Resource": "arn:aws:s3:::*/*"
    },
    {
      "Sid": "GravarNoBucketDeExportacao",
      "Effect": "Allow",
      "Action": [
        "s3:PutObject",
        "s3:DeleteObject",
        "s3:DeleteObjectVersion"
      ],
      "Resource": "arn:aws:s3:::NOME-DO-BUCKET/*"
    }
  ]
}

Attention: with this model, the role will read the contents of all Buckets in the account, including those unrelated to Cloud8. Evaluate whether this complies with your company’s security policy before applying it. If the goal is solely data export, the previous policy is sufficient.

IAM Role #

An IAM Role is an entity in AWS IAM that defines a set of permissions for making requests to AWS services. Unlike an IAM user, which is associated with a specific person, an IAM role is intended to be assumed by any trusted entity, such as an AWS service, an application, or an IAM user. Roles are useful for granting temporary permissions and can be assumed by different entities as needed.

ARN (Amazon Resource Name) #

The ARN is an identifier that follows a unique standard format to identify resources within AWS. It is used to specify the role uniquely in policies and permissions.

Role ARN Example #

arn:aws:iam::ID-NUMERICO-AWS:role/NOME-DO-ROLE

Using IAM Role ARN with S3 #

When you use an IAM Role with S3, you can grant specific permissions to access S3 buckets and objects. For example, you can create an IAM role with permissions to access a specific S3 bucket and then configure an AWS service (such as EC2) or an IAM user to assume that role. This is useful for managing and controlling access to S3 resources in a secure and scalable way.

Why use an IAM Role ARN? #

  • Security: Allows granting temporary permissions, minimizing risks.
  • Flexibility: Can be assumed by multiple entities, facilitating permission management.
  • Scalability: Ideal for large environments where different services and users need controlled access.

How to integrate with an Azure Storage Account? #

If you haven’t done so yet, the first step is to create a Storage Account in Azure. To do this, search for “Storage accounts” in the Azure portal search bar. Click “Create”. In the Basics tab, fill in the information, and define the Subscription and Resource Group where the storage account will be created.

Define a name and region to create the resource, and under “Preferred storage type” choose “Azure Blob Storage or Azure Data Lake Storage”.

Under Performance, select “Standard”, and under Redundancy select “Locally-redundant storage (LRS)”. However, this is just a suggestion, and the redundancy setting should always align with the user’s business rules.

Finish by clicking “Review + create”. Validate the data and click “Create”.

Integrating Azure Storage

Search for the created storage account. In the left sidebar menu, look for “Containers”. Click “Add container”, specify a name, and click “Create”. Note down the name of the created container.

Integrating Azure Storage

In the left sidebar menu, locate “Access keys”. Copy the following information to a notepad:

  • Storage account name
  • Key
Integrating Azure Storage

Integrating the Storage Account with the Cloud8 Platform #

Follow the steps below to create an integration with the Azure Storage Account inside our MultiCloud Dashboard.

  • Find the “Integrations” option in the sidebar menu
  • Select “New Integration” from the first option
  • Click on “Type” and select the “Azure Storage Account” option
  • Give this integration a name
  • Fill in the required data: Storage Account Name, Storage Account Key, and Container
Cloud8 new integration

How to integrate with GCP Cloud Storage? #

If you haven’t done so yet, you first need to create the GCP JSON in the Service Account. To do this, go to the GCP Console and search for IAM & Admin. Select Service Accounts in the left sidebar menu.

Integrating GCP Storage

Under the Permissions tab, select Manage access | Add another role and choose Storage Object Admin.

Integrating GCP Storage

Return to Service Accounts and click the three-dot icon to select the Manage Keys option. Click Add key | Create new key to create a new access key if you haven’t created one yet. Otherwise, granting the necessary accesses in the previous step is sufficient.

Integrating GCP Storage

See below how to integrate GCP Cloud Storage into your Cloud8 account.

  • Find the “Integrations” option in the sidebar menu;
  • Create a new integration of the “GCP Cloud Storage” Type
  • Add a credential (JSON file of a Service Account) generated in Access Key;
  • Click “Save” and you are all set.
Cloud8 GCP Storage integration

How to integrate with Google Drive? #

Initially, you need to enable the Google Drive API within the project where the Service Account was created, using the link: https://console.cloud.google.com/apis/api/drive.googleapis.com/metrics?project=xxxxxx

You will also need a JSON file containing the service account. To do this, in the Google console, under Service Accounts, select the created service account and in the Keys tab, click Add Key, then Create new key. The Service Account does not need any roles in the project: access to Google Drive is granted directly in the Shared Drive by adding its email as a member (see below).

Connecting GCP providers to Cloud8

Select JSON, then click Create. A Private Key will be automatically generated.

Connecting GCP providers to Cloud8

Next, you need to create a Shared Drive via the link https://drive.google.com/drive/shared-drives. Click Create a shared drive.

NOTE: Shared Drives only exist in Google Workspace accounts (work or school accounts) whose edition includes the feature; free personal accounts (@gmail.com) do not have access. Even within Workspace, the organization administrator may restrict who can create Shared Drives.

If the Create a shared drive option does not appear, ask your Google Workspace administrator to create the Shared Drive or enable creation for your user. See Create a shared drive and Allow users to create shared drives.

Set a name and click Create.

Note down the Shared Drive Folder ID, which can be obtained directly from the Shared Drive URL. For example:

Example URL: https://drive.google.com/drive/folders/1AbCdEfGhIjKlMnOpQrStUv

Folder ID

1AbCdEfGhIjKlMnOpQrStUv

The ID is the sequence of characters after /folders/. Next, click Manage Members, select the Service Account email, and click Done.

See below how to integrate Google Drive into your Cloud8 account.

  • Find the “Integration” option in the sidebar menu;
  • Create a new integration of the “Google Drive” Type
  • Set a Name for the integration;
  • Add the Shared Drive folder ID;
  • Add the Service account JSON
  • Click Save and you are all set.

NOTE: Export to Google Drive occurs whenever there is new cost data, 2 to 3 times a day. The name defined in Exported file name when saving the Dashboard determines whether the file is overwritten or a new one is created:

File nameBehavior
custos.csv (fixed name)Overwrites the same file on every export
custos-YYYYMM.csvOne file per month: updates only the file for the processed month
custos-YYYYMMDDHHMMSS.csvAlways creates a brand new file on every export

Exporting Cloud8 data to a Cloud Storage Account (all supported providers)


You may want to check these Docs too: #

  • How to export data to cloud storages
  • Monitoring the creation of new resources in Cloud8
  • Cost Analysis Dashboards
  • Creating and managing Cost Management Exports
  • Configuring GCP SSO and SAML
Amazon, armazenamento, AWS, Azure, bucket, bucket s3, GCP, google, Integração, json, Microsoft, storage, Tutorial
Did this Doc help you?

Share This Article:

  • Facebook
  • X
  • LinkedIn
  • Pinterest
Table of Contents
  • How to integrate with an AWS S3 Bucket?
    • Required permissions in the S3 Bucket
      • Optional model: reading all Buckets
    • IAM Role
    • ARN (Amazon Resource Name)
      • Role ARN Example
      • Using IAM Role ARN with S3
      • Why use an IAM Role ARN?
  • How to integrate with an Azure Storage Account?
    • Integrating the Storage Account with the Cloud8 Platform
  • How to integrate with GCP Cloud Storage?
  • How to integrate with Google Drive?
Cloud8 logo default
  • Terms of Use
  • About Us
  • FAQ / Support
  • Blog
  • Contact Us
  • Cookies (EU)
  • Terms of Use
  • About Us
  • FAQ / Support
  • Blog
  • Contact Us
  • Cookies (EU)
Globe-americas Facebook Twitter Linkedin Youtube

Disclaimer: AWS, images, and associated services are property of Amazon Web Services Inc. and its affiliates. Azure, images, and associated services are property of Microsoft Corporation. GCP, images, and associated services are property of Google Inc. Huawei, images, and associated services are property of Huawei Technologies Co Ltd. Oracle, images, and associated services are property of Oracle Corporation. Cloud8 Brasil em Português.

Manoel Netto Designer
Manage Consent
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
  • Manage options
  • Manage services
  • Manage {vendor_count} vendors
  • Read more about these purposes
View preferences
  • {title}
  • {title}
  • {title}