Added documentation for configuring Killbill to send events to AWS SQS. #559
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
||
| * Access to AWS Management Console. | ||
| * IAM permissions to create and manage SQS and IAM roles. | ||
| * SSH access to the EC2 instance running Killbill. |
There was a problem hiding this comment.
Suggested change
| * SSH access to the EC2 instance running Killbill. | |
| * SSH access to the EC2 instance running Kill Bill. |
|
|
||
| 1. Navigate to the EC2 Dashboard in the AWS Management Console. | ||
|
|
||
| 2. Select the EC2 instance where Killbill is running. |
There was a problem hiding this comment.
Suggested change
| 2. Select the EC2 instance where Killbill is running. | |
| 2. Select the EC2 instance where Kill Bill is running. |
|
|
||
| === Step 4: Configure Killbill to Use SQS | ||
|
|
||
| 1. SSH into the EC2 instance running Killbill. |
There was a problem hiding this comment.
Suggested change
| 1. SSH into the EC2 instance running Killbill. | |
| 1. SSH to the EC2 instance running Kill Bill. |
|
|
||
| === Step 6: Test the Configuration | ||
|
|
||
| 1. To test the setup, install any plugin, add a user, or make any tenant configuration changes in Killbill. These actions should generate events that will be sent to the SQS queue. |
There was a problem hiding this comment.
Suggested change
| 1. To test the setup, install any plugin, add a user, or make any tenant configuration changes in Killbill. These actions should generate events that will be sent to the SQS queue. | |
| 1. To test the setup, install any plugin, add a user, or make tenant configuration changes in Kill Bill. These actions should generate events that will be sent to the SQS queue. |
|
|
||
| == Conclusion | ||
|
|
||
| By following these steps, you should be able to configure Killbill to send events to an AWS SQS queue, enabling better event-driven integrations and workflows. |
There was a problem hiding this comment.
Suggested change
| By following these steps, you should be able to configure Killbill to send events to an AWS SQS queue, enabling better event-driven integrations and workflows. | |
| By following these steps, you can configure Kill Bill to send events to an AWS SQS queue, enabling better event-driven integrations and workflows. |
|
|
||
| == Overview | ||
|
|
||
| This document outlines the steps to configure the Killbill application to send events to an Amazon Simple Queue Service (SQS) queue. |
There was a problem hiding this comment.
Maybe add a link to https://docs.killbill.io/latest/kill_bill_events to explain what a Kill Bill event is?
| -Dcom.killbill.aws.sqs.maxRetries=5 | ||
| ---- | ||
|
|
||
| === Step 5: Restart the Killbill EC2 Instance |
There was a problem hiding this comment.
Suggested change
| === Step 5: Restart the Killbill EC2 Instance | |
| === Step 5: Restart the Kill Bill EC2 Instance |
Thank you, Reshma for these comments. I have addressed them, please check when you get a chance. |
reshmabidikar
approved these changes
Jul 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.