Skip to content
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.

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

Add more explanations on integrating AWS SQS #60

Open
Zehelein opened this issue Mar 6, 2020 · 0 comments
Open

Add more explanations on integrating AWS SQS #60

Zehelein opened this issue Mar 6, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@Zehelein
Copy link
Contributor

Zehelein commented Mar 6, 2020

[x] Documentation enhancement

I got the SQS integration working but I am not 100% if all the steps are correct/if you have some better way/other suggestions.

  1. Create a policy in the Identity and Access Management (IAM) section
    • KMS: likely list+read would be enough? I allowed it for "All resources"
    • SQS: likely all but permission management and tagging are needed?
    • SNS: same as SQS
    • anything else like S3 or such would not be needed
  2. Setting environment variables (I am using dotenv for it). But it seems there are different approaches like config file or directly setting it in the SQS/SNS constructor. Maybe you use a different approach.
    • AWS_REGION e.g. eu-central-1
    • AWS_ACCESS_KEY_ID (20 characters)
    • AWS_SECRET_ACCESS_KEY (40 characters)
  3. The queue and dead-letter queue names must be unique per service.

I think in the SQS example there is one typo. Line 4 should be:
import { BUS_SQS_SYMBOLS, BusSqsModule, SqsTransportConfiguration } from '@node-ts/bus-sqs'

@adenhertog adenhertog added the enhancement New feature or request label Mar 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants