Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
951d38b7
Commit
951d38b7
authored
Sep 14, 2017
by
Abubakar Ango
Committed by
Achilleas Pipinellis
Sep 14, 2017
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Updated Doc: Omitting AWS access key and ID key=>value pairs when using AWS IAM profiles
parent
1ab15ba2
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
5 deletions
+2
-5
doc/administration/job_artifacts.md
doc/administration/job_artifacts.md
+2
-5
No files found.
doc/administration/job_artifacts.md
View file @
951d38b7
...
...
@@ -116,16 +116,13 @@ _The artifacts are stored by default in
}
```
NOTE: If you are using AWS IAM profiles, you will need to specify a blank
AWS access key and ID until [this fog-aws
issue](https://github.com/fog/fog-aws/issues/162) is resolved. For example:
NOTE: For GitLab 9.4+, if you are using AWS IAM profiles, be sure to omit the
AWS access key and secret acces key/value pairs. For example:
```ruby
gitlab_rails['artifacts_object_store_connection'] = {
'provider' => 'AWS',
'region' => 'eu-central-1',
'aws_access_key_id' => '',
'aws_secret_access_key' => '',
'use_iam_profile' => true
}
```
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment