SAML to AWS STS Keys Conversion icon

SAML to AWS STS Keys Conversion

by prolane.org · Developer Tools
Manifest V3 Free
View in Chrome Web Store Data as of 15 Oct 2026

Generates file with AWS STS Keys after logging in to AWS webconsole using SSO (SAML 2.0). It leverages 'assumeRoleWithSAML' API.

Users
10K
0 in 30 days
Rating
3.8 / 5
unchanged in 30 days
Ratings
9
0 in 30 days
Store rank
#9,476
#8,158 among extensions
Version
3.3
updated 20 Mar 2023

Users

monthly, 3 years
3,0006,50010KAug 2023Apr 2025Oct 2026
Latest, 15 Oct 2026: 10,000 usersMove the mouse over the chart for any month

Ratings count

monthly, 3 years
3711Aug 2023Apr 2025Oct 2026
Latest, 15 Oct 2026: 9 ratingsMove the mouse over the chart for any month

The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.

About SAML to AWS STS Keys Conversion

Google Chrome Extension which converts a SAML 2.0 assertion to AWS STS Keys (temporary credentials -> AccessKeyId, SecretAccessKey and SessionToken). ### Why this Chrome Extension? ### If you don't have any user administration setup within AWS Identity & Access Management (IAM) but instead rely on your corporate user directory, i.e. Microsoft Active Directory. Your company uses a SAML 2.0 Identity Provider (IDP) to log in to the AWS Web Management Console (Single Sign On). Then this Chrome Estension if for you! You run into trouble as soon as you would like to execute some fancy scripts from your computer which calls the AWS API's. When sending a request to the AWS API's you need credentials, meaning an AccessKey and SecretKey. You can easily generate these keys for each user in AWS IAM. However, since you don't have any users in AWS IAM and don't want to create users just for the sake of having an AccessKey and SecretKey you are screwed. But there is a way to get temporary credentials specifically for your corporate identity. The Security Token Service (STS) from AWS provides an API action assumeRoleWithSAML. Using the SAML Assertion given by your IDP the Chrome Extension will call this API action to fetch temporary credentials. (AccessKeyId, SecretAccessKey and SessionToken). This way there is no need to create some sort of anonymous user in AWS IAM used for executing scripts. This would be a real security nightmare, since it won't be possible to audit who did what. This Chrome Extension however will make it super easy for you to just use your corporate identity for executing scripts calling AWS API's.

Growth

WindowUsersChangeRatingsRating
7 days0+0.0%00.00
30 days0+0.0%00.00
6 months0+0.0%00.00
1 year0+0.0%00.00

Version history

5 versions recorded
3.320 Mar 2023
3.219 Dec 2022
3.116 Dec 2022
2.829 Jun 2022
2.78 Feb 2019

Details

Category
Developer Tools
First seen
8 Feb 2019
Size
157 KB
Languages
en
Pricing
Free
Extension ID
ekniobabpcnfjgfbphhcolcinmnbehde

Permissions and risk

Moderate riskimpact 3, likelihood 1
Permissions
webRequeststoragedownloads
Site access
<all_urls>
Can read and change data on every website you visit.

Alternatives to SAML to AWS STS Keys Conversion

Extensions that rank for the same store searches or share the Developer Tools category, ordered by users