Skip to content
This repository was archived by the owner on Jun 28, 2023. It is now read-only.

Commit c156d50

Browse files
committed
Periodic update - 2023-04-07
1 parent 87426c4 commit c156d50

12 files changed

+251
-14
lines changed

doc_source/MultiRegionAccessPoints.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,8 @@ The following image is a graphical representation of an Amazon S3 Multi\-Region
1212

1313
![\[How manual failover between Regions works with an Amazon S3 Multi-Region Access Point in an active-passive configuration.\]](http://docs.aws.amazon.com/AmazonS3/latest/userguide/images/MultiRegionAccessPointsFailover.png)
1414

15+
To learn more about how to use Multi\-Region Access Points, see [Tutorial: Getting started with Amazon S3 Multi\-Region Access Points](http://aws.amazon.com/getting-started/hands-on/getting-started-with-amazon-s3-multi-region-access-points/?ref=docs_gateway/amazons3/MultiRegionAccessPoints.html)\.
16+
1517
**Topics**
1618
+ [Creating Multi\-Region Access Points](CreatingMultiRegionAccessPoints.md)
1719
+ [Configuring a Multi\-Region Access Point for use with AWS PrivateLink](MultiRegionAccessConfiguration.md)

doc_source/NotificationHowTo.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ Currently, Amazon S3 can publish notifications for the following events:
1919
+ Object tagging events
2020
+ Object ACL PUT events
2121

22-
For full descriptions of all the supported event types, see [Supported event types for SQS, SNS, and Lambda](notification-how-to-event-types-and-destinations.md#supported-notification-event-types)\.
22+
For full descriptions of all the supported event types, see [Supported event types for SQS, SNS, and Lambda](notification-how-to-event-types-and-destinations.md#supported-notification-event-types)\.
2323

2424
Amazon S3 can send event notification messages to the following destinations\. You specify the Amazon Resource Name \(ARN\) value of these destinations in the notification configuration\.
2525
+ Amazon Simple Notification Service \(Amazon SNS\) topics

doc_source/aws-usage-report.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# AWS usage report for Amazon S3<a name="aws-usage-report"></a>
22

3-
When you download a usage report, you can choose to aggregate usage data by hour, day, or month\. The Amazon S3 usage report lists operations by usage type and AWS Region\. For more detailed reports about your Amazon S3 storage usage, download dynamically generated AWS usage reports\. You can choose which usage type, operation, and time period to include\. You can also choose how the data is aggregated\.
3+
When you download a usage report, you can choose to aggregate usage data by hour, day, or month\. The Amazon S3 usage report lists operations by usage type and AWS Region\. For more detailed reports about your Amazon S3 storage usage, download dynamically generated AWS usage reports\. You can choose which usage type, operation, and time period to include\. You can also choose how the data is aggregated\. For more information about usage reports, see [AWS Usage Report](https://docs.aws.amazon.com/cur/latest/userguide/usage-report.html) in the *AWS Cost and Usage Reports User Guide*\.
44

55
The Amazon S3 usage report includes the following information:
66
+ **Service** – Amazon S3
@@ -40,11 +40,11 @@ You can download a usage report as an \.xml or a \.csv file\.
4040

4141
1. Sign in to the AWS Management Console and open the Amazon S3 console at [https://console\.aws\.amazon\.com/s3/](https://console.aws.amazon.com/s3/)\.
4242

43-
1. In the title bar, choose your user name or account ID, and then choose **My Billing Dashboard**\.
43+
1. In the title bar, choose your user name or account ID, and then choose **Billing Dashboard**\.
4444

45-
1. In the navigation pane, choose **AWS Cost & Usage Reports**\.
45+
1. In the navigation pane, choose **Cost & usage reports**\.
4646

47-
1. In the **Other Reports** section, choose **AWS Usage Report**\.
47+
1. Under AWS Usage Report, choose **Create a Usage Report**\.
4848

4949
1. For **Services**, choose **Amazon Simple Storage Service**\.
5050

doc_source/get-request-ids.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,9 +8,9 @@ After you've recovered these logs, copy and retain those two values, because you
88

99
## Using HTTP to obtain request IDs<a name="http-request-id"></a>
1010

11-
You can obtain your request IDs, `x-amz-request-id` and `x-amz-id-2`, by logging the bits of an HTTP request before it reaches the target application\. There are a variety of third\-party tools that you can use to recover verbose logs for HTTP requests\. When you run the tool, listen on the port that your Amazon S3 traffic travels on, as you send out another Amazon S3 HTTP request\.
11+
You can obtain your request IDs, `x-amz-request-id` and `x-amz-id-2` by logging the bits of an HTTP request before it reaches the target application\. There are a variety of third\-party tools that can be used to recover verbose logs for HTTP requests\. Choose one that you trust, and then run the tool to listen on the port that your Amazon S3 traffic travels on, as you send out another Amazon S3 HTTP request\.
1212

13-
For HTTP requests, the pair of request IDs will look like the following examples\.
13+
For HTTP requests, the pair of request IDs will look like the following:
1414

1515
```
1616
x-amz-request-id: 79104EXAMPLEB723
@@ -88,7 +88,7 @@ logger.info("HostId: %s", response['ResponseMetadata']['HostId'])
8888
logger.info("Date: %s", response['ResponseMetadata']['HTTPHeaders']['date'])
8989
```
9090

91-
You can also catch exceptions and log relevant information when an exception is raised\. For details, see [Discerning useful information from error responses](https://boto3.amazonaws.com/v1/documentation/api/latest/guide/error-handling.html#discerning-useful-information-from-error-responses) in the *AWS SDK for Python \(Boto\) API Reference*\.
91+
You can also catch exceptions and log relevant information when an exception is raised\. For more information, see [Discerning useful information from error responses](https://boto3.amazonaws.com/v1/documentation/api/latest/guide/error-handling.html#discerning-useful-information-from-error-responses) in the *AWS SDK for Python \(Boto\) API Reference*\.
9292

9393
Additionally, you can configure Boto3 to output verbose debugging logs by using the following code:
9494

@@ -101,7 +101,7 @@ For more information, see [https://boto3.amazonaws.com/v1/documentation/api/late
101101

102102
### Using the SDK for Ruby to obtain request IDs<a name="ruby-request-id"></a>
103103

104-
You can get your request IDs by using either the AWS SDK for Ruby \- Version 1, Version 2, or Version 3\.
104+
You can get your request IDs using the SDK for Ruby Versions 1, 2, or 3\.
105105
+ **Using the SDK for Ruby \- Version 1**– You can enable HTTP wire logging globally with the following line of code\.
106106

107107
```

doc_source/getting-started-next-steps.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,12 +76,15 @@ You can get started with step\-by\-step tutorials to learn more about Amazon S3\
7676
+ [Tutorial: Getting started using the Amazon S3 Glacier storage classes](http://aws.amazon.com/getting-started/hands-on/getting-started-using-amazon-s3-glacier-storage-classes/?ref=docs_gateway/amazons3/tutorials.html)
7777
+ [Tutorial: Optimizing costs and gaining visibility into usage with S3 Storage Lens](http://aws.amazon.com/getting-started/hands-on/amazon-s3-storage-lens/?ref=docs_gateway/amazons3/tutorials.html)
7878

79+
### Managing storage<a name="storage-management-tutorials"></a>
80+
+ [Tutorial: Getting started with Amazon S3 Multi\-Region Access Points](http://aws.amazon.com/getting-started/hands-on/getting-started-with-amazon-s3-multi-region-access-points/?ref=docs_gateway/amazons3/tutorials.html)
81+
7982
### Hosting videos and websites<a name="host-web-video-tutorials"></a>
8083
+ [Tutorial: Hosting on\-demand streaming video with Amazon S3, Amazon CloudFront, and Amazon Route 53](tutorial-s3-cloudfront-route53-video-streaming.md)
8184
+ [Tutorial: Configuring a static website on Amazon S3](HostingWebsiteOnS3Setup.md)
8285
+ [Tutorial: Configuring a static website using a custom domain registered with Route 53](website-hosting-custom-domain-walkthrough.md)
8386

84-
### Data processing<a name="data-processing-tutorials"></a>
87+
### Processing data<a name="data-processing-tutorials"></a>
8588
+ [Tutorial: Transforming data for your application with S3 Object Lambda](tutorial-s3-object-lambda-uppercase.md)
8689
+ [Tutorial: Detecting and redacting PII data with S3 Object Lambda and Amazon Comprehend](tutorial-s3-object-lambda-redact-pii.md)
8790
+ [Tutorial: Using S3 Object Lambda to dynamically watermark images as they are retrieved](http://aws.amazon.com/getting-started/hands-on/amazon-s3-object-lambda-to-dynamically-watermark-images/?ref=docs_gateway/amazons3/tutorials.html)

doc_source/grant-destinations-permissions-to-s3.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,8 @@
22

33
You must grant the Amazon S3 principal the necessary permissions to call the relevant API to publish messages to an SNS topic, an SQS queue, or a Lambda function\. This is so that Amazon S3 can publish event notification messages to a destination\.
44

5+
To troubleshoot publishing event notification messages to a destination, see [ Troubleshoot to publish Amazon S3 event notifications to an Amazon Simple Notification Service topic ](https://repost.aws/knowledge-center/sns-not-receiving-s3-event-notifications)\.
6+
57
**Topics**
68
+ [Granting permissions to invoke an AWS Lambda function](#grant-lambda-invoke-permission-to-s3)
79
+ [Granting permissions to publish messages to an SNS topic or an SQS queue](#grant-sns-sqs-permission-for-s3)

doc_source/index.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -589,10 +589,11 @@ sponsored by Amazon.
589589
+ [Detect people and objects in a video with Amazon Rekognition using an AWS SDK](example_cross_RekognitionVideoDetection_section.md)
590590
+ [Save EXIF and other image information using an AWS SDK](example_cross_DetectLabels_section.md)
591591
+ [Troubleshooting](troubleshooting.md)
592+
+ [Troubleshoot Access Denied (403 Forbidden) errors in Amazon S3](troubleshoot-403-errors.md)
592593
+ [Troubleshoot Batch Operations](troubleshooting-batch-operations.md)
593594
+ [Troubleshoot CORS](cors-troubleshooting.md)
594-
+ [Troubleshooting replication](replication-troubleshoot.md)
595595
+ [Troubleshoot Amazon S3 Lifecycle issues](troubleshoot-lifecycle.md)
596+
+ [Troubleshooting replication](replication-troubleshoot.md)
596597
+ [Troubleshoot server access logging](troubleshooting-server-access-logging.md)
597598
+ [Troubleshoot versioning](troubleshooting-versioning.md)
598599
+ [Getting Amazon S3 request IDs for AWS Support](get-request-ids.md)

doc_source/notification-how-to-event-types-and-destinations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Event notification types and destinations<a name="notification-how-to-event-types-and-destinations"></a>
22

3-
Amazon S3 supports several event notification types and destinations where the notifications can be published\. You can specify the event type and destination when configuring your event notifications\. Only one destination can be specified for each event notification\.
3+
Amazon S3 supports several event notification types and destinations where the notifications can be published\. You can specify the event type and destination when configuring your event notifications\. Only one destination can be specified for each event notification\. Amazon S3 event notifications send one event entry for each notification message\.
44

55
**Topics**
66
+ [Supported event destinations](#supported-notification-destinations)

0 commit comments

Comments
 (0)