{"id":20132,"date":"2026-01-05T15:16:04","date_gmt":"2026-01-05T06:16:04","guid":{"rendered":"https:\/\/aireviewirush.com\/?p=20132"},"modified":"2026-01-05T15:16:04","modified_gmt":"2026-01-05T06:16:04","slug":"amazon-s3-storage-lens-provides-efficiency-metrics-assist-for-billions-of-prefixes-and-export-to-s3-tables","status":"publish","type":"post","link":"https:\/\/aireviewirush.com\/?p=20132","title":{"rendered":"Amazon S3 Storage Lens provides efficiency metrics, assist for billions of prefixes, and export to S3 Tables"},"content":{"rendered":"


\n<\/p>\n

\n\n\n\n
\n
\n \"Voiced<\/a>\n <\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Immediately, we\u2019re asserting three new capabilities for Amazon S3 Storage Lens<\/a> that provide you with deeper insights into your storage efficiency and utilization patterns. With the addition of efficiency metrics, assist for analyzing billions of prefixes, and direct export to Amazon S3 Tables,<\/a> you have got the instruments you must optimize software efficiency, scale back prices, and make data-driven selections about your Amazon S3\u00a0storage technique.<\/p>\n

New efficiency metric classes<\/strong><\/span>
\n
S3 Storage Lens now contains eight new efficiency metric classes that assist establish and resolve efficiency constraints throughout your group. These can be found at group, account, bucket, and prefix ranges. For instance, the service helps you establish small objects in a bucket or prefix that may\u00a0 decelerate software efficiency. This may be mitigated by batching small objects or utilizing the Amazon S3 Specific One Zone<\/a> storage class for greater efficiency small object workloads.<\/p>\n

To entry the brand new efficiency metrics, you must allow efficiency metrics within the S3 Storage Lens superior tier when creating a brand new Storage Lens dashboard or modifying an current configuration.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n
Metric class<\/strong><\/td>\nParticulars<\/strong><\/td>\nUse case<\/strong><\/td>\nMitigation<\/strong><\/td>\n<\/tr>\n
Learn request measurement<\/td>\nDistribution of learn request sizes (GET) by day<\/td>\nEstablish dataset with small learn request patterns that decelerate efficiency<\/td>\nSmall request: Batch small objects or use Amazon S3 Specific One Zone for high-performance small object workloads<\/td>\n<\/tr>\n
Write request measurement<\/td>\nDistribution of write request sizes (PUT, POST, COPY, and UploadPart) by day<\/td>\nEstablish dataset with small write request patterns that decelerate efficiency<\/td>\nGiant request: Parallelize requests, use MPU or use AWS CRT<\/td>\n<\/tr>\n
Storage measurement<\/td>\nDistribution of object sizes<\/td>\nEstablish dataset with small small objects that decelerate efficiency<\/td>\nSmall object sizes: Take into account bundling small objects<\/td>\n<\/tr>\n
Concurrent PUT 503 errors<\/td>\nVariety of 503s attributable to concurrent PUT operation on similar object<\/td>\nEstablish prefixes with concurrent PUT throttling that decelerate efficiency<\/td>\nFor single author, modify retry habits or use Amazon S3 Specific One Zone. For a number of writers, use consensus mechanism or use Amazon S3 Specific One Zone<\/td>\n<\/tr>\n
Cross-Area information switch<\/td>\nBytes transferred and requests despatched throughout Area, in Area<\/td>\nEstablish potential efficiency and value degradation attributable to cross-Area information entry<\/td>\nCo-locate compute with information in the identical AWS Area<\/td>\n<\/tr>\n
Distinctive objects accessed<\/td>\nQuantity or share of distinctive objects accessed per day<\/td>\nEstablish datasets the place small subset of objects are being regularly accessed. These may be moved to greater efficiency storage tier for higher efficiency<\/td>\nTake into account transferring lively information to Amazon S3 Specific One Zone or different caching options<\/td>\n<\/tr>\n
FirstByteLatency (current Amazon CloudWatch<\/a> metric)<\/td>\nEvery day common of first byte latency metric<\/td>\nThe every day common per-request time from the whole request being obtained to when the response begins to be returned<\/td>\n\n <\/tr>\n
TotalRequestLatency (current Amazon CloudWatch metric)<\/td>\nEvery day common of Complete Request Latency<\/td>\nThe every day common elapsed per request time from the primary byte obtained to the final byte despatched<\/td>\n\n <\/tr>\n<\/tbody>\n<\/table>\n

The way it works
\n
<\/strong>On the Amazon S3 console<\/a> I select Create Storage Lens dashboard<\/strong> to create a brand new dashboard. It’s also possible to edit an current dashboard configuration. I then configure normal settings similar to offering a Dashboard title<\/strong>, Standing<\/strong>, and the non-compulsory Tags.<\/strong> Then, I select Subsequent<\/strong>.<\/p>\n

\"\"<\/a>
\n
Subsequent, I outline the scope of the dashboard by choosing Embody all Areas and Embody all buckets<\/strong> and specifying the Areas and buckets to be included.<\/p>\n

\"\"<\/a>
\n
I decide in to the Superior tier<\/strong> within the Storage Lens dashboard configuration, choose Efficiency metrics<\/strong>, then select Subsequent<\/strong>.<\/p>\n

\"\"<\/a>
\n
Subsequent, I choose Prefix aggregation<\/strong> as a further metrics aggregation, then depart the remainder of the knowledge as default earlier than I select Subsequent<\/strong>.<\/p>\n

\"\"<\/a>
\n
I choose the Default metrics report<\/strong>, then Common objective bucket<\/strong> because the bucket kind, after which choose the Amazon S3 bucket in my AWS account because the Vacation spot bucket<\/strong>. I depart the remainder of the knowledge as default, then choose Subsequent<\/strong>.<\/p>\n

\"\"<\/a>
\n
I evaluate all the knowledge earlier than I select Submit<\/strong> to finalize the method.<\/p>\n

\"\"<\/a>
\n
After it\u2019s enabled, I\u2019ll obtain every day efficiency metrics immediately within the Storage Lens console<\/a> dashboard. It’s also possible to select to export report in CSV or Parquet format to any bucket in your account or publish to Amazon CloudWatch. The efficiency metrics are aggregated and printed every day and might be obtainable at a number of ranges: group, account, bucket, and prefix. On this dropdown menu, I select the % concurrent PUT 503 error for the Metric<\/strong>, Final 30 days for the Date vary<\/strong>, and 10 for the High N buckets<\/strong>.<\/p>\n

\"\"<\/a>
\n
The Concurrent PUT 503 error depend metric tracks the variety of 503 errors generated by simultaneous PUT operations to the identical object. Throttling errors can degrade software efficiency. For a single author, modify retry habits or use greater efficiency storage tier similar to Amazon S3 Specific One Zone to mitigate concurrent PUT 503 errors. For a number of writers situation, use a consensus mechanism to keep away from concurrent PUT 503 errors or use greater efficiency storage tier similar to Amazon S3 Specific One Zone.<\/p>\n

\"\"<\/a><\/p>\n

Full analytics for all prefixes in your S3 buckets<\/strong><\/span>
\n
S3 Storage Lens now helps analytics for all prefixes in your S3 buckets by way of a brand new Expanded prefixes metrics report<\/strong>. This functionality removes earlier limitations that restricted evaluation to prefixes assembly a 1% measurement threshold and a most depth of 10 ranges. Now you can monitor as much as billions of prefixes per bucket for evaluation on the most granular prefix degree, no matter measurement or depth.<\/p>\n

The Expanded prefixes metrics report contains all current S3 Storage Lens metric classes: storage utilization, exercise metrics (requests and bytes transferred), information safety metrics, and detailed standing code metrics.<\/p>\n

How you can get began<\/strong>
\n
I comply with the identical steps outlined within the The way it works<\/strong> part to create or replace the Storage Lens dashboard. In Step 4 on the console, the place you choose export choices, you possibly can choose the brand new Expanded prefixes metrics report<\/strong>. Thereafter, I can export the expanded prefixes metrics report in CSV or Parquet format to any normal objective bucket in my account for environment friendly querying of my Storage Lens information.<\/p>\n

\"\"<\/a>
\n
Good to know
\n
<\/strong>This enhancement addresses situations the place organizations want granular visibility throughout their total prefix construction. For instance, you possibly can establish prefixes with incomplete multipart uploads to scale back prices, monitor compliance throughout your total prefix construction for encryption and replication necessities, and detect efficiency points on the most granular degree.<\/p>\n

Export S3 Storage Lens metrics to S3 Tables
\n
<\/strong><\/span>S3 Storage Lens metrics can now be robotically exported to S3 Tables, a completely managed function on AWS with built-in Apache Iceberg assist. This integration gives every day computerized supply of metrics to AWS managed S3 Tables for rapid querying with out requiring extra processing infrastructure.<\/p>\n

How you can get began<\/strong>
\n
I begin by following the method outlined in Step 5 on the console, the place I select the export vacation spot. This time, I select Expanded prefixes metrics report<\/strong>. Along with Common objective bucket, I select Desk bucket<\/strong>.<\/p>\n

The brand new Storage Lens metrics are exported to new tables in an AWS managed bucket<\/a> aws-s3<\/code>.<\/p>\n

\"\"<\/a>
\n
I choose the expanded_prefixes_activity_metrics<\/strong> desk to view API utilization metrics for expanded prefix stories.<\/p>\n

\"\"<\/a>
\n
I can preview the desk on the Amazon S3 console or use Amazon Athena<\/a> to question the desk.<\/p>\n

\"\"<\/a>
\n
Good to know
\n
<\/strong>S3 Tables integration with S3 Storage Lens simplifies metric evaluation utilizing acquainted SQL instruments and AWS analytics companies similar to Amazon Athena, Amazon QuickSight<\/a>, Amazon EMR<\/a>, and Amazon Redshift<\/a>, with out requiring an information pipeline. The metrics are robotically organized for optimum querying, with customized retention and encryption choices to fit your wants.<\/p>\n

This integration allows cross-account and cross-Area evaluation, customized dashboard creation, and information correlation with different AWS companies. For instance, you possibly can mix Storage Lens metrics with S3 Metadata to investigate prefix-level exercise patterns and establish objects in prefixes with chilly information which can be eligible for transition to lower-cost storage tiers.<\/p>\n

In your agentic AI workflows, you need to use pure language to question S3 Storage Lens metrics in S3 Tables with the S3 Tables MCP Server<\/a>. Brokers can ask questions similar to \u2018which buckets grew essentially the most final month?\u2019 or \u2018present me storage prices by storage class\u2019 and get prompt insights out of your observability information.<\/p>\n

Now obtainable
\n
<\/strong><\/span>All three enhancements can be found in all AWS Areas<\/a> the place S3 Storage Lens is at present provided (besides the China Areas and AWS GovCloud (US)).<\/p>\n

These options are included within the Amazon S3 Storage Lens Superior tier at no extra cost past normal superior tier pricing. For the S3 Tables export, you pay just for S3 Tables storage, upkeep, and queries. There isn’t any extra cost for the export performance itself.<\/p>\n

To be taught extra about Amazon S3 Storage Lens efficiency metrics, assist for billions of prefixes, and export to S3 Tables, confer with the Amazon S3 consumer information<\/a>. For pricing particulars, go to the Amazon S3 pricing web page<\/a>.<\/p>\n

Veliswa Boya<\/a>.<\/p>\n

\n <\/div>\n\n","protected":false},"excerpt":{"rendered":"

Immediately, we\u2019re asserting three new capabilities for Amazon S3 Storage Lens that provide you with deeper insights into your storage efficiency and utilization patterns. With the addition of efficiency metrics, assist for analyzing billions of prefixes, and direct export to Amazon S3 Tables, you have got the instruments you must optimize software efficiency, scale back […]<\/p>\n","protected":false},"author":1,"featured_media":20134,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[20],"tags":[],"class_list":{"0":"post-20132","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-cloud-computing"},"_links":{"self":[{"href":"https:\/\/aireviewirush.com\/index.php?rest_route=\/wp\/v2\/posts\/20132","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aireviewirush.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/aireviewirush.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/aireviewirush.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/aireviewirush.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=20132"}],"version-history":[{"count":1,"href":"https:\/\/aireviewirush.com\/index.php?rest_route=\/wp\/v2\/posts\/20132\/revisions"}],"predecessor-version":[{"id":20133,"href":"https:\/\/aireviewirush.com\/index.php?rest_route=\/wp\/v2\/posts\/20132\/revisions\/20133"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/aireviewirush.com\/index.php?rest_route=\/wp\/v2\/media\/20134"}],"wp:attachment":[{"href":"https:\/\/aireviewirush.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=20132"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aireviewirush.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=20132"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aireviewirush.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=20132"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}