diff --git a/README.md b/README.md
index 111f728..56bed63 100644
--- a/README.md
+++ b/README.md
@@ -1,168 +1,13 @@
-[](https://github.com/itsmestefanjay/camunda-s3-connector/actions/workflows/maven.yml)
+[](https://github.com/NovatecConsulting/camunda-aws-s3-connector/actions/workflows/maven.yml)
# AWS S3 Connector
Camunda Outbound Connector to interact with the content of an S3 bucket
-DISCLAIMER: You are responsible for your AWS configuration in your environment, keep in mind that you have to make
-sure that you keep credentials in a safe place and only give access to specific resources, and be as restrictive as
-possible. This is not a security tutorial for AWS. You should definitively know what you are doing!
-
## Features
-- Upload a generated file to an AWS S3 bucket
-- Delete a file from an AWS S3 bucket
-- Download a file from an AWS S3 bucket
-- Files are saved in the local filesystem to allow interaction between activities
-
-
-## Setup
-
-### Connector configuration
-
-| name | description | example |
-|-----------------|--------------------------------------------|-----------------------------|
-| `accessKey` | the AWS access key for the authorized user | `secrets.AWS_ACCESS_KEY` |
-| `secretKey` | the AWS secret key for the authorized user | `secrets.AWS_SECRET_KEY` |
-| `region` | the AWS region of your S3 bucket | eu-central-1 |
-| `bucketName` | the name of the S3 bucket | camunda-s3-connector-bucket |
-| `objectKey` | path + file name in the s3 bucket | `="invoice/"+fileName` |
-| `operationType` | what to do on s3 | `PUT_OBJECT` |
-| `filePath` | absolute path to the file to upload | `=filePath` |
-| `contentType` | the content type of the content | `=contentType` |
-
-NOTE: please do not put secrets directly into your configuration. See the secrets section for more details.
-
-#### How it looks in the modeler
-
-
-### AWS Resources
-- S3 bucket (non-public) with server-side encryption and versioning enabled
-- IAM User with putObject, deleteObject and getObject rights to the bucket
-- Access key and Secret key for the IAM user
-
-#### IAM policy
-
-```json
-{
- "Version": "2012-10-17",
- "Statement": [
- {
- "Sid": "AllowPutAndDeleteInS3",
- "Effect": "Allow",
- "Action": [
- "s3:PutObject",
- "s3:DeleteObject",
- "s3:GetObject"
- ],
- "Resource": "arn:aws:s3:::/*"
- }
- ]
-}
-```
-
-## Runtime
-
-### Get credentials from AWS
-
-In order to access AWS from your connector you need the above mentioned user with a IAM policy for S3. Additionally
-you need to generated credentials for the user. You can do this over the AWS console in IAM:
-
-- Log into your AWS console
-- Go to IAM > Users
-- Select your created user, e.g. `camunda-s3-connector-user`
-- Go to Security credentials > Access keys
-- Click `Create access key`
-- Select `Third-party service`
-- Check that you understand the risk of having a permanent access key
-- add a tag if wished
-- Click on create and save your credentials in a save place
-
-ATTENTION: There are many ways to achieve this in IAM, I only describe the easiest,
-but possibly not the safest way to do it
-
-### Docker Compose
-
-You can use the `compose-camunda-platform.yaml` file to start a local Camunda 8 platform instance with Operate. The connector
-and additional JobWorkers that might generate files, are run in a separate Springboot application.
-
-### Running the connector
-
-- Configure your Springboot application for local or camunda platform
-
-```properties
-zeebe.client.cloud.region: my-region
-zeebe.client.cloud.clusterid: my-cluster-id
-zeebe.client.cloud.clientid: my-client-id
-zeebe.client.cloud.clientsecret: my-client-secret
-```
-
-Or if you use a local runtime:
-
-```properties
-operate.client.enabled=true
-camunda.operate.client.url=http://localhost:8081
-camunda.operate.client.username=demo
-camunda.operate.client.password=demo
-zeebe.client.broker.gateway-address=localhost:26500
-zeebe.client.security.plaintext=true
-```
-
-And add your access and secret key from your AWS as environment variables:
-
-```
-AWS_ACCESS_KEY=my-access-key
-AWS_SECRET_KEY=my-secret-key
-```
-
-- Start the Springboot application
-
-### Handling secrets
-Since your connector needs to run in a custom connector runtime, you cannot just add secrets in the cloud console since
-they will not be auto-magically transported into your connector runtime. You can provide them by:
-
-- adding them as environment variables (e.g. when you use the SpringBoot connector runtime)
-- adding them as an env file to your docker container
-
-NOTE: This behaviour will most likely be improved in the future
-
-## FileAdapter
-
-The connector uses two file adapters:
-
-- *cloud file adapter* to S3
-- *local file adapter* to the local file system
-
-### Why is this necessary?
-If you are handling a lot of files (maybe even big files) it is a best practice approach to NOT store your file or the content
-in a process variable for several reasons:
-
-- Zeebe currently only support variables < 2MB
-- The files become part of the process state
-- You have no way to clean it up (yet)
-
-With the local file adapter the file can be written to a temp directory and the file path can be handed to other activities.
-If you want to move files to another process instance, just upload it back to S3 and start another process with the
-input variables needed to download the file again from S3.
-
-### How to generate content?
-The upload is done by resolving a local path to a `Path`. Since a process variable is currently limited in size to approx.
-2-4MB (there are some Zeebe chaos engineering tests) the file content should stay in the connector runtime. You can e.g.
-run a `JobWorker` in the same runtime environment to generate a file and store it with the `LocalFileCommand` interface.
-You can then get the path and set it into a `filePath` variable, which you then can reference with a FEEL expression in
-the `filePath` configuration of the connector:
+- Connector implementation to interact with an S3 bucket in AWS
+- Process example on ho to generate content and upload it with the connector
+- File API to streamline file handling between job workers and the connector
-```java
-public class MyWorkerClass {
-
- @JobWorker("generate-file")
- public void generate() {
- byte[] content = "This is some random file".getBytes(StandardCharsets.UTF_8);
- String filePath = String.format("results/%s/my-file.txt", job.getProcessInstanceKey());
- localFileCommand.saveFile(content, filePath);
- return Map.of("generatedFilePath", filePath, "generatedFileContentType", "text/plain");
- }
-
-}
-```