What AWS architecture would you recommend?

A web design company currently runs several FTP servers that their 250 customers use to upload and
download large graphic files They wish to move this system to AWS to make it more scalable, but they wish to
maintain customer privacy and Keep costs to a minimum.
What AWS architecture would you recommend?

A web design company currently runs several FTP servers that their 250 customers use to upload and
download large graphic files They wish to move this system to AWS to make it more scalable, but they wish to
maintain customer privacy and Keep costs to a minimum.
What AWS architecture would you recommend?

A.
ASK their customers to use an S3 client instead of an FTP client. Create a single S3 bucket Create an IAM
user for each customer Put the IAM Users in a Group that has an IAM policy that permits access to subdirectories within the bucket via use of the ‘username’ Policy variable.

B.
Create a single S3 bucket with Reduced Redundancy Storage turned on and ask their customers to use an
S3 client instead of an FTP client Create a bucket for each customer with a Bucket Policy that permits
access only to that one customer.

C.
Create an auto-scaling group of FTP servers with a scaling policy to automatically scale-in when minimum
network traffic on the auto-scaling group is below a given threshold. Load a central list of ftp users from S3
as part of the user Data startup script on each Instance.

D.
Create a single S3 bucket with Requester Pays turned on and ask their customers to use an S3 client
instead of an FTP client Create a bucket tor each customer with a Bucket Policy that permits access only to
that one customer.



Leave a Reply 4

Your email address will not be published. Required fields are marked *


Shinobi

Shinobi

A: is the best solution in this case.
D: is out, because the limit of 100 buckets

AI

AI

why not B

Nick Doyle

Nick Doyle

Nothing to indicate RRS is a good fit here