The source project of this merge request has been removed.
Playbook content for flat file alternative using S3 INPLATFORM-176
Merge request reports
Activity
added 3 commits
-
7bc818fc...027f8084 - 2 commits from branch
interop/iics:master
- f5d3d6de - Playbook content for flat file alternative using S3 INPLATFORM-176
-
7bc818fc...027f8084 - 2 commits from branch
- Resolved by Shreyash Shrestha
- Resolved by Shreyash Shrestha
- Resolved by Shreyash Shrestha
@SHREYASH.SHRESTHA I think this can be moved to Best Practices And Recommendations folder.
added 1 commit
- 56dc2a76 - Playbook content for flat file alternative using S3 INPLATFORM-176
added 1 commit
- e8b57b2a - Playbook content for flat file alternative using S3 INPLATFORM-176
added 1 commit
- cef2cce6 - Playbook content for flat file alternative using S3 INPLATFORM-176
added 1 commit
- edf69df5 - Playbook content for flat file alternative using S3 INPLATFORM-176
added 1 commit
- aa0389c2 - Playbook content for flat file alternative using S3 INPLATFORM-176
mentioned in commit 312ac351
- docs/best-practices/flat-file-alternative.md 0 → 100644
24 After you have acquired an AWS account, you can create an IAM User with Read/Write permissions to AWS S3 Buckets in your account. 25 If you are using AWS S3 only as a source, then you may only need Read permission. An AWS Access and Secret key can be generated for this IAM User which is then used in the IICS AWS S3 Connection Properties. 26 27 [IICS AWS S3 Connection Documentation](https://docs.informatica.com/integration-cloud/cloud-data-integration/current-version/data-integration-connections/connection-properties/amazon-s3-connection-properties.html) 28 29 ### AWS S3 for testing and debugging integrations 30 31 AWS S3 provides a great mechanism to test pieces of a large ETL project. 32 When an ETL project relies on multiple sources and transformations, small pieces of the transformation can be designed and tested by outputting to an S3 bucket for verification. 33 Once the verification is successful, the next transformation can be designed and tested in the same fashion. 34 This method can also be used for testing changes that need to be made on an ETL process. 35 Parts that need to be changed can be duplicated and verified in an S3 bucket. 36 37 ## WiscAlerts example 38 39 The [WiscAlerts example](./tutorials/wiscalerts/wiscalerts.md) describes a successful use of AWS S3 as a Flat file alternative. - docs/best-practices/flat-file-alternative.md 0 → 100644
26 27 [IICS AWS S3 Connection Documentation](https://docs.informatica.com/integration-cloud/cloud-data-integration/current-version/data-integration-connections/connection-properties/amazon-s3-connection-properties.html) 28 29 ### AWS S3 for testing and debugging integrations 30 31 AWS S3 provides a great mechanism to test pieces of a large ETL project. 32 When an ETL project relies on multiple sources and transformations, small pieces of the transformation can be designed and tested by outputting to an S3 bucket for verification. 33 Once the verification is successful, the next transformation can be designed and tested in the same fashion. 34 This method can also be used for testing changes that need to be made on an ETL process. 35 Parts that need to be changed can be duplicated and verified in an S3 bucket. 36 37 ## WiscAlerts example 38 39 The [WiscAlerts example](./tutorials/wiscalerts/wiscalerts.md) describes a successful use of AWS S3 as a Flat file alternative. 40 41 EI Staff have implemented the integration using AWS S3 instead of relying on flat files.
Please register or sign in to reply