Hello looking back.
So now with reliability security and encryption features let's start.
So let's start with reliability.
Amazon asking us stores all the queued messages and messages within a single.
So all the cues and the messages within in a single highly available region with multiple redundant
it is on.
So your messages and cues are in in multiple availability zones but in the same region.
So there's no single computer network or easy failure that can make messages inaccessible.
So by doing that by taking your cues and the messages within and replicating them in multiple availability
zones but it has to be in the same region.
The only thing which is highly unlikely except if it is a natural disaster that we are going to lose
a complete region at once.
And even if that happens that will be very rare to happen.
And I'm sure it will have its place in place or somehow to compensate its customers for such a mistake.
So there is no single computer is it for instance hardware server network or easy failure that can make
your message inaccessible unless if you are extremely unlucky and you lose a complete region for extended
time
security you can use I am policies to control who can read or write messages from two years.
Q Can I provide access to cues to anonymous anonymous access.
Yes you can but you are talking about control and security features not the security features authentication
mechanism mechanism ensure that message is stored in an obscure message queues are secured against unauthorized
access.
You can't control who send messages to a message queue and who can receive messages from a message queue
using in policies and for additional security you can build your application to encrypt messages before
they are placed in a message queue.
It's up to you if you want to encrypt your message below before they are placed in a queue.
Of course you can but remember that your upgrade your other application components must have access
to the encryption keys in order to be kept.
So it's up to you but you manage the complex it's your support HDTV it's GDP over SSL and supports allows
virgins when 1.1 1.2 in all supported regions.
So this is supported us is PCI d s s payment card industry data security standard live and one complaint
and also it is eligible for hiper which is the Health Insurance Portability and Accountability Act.
So these are certification of compliance for the obscure service that can be used for PCI ideas as basically
great card payment industry or applications and also for the health care industry that you can use it
for that to decouple applications that will help will serve in the PC industry or in the healthcare
industry.
Encryption very important.
Now lets talk about server side encryption.
If the components were log message to the queue is there ability in the queue as queue to encrypt the
messages as they are received.
Yes.
So it will let you transmit sensitive data and encrypted queues service something corruption protects
the contents of messages in Amazon as Skewes using Calamus managed keys but of course using keys will
be an extra charge.
You can if you don't want to encrypt it on your side before sending it to ask you as.
Then you can send it unencrypted and it will be encrypted on the queue itself.
And what will be encrypted there are parts that will be encrypted and parts will not and we talk about
that now.
So it was I think optional encrypt messages as soon as Amazon.
Q S receives them so as soon as they are get into the queue they are going to be encrypted the messages
are stored in encrypted form.
Amazing.
Decrypts message is only when they are sent to an authorized consumer who determined the authorized.
We talked about high end policies right and it uses a 256 bit encryption and not worry about a mess.
It is a skillful and secure highly available service in the club and when we talk about encryption.
Is it available for standard or for FIFO queues.
It's available for both of them.
As we mentioned before that FIFO queues are not available in all regions.
Also several have been corruption for years.
Is not available in all regions so you need to check the entire region for availability.
What if I need to use it in a region and the region doesn't have the service.
We said that you can always encrypt the data before encrypt the messages before sending them to the
rescue rescue.
However that will be client side encryption not server side encryption so you'll need to manage how
we are going to do that what is encrypted what's not encrypted so he will encrypt the body of the message
in a queue and it will not encrypt the following components of the message.
The meta data of the queue.
So basically the queue name and the attributes of the queue are not.
Message me today.
So which message timestamp and attributes for the message itself.
It's not encrypted and Bercu Matrix The Matrix specific to that Q And if you look at that this is not
something critical for you to be encrypted.
Right you are worried about the message itself.
Which part.
What to do what transcoding is required.
Your actual data that your actual date but these are human to date that message today to pick your metrics.
These are AWOS attributes for your Qs.
Not the message itself.
Encrypting a message makes it makes its context unavailable to unauthorized or anonymous user so even
if someone has access to the message they will not be able to read the contents of the message.
Getting messages does not affect the normal function functioning of an excuse so that encryption will
it affect the performance would affect the number of queues.
This or that it does not and message is encrypted only if it is sent after the encryption of a queue
is enabled.
So are you telling me that if I had queues the queue had messages.
Remember when you said that some messages can be there for 14 days.
What if I don't own encryption service side encryption on the queue and there are some messages on encrypted
so young cryptic messages.
It will not be encrypted when you turn it on on the ice.
So the new message is loaded or it will be encrypted.
The older ones will not be encrypted and also any encrypted message that say that it was an encrypted
queue and I had encrypted messages.
And now I turned off the encryption so the encrypted messages will remain encrypted.
But the new ones will not be encrypted.
Karaite one more lecture with us limits and names and monitoring monitoring this should be an easier
one.
In order to complete the theory part of the US I will see you after the break.
Thank you.