open-index/open-npm huggingface dataset:
npm package: @posthog/redshift-plugin
Description: Export PostHog events to Amazon Redshift on ingestion.
Latest version: 0.0.7

# Redshift Plugin

Send events to AWS Redshift on ingestion.

## Instructions

### 1. [Create a Redshift Cluster](https://docs.aws.amazon.com/redshift/latest/dg/tutorial-loading-data-launch-cluster.html)

### 2. Make sure PostHog can access your cluster

This might require a few things:

-   [Allowing public access to the cluster](https://aws.amazon.com/premiumsupport/knowledge-center/redshift-cluster-private-public/)
-   [Ensuring your VPC security group allows traffic to and from the Redshift cluster](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_SecurityGroups.html) - If this is not possible in your case, you should consider using our [S3 plugin](https://posthog.com/plugins/s3-export) and then setting up your own system for getting data into your Redshift cluster

### 3. Create a user with table creation priviledges

We need to create a new table to store events and execute `INSERT` queries. You can and should block us from doing anything else on any other tables. Giving us table creation permissions should be enough to ensure this:

```sql
CREATE USER posthog WITH PASSWORD '123456yZ';
GRANT CREATE ON DATABASE your_database TO posthog;
```

### 4. Add the connection details at the plugin configuration step in PostHog
npm package: @posthog/replicator-plugin
Description: Replicate PostHog event stream in another PostHog instance
Author: PostHog
Latest version: 0.0.7

# PostHog Plugin: Replicator

Replicate PostHog event stream in another PostHog instance. Simply: export events.

## Installation

1. Access PostHog's **Plugins** page from the sidebar.
1. Go to the **Advanced** tab.
1. **Fetch and install** the following URL in the **Install from GitHub, GitLab or npm** section:  
   `https://github.com/PostHog/posthog-plugin-replicator`.
1. Configure the plugin.
1. See events come into another PostHog instance, identically to originals.

## Questions?

### [Join our Slack community.](https://posthog.com/slack)
npm package: @posthog/s3-export-plugin
Description: Export PostHog events to Amazon S3 on ingestion.
Latest version: 0.0.7

# S3 Export Plugin

Export events to Amazon S3 on ingestion. Archive your data, or simply free it up for other kinds of analysis, by integrating export right into your event processing pipeline.

**_Available on self-hosted PostHog 1.24.0+_**

## Installation

1. Access PostHog's **Plugins** page from the sidebar.
1. To perform installation either:
    1. go to the **Repository** tab, find this plugin, and **Install** it,
    1. or go to the **Advanced** tab and **Fetch and install** the following URL in the **Install from GitHub, GitLab or npm** section:  
       `https://github.com/posthog/s3-export-plugin`.
1. Configure the plugin by entering your AWS credentials and S3 bucket details.
1. Watch events roll into S3!

## Obtaining AWS Credentials

1. Log in to [AWS](https://console.aws.amazon.com/).
1. Open [S3](https://s3.console.aws.amazon.com/) in the AWS console and create a new bucket in your chosen region.
1. Open [IAM](https://console.aws.amazon.com/iam/home) and create a new policy to allow access to this bucket.
    1. Open "Policies" and click "Create policy"
    1. On the "Visual Editor" tab, click "Choose a service" and select "S3"
    1. Under "Actions" select
        1. "Write" -> "PutObject"
        1. "Permission Management" -> "PutObjectAcl"
    1. Under "Resources" select "Specific" and click "object" -> "Add ARN"
    1. Specify your bucket name and choose "any" for the object name, so the ARN looks something like this: `arn:aws:s3:::my-bucket-name/*`
    1. Click "Next" until you end up on the "Review Policy" page
    1. Give it a name
1. Open [IAM](https://console.aws.amazon.com/iam/home) and create a new user who uses this policy
    1. Click "Users" -> "Add User"
    1. Specify a name and choose "Programmatic access"
    1. Click "Next"
    1. Select "Attach existing policies directly"
    1. Select the policy you had just created
    1. Click "Next" until you reach the "Create user" button. Click that as well.
    1. Make sure to copy your "Access key" and "Secret access key". The latter will not be shown again.
1. Install the plugin in PostHog and fill in the "Access key", "Secret access key", "Bucket region" and "Bucket name" fields. Adjust other parameters as needed.

## Memory Usage

To vastly increase export throughput, this plugin batches events in memory before uploading them to S3. Upload frequency (every minute by default) and maximum upload
size (1 MB by default) can be configured when the plugin is installed.

You should make sure to keep these numbers reasonable to avoid running out of memory on your server. Note that the values apply to **each** concurrent plugin server thread.

## Incorrect S3 Access Configuration Handling

If you incorrectly configured your bucket or access roles, you will not get an error message. This will change once
[this PostHog plugin server issue](https://github.com/PostHog/plugin-server/issues/72) is resolved. Thank you for your patience!

## Questions?

### [Join the PostHog Users Slack community.](https://posthog.com/slack)