Skip to content

Screenshot and user number included in iFlow #14

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ajmaradiaga merged 1 commit into from
Oct 26, 2026
Merged

Screenshot and user number included in iFlow #14

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions ...e-aws-pipeline-revenue-management/dev-garage-aws-pipeline-revenue-management.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -89,6 +89,10 @@ Start Timer (runs the flow once each time you deploy)
| **S3 Write** | Writes the enriched JSON to `curated-corp/profit-margins/` |
| **Show Run Summary** | Puts the run summary in the message, so it's the last thing you see in the Monitor |

By the end of the exercise, you will have an integration flow like the one below:

![Finished integration flow](./assets/aws-s3-step8-finished-iflow.png)

---

### Step 1 — Create a Package and an Integration Flow
Expand All @@ -111,7 +115,7 @@ On the package's **Artifacts** tab, click **Add → Integration Flow**. Keep **C

| Field | Value |
| :--- | :--- |
| Name | `AWS Pipeline for Revenue Management` |
| Name | `AWS Pipeline for Revenue Management User{{var:userNumber}}` |
| ID | *(auto-populated)* |

Click **OK**, open the integration flow, and click **Edit**. Delete the default **Sender** and **Receiver**. This flow is started by a timer and has no sender.
Expand All @@ -120,8 +124,6 @@ Click **OK**, open the integration flow, and click **Edit**. Delete the default

Click **Save** regularly as you build.

---

### Step 2 — Check the Credentials Provisioned for You

The AWS adapters authenticate to Amazon S3 with two secure parameters. They have been created in your tenant, so you don't create them and you never see the AWS access key or secret.
Expand Down
Loading