message queue - Amazon SQS multi tenancy and HIPAA compliance -


i'm going implement client/server application - 1 server - [0-n] clients.

in order organize communication between clients , server plan use amazon sqs or that.

right have 2 questions:

is amazon sqs hipaa compliant ?

how organise multi tenancy support based on amazon sqs queues ?

the data between clients must not shared. each client can deal data sent client.

is possible implement on single amazon sqs queue or need create separate queue each client ?

regarding hipaa , sqs: while baa aws not allow use sqs phi, allow use s3 (but don't take word it, in baa sure).

if case, can put message payload (phi) in (encrypted) s3 file , send sqs message references s3 key. when handle sqs message, go grab file s3 , process it, deleting message and/or file appropriate.

there "extended" sqs client may able use handles magic you.

another option enable , configure event notifications on s3 bucket such message queued each file uploaded bucket. in other words, file uploaded , message sent side-effect. then, when process message handle s3 file. keeping phi in s3, avoid baa restrictions on sqs.


Comments

Popular posts from this blog

java - UnknownEntityTypeException: Unable to locate persister (Hibernate 5.0) -

python - ValueError: empty vocabulary; perhaps the documents only contain stop words -

ubuntu - collect2: fatal error: ld terminated with signal 9 [Killed] -