Hello and welcome back more as three scenary best questions one of your clients is using it.
Yes.
And he's wondering how can he sort of private content from a story to the subscribed users securely.
Keeping in mind that the subscribers are not users.
Remember what we call these the that users are not users.
They don't have credentials.
Yes.
So these are public users in a sense that they are not authenticated they're not authenticated users.
Why not.
And syndicated.
They don't have any obvious credentials.
Think of Dropbox or any cloud service where you can now save files and download drives upload and all
that.
If you are sharing a file with someone does that one have to have an account on Dropbox.
The answer is No.
On Microsoft SharePoint the answer is No.
They will send you an email link.
If you click on that link that is a signed link that can allow you securely to access the file or the
files that are shared with you or allow you to upload files as well to that folder in that cloud solution
or Sharepoint whatever the solution is.
Keeping in mind that subscribers are not users and have no obvious credentials.
The client maintains information IDs about subscribed users in a separate.
It obviously is.
How can your client achieve this achieve what set of that content privately and securely to the subscribed
users.
And no one else would be able to get to that a create either.
Yes I am users and provide them permissions to read the objects can be said of the content through cloud
front instead of direct from S3.
This one I can immediately rule out.
Why.
Because this is talking about plug front as opposed to a story not about the security of cloud.
Cloud front as opposed to S3.
So that's why I don't see leverage pre-signed you or else for each user to access the private content
when they want to access it.
So this is a potential correct answer.
The configure your as three bucket policy to allow these users access to the private content only.
This cannot be done.
Why.
Although I can configure users in the bucket policy.
I can do I am users I can I do I am groups or user groups and I can do I am rules as well.
That can be configured and I can do asterisk which is anyone and I can do of course account canonical
ID or they count IDs so you can do that.
But here when we are talking about specified set of users how can you.
Are you going to configure configure rules after rules of the rules of the rules Grand's of the guns
are against it remember that the policy can be maximum 20 kilobyte I you want to be able to do that.
And if someone thinks about the object of it as you can not define users in the object itself.
So what do we do then.
Then this one seems to be the right answer for this case.
Why not this one.
A is wrong.
Why if C is the correct one then it is wrong but we didn't find out what created this AM users remember
what they said about the subscribers the subscribers are not users and users are either users and they
have no obvious credentials.
I mean those have to be credentials.
That's why it's wrong.
So C is the correct answer.
Is incorrect use of content do not need to have the earliest accounts to access the content.
That's what they said that users do not have it of his credentials.
B How would this help.
Problem is not about the performance or the answer is not complete C is correct.
DS incorrect because these are not either of us users to start with and the correct answer is C Google
information for the scope presented to you or else can be used to provide temporary access because usually
define an expiration to that as well to a specific object.
To those who do not have either of us credentials exemple is customers who bought web sites subscription
or for their subscriptions online.
By default all objects are private and only the object owners owner can access it.
To share an object you have to either make it public and that's one way.
But if you don't want to do it for everyone then you generate pre-signed you or else to grant access
for a limited time to this object or objects using the object owner's own security credentials.
So take a break now and I will see you in the next lecture with more of your ass knowledge and practice.
I'll see you then.