summary
Help Page for ETL Configuration of Data Settings from Amazon Aurora MySQL.
Unlike normal MySQL transfers, Aurora outputs a temporary CSV file to S3 and reads the CSV file for the transfer.
Compared to the usual MySQL transfer method, this method can transfer large amounts of data with less load on Aurora.
Please keep in mind that the column names of the target table may not be inherited as the table names after the transfer.
constraints
- none in particular
Setting items
STEP1 Basic settings
| item name | indispensable | default value | Contents |
|---|---|---|---|
| Amazon Aurora MySQL Connection Configuration | Yes | - | Select the previously registered Connection Configuration that has the necessary permissions for this ETL Configuration. |
| database | Yes | - | Specify the name of the database containing the transferred data in MySQL. |
| query | Yes | - | Enter SQL to retrieve transfer data from MySQL. Do not include ";" at the end of the query. Custom Variables can also be set and embedded within the query. |
| S3 bucket name | Yes | - | Specify the name of the S3 bucket to temporarily output data. |
STEP2 Detailed settings
| item name | default value | Details |
|---|---|---|
| Skip query execution during transfer, Start fetching from a deployed S3 file. |
Do not skip | Selecting Skip allows execution from the S3 file ingestion phase by skipping the query if the job fails after the Aurora query completes. |
| Socket timeout (seconds) | 1800 | The maximum timeout period for ETL Configuration can be set. If the job execution time exceeds the time specified in this Job Setting, the executing job will be stopped. |
supplement
- Aurora's SELECT INTO OUTFILE clause is used for CSV temporary file output.