# Diagnose connection issues with cloud storage

Check common cloud storage configuration points.

If you have issues with your Stripe Data Pipeline connection to your cloud storage, use this guide to check common configuration points.

## Google Cloud Storage 

Confirm that the bucket and project names match those in the Data Pipeline Dashboard:

1. Navigate to the [Data Pipeline Dashboard](https://dashboard.stripe.com/settings/stripe-data-pipeline).
1. Save the bucket and project listed for your Google Cloud Storage connection.
1. Open the [Cloud Storage bucket](https://console.cloud.google.com/storage/browser) page under the correct Google Cloud Project.
1. Confirm that the bucket listed in your Dashboard appears in your console.

To confirm that the roles and permissions are correct:

1. Navigate to your [Cloud Storage bucket](https://console.cloud.google.com/storage/browser) details, then click the Permissions tab.
1. Confirm that your [Service Account](https://console.cloud.google.com/iam-admin/serviceaccounts) includes the following roles: `Storage Object User`, `Storage Object Creator`, and `Storage Insights Collector Service`.

Make sure that you continue to confirm the [Google Cloud Status Dashboard](https://status.cloud.google.com/) for any ongoing issues with Google Cloud Storage. Contact [Stripe support](https://support.stripe.com/contact/email?topic=third_party_integrations&subject=Stripe%20Data%20Pipeline%20\(SDP\)) if these steps don’t resolve your connection issues.

## Azure 

Confirm that the container is correct:

1. Navigate to the [Storage Accounts](https://portal.azure.com/#view/HubsExtension/BrowseResource/resourceType/Microsoft.Storage%2FStorageAccounts) page.
1. Click **Storage browser** > **Data storage** > **Containers**.
1. Confirm that your container from the [Data Pipeline Dashboard](https://dashboard.stripe.com/settings/stripe-data-pipeline) appears on the Azure Containers page.

To confirm that the access key still exists:

1. Navigate to the [Storage Accounts](https://portal.azure.com/#view/HubsExtension/BrowseResource/resourceType/Microsoft.Storage%2FStorageAccounts) page.
1. Click **Security + networking** > **Access keys**.
1. Confirm that the shared access key still exists.

To confirm that the Resource group and Subscription ID are correct:

1. Navigate to the [Storage Accounts](https://portal.azure.com/#view/HubsExtension/BrowseResource/resourceType/Microsoft.Storage%2FStorageAccounts) page.
1. Click **Overview**.
1. Confirm that the Resource group and Subscription ID match those from the initial onboarding. Make sure that you continue to confirm the [Azure Status Dashboard](https://azure.status.microsoft/en-us/status) for any ongoing issues with Azure. Contact [Stripe support](https://support.stripe.com/contact/email?topic=third_party_integrations&subject=Stripe%20Data%20Pipeline%20\(SDP\)), if these steps don’t resolve your connection issues.

## Amazon S3 

To confirm you attached the policy you created to the new trust role:

1. Navigate to the [IAM console](https://console.aws.amazon.com/iam/) and click **Policies**.
1. Select the policy created in [step 4](https://docs.stripe.com/stripe-data/access-data-in-warehouse/cloud-storage/aws-s3-storage.md#create-permission-policy) (for example, `stripe-data-pipeline-policy`).
1. Click **Entities attached** and confirm that `stripe-data-pipeline-s3-role` appears under **Attached as a permissions policy**.
1. If not, click **Attach**, then select `stripe-data-pipeline-s3-role` and click **Attach policy**.

## Common issues

If you can’t find a specific table in a data load, it might not be an API-backed table, and therefore isn’t included in every data load. For example, you can only find your `exchange_rates_from_usd` table every 28 hours. You can confirm this by checking for a SUCCESS_File or confirming the [data freshness ](https://docs.stripe.com/stripe-data/data-pipeline/data-freshness.md#dataset-freshness).