PostHog Handbook Library / Engineering

450 words. Estimated reading time: 2 min.

# Working with cloud providers

### AWS

#### How do I get access?

Create a PR to the `posthog-cloud-infra` repository to add your details in the identity center Terraform configuration with `groups = local.default_groups`.

To give someone access

1. Add the new user to the cloud infra repo (see link above)
2. Use their email address as their username
3. Add them to the "Developers" and "DevelopersRO" groups (just use `groups = local.default_groups`)
4. Add team infra as reviewer.
5. Once this is merged, tell them to use http://go/aws to log in

#### Elevating permissions via `#aws-access`

To access the dev AWS environment, use the `/awsaccess` slash command in the `#aws-access` Slack channel and fill out the form that appears. Make sure to set up your AWS config file as described in our docs.

A dedicated `secrets-editor` role is available for managing secrets. Use this role across all AWS environments.

EKS access via `#aws-access` is currently in development. In the near future, expect all AWS access to be managed through the `#aws-access` channel.

#### Permissions errors using AWS CLI

If you see something like:

    <my-user> is not authorized to perform: <action> on resource: <resource> with an explicit deny

Note the "with an explicit deny" in the end which likely is due to the fact that we force Multi-Factor Authentication (MFA). Follow this guide to use a session token.

TLDR:

1. Look up your security credential MFA device name from AWS console from `https://console.aws.amazon.com/iam/home#/users/<user-name>?section=security_credentials`
2. Run `aws sts get-session-token --serial-number <arn-of-the-mfa-device> --token-code <code-from-token> --duration 129600` where `code-from-token` is the same code you'd use to login to the AWS console (e.g. from Authy app).
3. Run the following code, replacing the placeholder values with the appropriate ones:

    export AWS_ACCESS_KEY_ID=example-access-key-as-in-previous-output
    export AWS_SECRET_ACCESS_KEY=example-secret-access-key-as-in-previous-output
    export AWS_SESSION_TOKEN=example-session-token-as-in-previous-output

1. Unset them when done (after they expire before running `get-session-token` again):

    unset AWS_ACCESS_KEY_ID && unset AWS_SECRET_ACCESS_KEY && unset AWS_SESSION_TOKEN

#### Deploying PostHog

See the AWS self-host deployment guide.

### GCP

#### How do I get access?

Ask in the `#team-infrastructure` Slack channel for someone to add you.

To give someone access: Navigate to PostHog project IAM and use the `+Add` button at the top to add their PostHog email address and toggle `Basic` -> `Editor` role.

#### Deploying PostHog

See the GCP self-host deployment guide.

### DigitalOcean

#### How do I get access?

Ask in the `#team-infrastructure` Slack channel for someone to add you.

To give someone access: navigate to PostHog team settings page and use the `Invite Members` button to add their PostHog email address.

#### Edit 1-Click app info

This can be done in the vendor portal, click on `PostHog` with Approved status to edit the listing.

The code and setup files are in digitalocean/marketplace-kubernetes repository.

#### Deploying PostHog

See the DigitalOcean self-host deployment guide.

Canonical URL: https://posthog.com/handbook/engineering/cloud-providers

GitHub source: contents/handbook/engineering/cloud-providers.md

Content hash: `5cb20c4fbd52c08a`

Static reader notes

- `MDX_COMPONENT_STATIC_ADAPTER`: Adapted interactive MDX components for static reading: PrivateLink.