AWS solutions documentation change
Summary
Corrected typo in 'Prebid Server', added S3 storage documentation, updated configuration reference link, and added detailed section about S3 bucket structure for stored requests
Security assessment
Changes focus on documentation accuracy and operational details of S3 storage for Prebid Server features. No security controls, vulnerabilities, or access policies are mentioned. The S3 bucket retention notice is operational rather than security-focused.
Diff
diff --git a/solutions/latest/prebid-server-deployment-on-aws/configure-the-solution.md b/solutions/latest/prebid-server-deployment-on-aws/configure-the-solution.md index 5db472713..ebb85b8ff 100644 --- a//solutions/latest/prebid-server-deployment-on-aws/configure-the-solution.md +++ b//solutions/latest/prebid-server-deployment-on-aws/configure-the-solution.md @@ -9 +9 @@ Opting out of using CloudFront and AWS WAFManaging configuration files for the s -This section provides instructions for configuring the Prebid Servcer Deployment on AWS solution. +This section provides instructions for configuring the Prebid Server Deployment on AWS solution. @@ -147 +147,3 @@ Contains the core configuration for running Prebid Server. This file manages set -Refer to the [Prebid Server Configuration Guide](https://docs.prebid.org/prebid-server/host-config.html) for detailed usage instructions. + * S3 storage + +Refer to the [full list of application configuration options](https://github.com/prebid/prebid-server-java/blob/master/docs/config-app.md) for detailed usage instructions. @@ -217,0 +220,29 @@ By maintaining a clear separation between default and custom configurations and +### S3 Bucket for stored requests + +An S3 bucket for the "stored requests" functionality of Prebid Server is created automatically by the stack. Use the following procedure to locate this bucket: + + 1. **Access the CloudFormation stack outputs** \- Sign in to the [AWS CloudFormation console](https://console.aws.amazon.com/cloudformation). + + 2. **Select the Prebid Server stack** \- From the list of stacks, select the stack that is responsible for creating your Prebid Server environment. + + 3. **View the outputs** \- After selecting the stack, choose the **Outputs** tab. + + 4. **Locate the S3 bucket link** \- Find the **Output** entry that starts with `PrebidStoredRequestsBucket`. This output contains a direct link to the S3 bucket. + + 5. Click the link to access the bucket. You’ll find it preconfigured with the following directory structure: + + * `stored_requests/` \- Use this directory to store OpenRTB request templates. Stored requests define default values for requests, allowing clients to send only a reference ID while the server merges in the full configuration. + + * `stored_impressions/` \- Use this directory to store impression definitions for OpenRTB requests. This allows commonly used ad slot configurations to be reused without sending the full impression object in each request. Clients can reference these stored IDs in their request. + + * `stored_responses/` \- Use this directory to store static responses that Prebid Server can return in place of making real bid calls to demand partners. + + * `stored_accounts/` \- Use this directory to store publisher account definitions for OpenRTB requests. Each file defines account-specific settings, such as enabled modules or privacy enforcement rules. + + + + +This S3 bucket is retained after the stack is deleted. To delete the bucket, see [Deleting the Amazon S3 buckets](./uninstall-the-solution.html#deleting-the-amazon-s3-buckets). + +For detailed information about using stored requests and other types of stored data with Prebid Server, see the [Prebid Server documentation on Setting Up Stored Requests](https://docs.prebid.org/prebid-server/features/pbs-storedreqs-java.html). +