After reviewing the last quarter's monthly bills, management has noticed an increase in the overall bill from AWS.
After researching this increase in cost, you discovered that some new services and users are doing many GET Bucket API calls to Amazon S3
Your boss has asked you to come up with a new cost-effective way to reduce the number of these new GET Bucket API calls.
What process should you use to help mitigate the cost?
Click on the arrows to vote for the correct answer
A. B. C. D.Answer - C.
Option A is INCORRECT because this does not reduce the number of GET Bucket API calls to Amazon S3.
Option B is INCORRECT because this method may impact the service if the S3 objects are moved to Glacier.
Option C is CORRECT because bucket policies can limit unauthorized access to reduce the number of API calls to S3.
Option D is INCORRECT because uploading all files to Elastic Cache is not an ideal solution.
For more information on how to reduce the S3 cost, please refer to the below link:
https://aws.amazon.com/premiumsupport/knowledge-center/s3-reduce-costs/The correct answer to this question is C: Prevent unauthorized access or limit public access to your bucket using bucket policies.
Explanation: Amazon S3 (Simple Storage Service) is an object storage service that provides industry-leading scalability, data availability, security, and performance. It provides a simple web services interface that can be used to store and retrieve any amount of data, at any time, from anywhere on the web. However, it is important to monitor the usage of the service to avoid unexpected increases in the bill.
In this scenario, the increase in cost is due to the excessive use of GET Bucket API calls to Amazon S3. The GET Bucket API call is used to list all the objects in a bucket. When many GET Bucket API calls are made, it can result in increased data transfer and API request charges.
To mitigate this cost, the best approach is to prevent unauthorized access or limit public access to your bucket using bucket policies. This can be achieved by creating a policy that specifies which IAM users or roles can access the bucket and what actions they can perform on the objects in the bucket. By doing this, you can control the access to your bucket and reduce the number of GET Bucket API calls.
Some examples of bucket policies that can be used to control access are:
Deny public access to the bucket: { "Version": "2012-10-17", "Statement": [ { "Effect": "Deny", "Principal": "", "Action": "s3:GetBucket", "Resource": "arn:aws:s3:::examplebucket" } ] }
Allow access to specific IAM users or roles: { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "AWS": [ "arn:aws:iam::ACCOUNT-ID-WITHOUT-HYPHENS:user/USERNAME", "arn:aws:iam::ACCOUNT-ID-WITHOUT-HYPHENS:role/ROLE-NAME" ] }, "Action": "s3:GetBucket*", "Resource": "arn:aws:s3:::examplebucket" } ] }
In summary, to reduce the number of GET Bucket API calls and mitigate the cost, the best approach is to prevent unauthorized access or limit public access to your bucket using bucket policies.