With this model AWS charge you for running tasks rather than running container instances. The Fargate launch type allows you to run your containerized applications without the need to provision and manage the backend infrastructure. You just register your task definition and Fargate launches the container for you. The Fargate Launch Type is a serverless infrastructure managed by AWS.

With this launch type you pay for running container instances (EC2 instances).

This does not specify the launch type. You can run an ECS Service on the Fargate or EC2 launch types.

This does not specify the launch type. You can run an ECS Service on the Fargate or EC2 launch types.

1."company should be charged per running task" Therefore, the best answer is to use Amazon ECS with the Fargate launch type as with this model AWS charge you for running tasks rather than running container instances.

Amazon DynamoDB is designed for scale and performance. In most cases, the DynamoDB response times can be measured in single-digit milliseconds. However, there are certain use cases that require response times in microseconds. For these use cases, DynamoDB Accelerator (DAX) delivers fast response times for accessing eventually consistent data. In this scenario the question is calling for sub-millisecond (e.g. microsecond) latency and this is required for read traffic as evidenced by the need to over-provision reads. Therefore, DynamoDB DAX would be the best solution for reducing the latency and meeting the requirements.

This will not reduce the latency of the application. Transfer Acceleration is used for improving performance of uploads of data to Amazon S3.

This may reduce the requirement for over-provisioning reads but it will not solve the problem of reducing latency. With this solution the application performance will be worse, it’s a case of reducing cost along with performance.

GSI is used to speed up queries on non-key attributes. There is no requirement here for a Global Secondary Index.

1."Latency" &

2."Read Capacity" of DynamoDB.

& DynamoDB DAX main purpose is to improve latency & thus read capacity of DynamoDB.

Add a bucket policy that requires Multi-Factor Authentication for requests to access the S3 bucket objects would be very difficult to manage & it won't solve our problem to allow only paid subscribers.

As this is encryption at rest and S3 will simply unencrypt the objects when users attempt to read them. This provides privacy protection for data at rest but does not restrict access.

• When Amazon S3 objects are private, only the object owner has permission to access these objects. However, the object owner can optionally share objects with others by creating a presigned URL, using their own security credentials, to grant time-limited permission to download the objects.
• When you create a presigned URL for your object, you must provide your security credentials, specify a bucket name, an object key, specify the HTTP method (GET to download the object) and expiration date and time. The presigned URLs are valid only for the specified duration.
• Anyone who receives the presigned URL can then access the object. In this scenario, a pre-signed URL can be generated only for paying customers and they will be the only website visitors who can view the premier content.

This would provide everyone the ability to download the content.

1."make available to only paid subscribers" which redirect us to option C as in this scenario, a pre-signed URL can be generated only for paying customers and they will be the only website visitors who can view the premier content.