AWS solutions documentation change
Summary
Updated documentation links and GitHub repository references
Security assessment
Changes involve URL updates and repository path corrections without any security-specific content modifications or vulnerability references.
Diff
diff --git a/solutions/latest/prebid-server-deployment-on-aws/security-1.md b/solutions/latest/prebid-server-deployment-on-aws/security-1.md index 04e171ce8..490c9875a 100644 --- a//solutions/latest/prebid-server-deployment-on-aws/security-1.md +++ b//solutions/latest/prebid-server-deployment-on-aws/security-1.md @@ -3 +3 @@ -[Documentation](/index.html)[Prebid Server Deployment on AWS](https://aws.amazon.com/solutions/implementations/prebid-server-deployment-on-aws/)[Implementation Guide](solution-overview.html) +[Documentation](/index.html)[Guidance for Deploying a Prebid Server on AWS](https://aws.amazon.com/solutions/guidance/deploying-a-prebid-server-on-aws/)[Implementation Guide](solution-overview.html) @@ -31 +31 @@ Amazon VPC is configured with multiple subnets, routes, security groups, and NAT -This solution uses Amazon ECS to containerize the Prebid Server. The container runs the open source Prebid Server and is hosted by the Elastic Container Repository for AWS Solutions. A custom build is applied to the open source project’s default container in configuration settings for areas including file output and bidder adapter. To see how the ECS containers are constructed, refer to the [Dockerfile](https://github.com/aws-solutions/prebid-server-deployment-on-aws/blob/main/deployment/ecr/prebid-server/Dockerfile). If you need to access these containers while they are running in Fargate, see [Using Amazon ECS Exec to access your containers on AWS Fargate and Amazon EC2](https://aws.amazon.com/blogs/containers/new-using-amazon-ecs-exec-access-your-containers-fargate-ec2/) on the _AWS Blog_. +This solution uses Amazon ECS to containerize the Prebid Server. The container runs the open source Prebid Server and is hosted by the Elastic Container Repository for AWS Solutions. A custom build is applied to the open source project’s default container in configuration settings for areas including file output and bidder adapter. To see how the ECS containers are constructed, refer to the [Dockerfile](https://github.com/aws-solutions-library-samples/prebid-server-deployment-on-aws/blob/main/deployment/ecr/prebid-server/Dockerfile). If you need to access these containers while they are running in Fargate, see [Using Amazon ECS Exec to access your containers on AWS Fargate and Amazon EC2](https://aws.amazon.com/blogs/containers/new-using-amazon-ecs-exec-access-your-containers-fargate-ec2/) on the _AWS Blog_.