diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2019-11-12 06:06:32 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2019-11-12 06:06:32 +0000 |
| commit | 60877d1bff65fa4d2b74409d343d5b7615478891 (patch) | |
| tree | 997e11e2c885f2d951cedb5a7aea296436cb639e /doc/administration/packages/container_registry.md | |
| parent | 75687c79df805b57914d79cf217e3f08dbc77cc2 (diff) | |
| download | gitlab-ce-60877d1bff65fa4d2b74409d343d5b7615478891.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/administration/packages/container_registry.md')
| -rw-r--r-- | doc/administration/packages/container_registry.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/administration/packages/container_registry.md b/doc/administration/packages/container_registry.md index 980d4da65df..2444365d5ae 100644 --- a/doc/administration/packages/container_registry.md +++ b/doc/administration/packages/container_registry.md @@ -877,6 +877,6 @@ The above image shows: - The HEAD request to the AWS bucket reported a 403 Unauthorized. What does this mean? This strongly suggests that the S3 user does not have the right -[permissions to perform a HEAD request](https://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectHEAD.html). +[permissions to perform a HEAD request](https://docs.aws.amazon.com/AmazonS3/latest/API/API_HeadObject.html). The solution: check the [IAM permissions again](https://docs.docker.com/registry/storage-drivers/s3/). Once the right permissions were set, the error will go away. |