# Structural process overview for Amazon Redshift

The following high-level diagram describes how Tonic orchestrates the processing and moving of data in Amazon Redshift during data generation.

<figure><img src="https://3378426797-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LSQCLFQ4bslJ-HYc8c3%2Fuploads%2FgCZkves49ezCx0XJbX5u%2FRedshiftJobFlow.png?alt=media&#x26;token=f82d67dc-70ae-4bb7-97a1-2d1108cf4de5" alt=""><figcaption><p>Data generation process flow for Amazon Redshift</p></figcaption></figure>

This diagram specifically shows the Amazon Redshift data generation process. For the Structural architecture diagram, go to [architecture-diagram](https://docs.tonic.ai/app/admin/architecture-diagram "mention").

Structural orchestrates the moving and transforming of data between Amazon Redshift databases. To do this, Structural uses Amazon S3.

Structural manages the lifetimes of data and resources used in AWS. It only requires you to assign the necessary permissions to the IAM role that Structural uses.

At a high level, the process is:

1. Structural copies the table data into Amazon S3 as CSV files. You specify the S3 bucket path in the Structural workspace configuration. Within the S3 bucket, the data files are copied into an `input` folder.
2. After it transforms the data in a file, Structural copies the transformed file to the `output` folder in the configured S3 bucket.
3. After it processes all of the files for a table, Structural copies the output data back into Amazon Redshift, into the destination database.