Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
B
blog
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
nimrod
blog
Commits
e5a98772
Commit
e5a98772
authored
8 years ago
by
nimrod
Browse files
Options
Downloads
Patches
Plain Diff
- Correct entry.
parent
6c6fadd3
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
content/aws_change_own_password.rst
+6
-6
6 additions, 6 deletions
content/aws_change_own_password.rst
with
6 additions
and
6 deletions
content/aws_change_own_password.rst
+
6
−
6
View file @
e5a98772
...
...
@@ -5,12 +5,12 @@ Self service AWS IAM policy
:summary: AWS IAM policy to allow users to change their own password and manage
their own keys.
A common practice for me a new member joins the team or when someone
forgets
his/ her AWS account password is to change the account password myself,
send the
new password over a unsecure channel (email, Slack) but force the
account to
change the password on first login. Also, I prefer to have users
manage their
own keys to AWS themselves. But without the correct IAM policy
users aren't able
to perform either action. Here's an IAM to allow both:
A common practice for me
when
a new member joins the team or when someone
forgets
his/ her AWS account password is to change the account password myself,
send the
new password over a
n
unsecure channel (email, Slack) but force the
account to
change the password on first login. Also, I prefer to have users
manage their
own keys to AWS themselves. But without the correct IAM policy
users aren't able
to perform either action. Here's an IAM to allow both:
.. code:: json
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment