# AWS Security Token Service (AWS STS)

Cloud service · AWS. Updated 2026-11-12. Page: https://blowstack.com/tools/cloud-services-hub/aws-security-token-service-(aws-sts)

> AWS Security Token Service (AWS STS) is a web service that enables you to request temporary, limited-privilege credentials for AWS Identity and Access Management (IAM) users or for users that you authenticate (federated users).

Practice exams covering AWS Security Token Service (AWS STS): [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner), [SOA-C03 AWS Certified CloudOps Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate), [DEA-C01 AWS Certified Data Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate), [DVA-C02 AWS Certified Developer - Associate](https://blowstack.com/practice-exams/aws-certified-developer-associate), [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional), [AIP-C01 AWS Certified Generative AI Developer - Professional](https://blowstack.com/practice-exams/aws-certified-generative-ai-developer-professional), [MLA-C02 (beta) AWS Certified Machine Learning Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-machine-learning-engineer-associate), [SCS-C03 AWS Certified Security - Specialty](https://blowstack.com/practice-exams/aws-certified-security-specialty), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate), [SAP-C02 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 6 key features of AWS Security Token Service (AWS STS)

AWS Security Token Service (AWS STS) features include the creation of temporary credentials, permission control through fine-grained access, integration with external identity providers for federated access, facilitation of cross-account access, support for multi-factor authentication, and operation as a globally available service.

1. **Temporary Credentials**: AWS Security Token Service allows the creation of temporary, short-term credentials that can be used to access AWS resources. These temporary credentials are a more secure alternative to using long-term access keys.
2. **Permission Control**: With AWS STS, you can define specific permissions for the temporary credentials, ensuring that applications and users have only the access they need, thus following the principle of least privilege.
3. **Active Directory Integration**: AWS STS supports federated identities, allowing users to authenticate with external identity providers (like Active Directory or LinkedIn) and then assume an IAM role with permissions for accessing AWS resources.
4. **Cross-Account Access**: It facilitates cross-account access, enabling the creation of trust relationships between AWS accounts or between an AWS account and an external identity provider. This simplifies managing permissions across AWS accounts.
5. **Multi-Factor Authentication Support**: AWS STS supports multi-factor authentication (MFA), adding an extra layer of security by requiring users to provide additional verification before being granted the temporary credentials.
6. **Global Service**: Session tokens from Regional AWS STS endpoints are valid in all Regions. Tokens from the global endpoint are valid only in Regions enabled by default unless that endpoint is configured to issue tokens valid in all Regions.

## Where AWS Security Token Service (AWS STS) is used

AWS Security Token Service (AWS STS) use cases include providing temporary access to AWS resources, enabling secure cross-account access, facilitating federation with external identity systems, and enhancing security with support for Multi-factor Authentication (MFA).

1. **Temporary Access for Users**: AWS STS allows the creation of temporary security credentials for users who need to access AWS resources for a short-term project or task. This eliminates the need to manage long-term credentials for every user, enhancing security by automatically expiring credentials.
2. **Cross-account Access**: It enables secure delegation of access to resources across different AWS accounts without having to share long-term access keys. By using AWS STS, administrators can grant users from one AWS account permissions to access resources in another account in a secure and controlled manner.
3. **Federation with Identity Systems**: AWS STS facilitates federation with external identity systems such as Active Directory, SAML 2.0-compliant identity providers, or other OpenID Connect (OIDC) compliant providers, enabling users to sign in using their existing corporate credentials to access AWS resources.
4. **Multi-factor Authentication (MFA) for Enhanced Security**: AWS STS supports the use of Multi-factor Authentication (MFA), adding an additional layer of security. When temporary security credentials are requested, requiring MFA can significantly reduce the risk of unauthorized access.

## How AWS Security Token Service (AWS STS) is priced

AWS STS is free for use, with no direct charges for the service itself, but costs may be incurred for requests over 100,000 per month outside of free tier regions and for using the temporary credentials with other AWS services.

- **AWS Security Token Service (AWS STS) Pricing**: AWS Security Token Service (AWS STS) is essentially a free-to-use feature for AWS account holders. However, while there is no direct charge for using AWS STS, any requests made to AWS services using the temporary security credentials generated by AWS STS will incur standard AWS service fees according to the particular serviceâs pricing model.

## Services AWS Security Token Service (AWS STS) works with

- **[AWS Identity and Access Management (IAM)](https://blowstack.com/tools/cloud-services-hub/aws-identity-and-access-management-(iam))**: AWS STS works with IAM to help manage and control temporary security credentials for users and roles.
- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: Uses temporary security credentials from AWS STS to grant access to S3 buckets and objects securely.
- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: Allows EC2 instances to assume roles and gain temporary credentials to perform various tasks.
- **[Amazon RDS](https://blowstack.com/tools/cloud-services-hub/amazon-rds)**: Enables RDS instances or users to get temporary credentials for accessing databases securely.
- **[Amazon DynamoDB](https://blowstack.com/tools/cloud-services-hub/amazon-dynamodb)**: Grants temporary security credentials to interact with DynamoDB tables while adhering to the principle of least privilege.
- **[AWS Lambda](https://blowstack.com/tools/cloud-services-hub/aws-lambda)**: Lambda functions can assume roles and get temporary security credentials to access other AWS services.
- **[Amazon Redshift](https://blowstack.com/tools/cloud-services-hub/amazon-redshift)**: Uses temporary security credentials to control access to Redshift clusters and data.
- **[Amazon CloudWatch](https://blowstack.com/tools/cloud-services-hub/amazon-cloudwatch)**: Allows temporary access to CloudWatch for monitoring and managing AWS resources.
- **[Amazon API Gateway](https://blowstack.com/tools/cloud-services-hub/amazon-api-gateway)**: Integrates with API Gateway to grant temporary access tokens for API calls.
- **[AWS Glue](https://blowstack.com/tools/cloud-services-hub/aws-glue)**: Provides temporary security credentials to access data stored in S3, DynamoDB, and other resources for ETL jobs.
- **[Amazon SageMaker](https://blowstack.com/tools/cloud-services-hub/amazon-sagemaker)**: Grants temporary credentials to SageMaker for accessing data stores and other resources needed for machine learning tasks.
- **[AWS Step Functions](https://blowstack.com/tools/cloud-services-hub/aws-step-functions)**: Step Functions use temporary credentials to execute state machines that interact with other AWS services.
- **[Amazon EMR](https://blowstack.com/tools/cloud-services-hub/amazon-emr)**: Allows Amazon EMR clusters to use temporary credentials for accessing data and services securely.
- **[AWS CloudFormation](https://blowstack.com/tools/cloud-services-hub/aws-cloudformation)**: Uses temporary security credentials to provision and manage AWS resources defined in CloudFormation templates.
- **[Amazon AppFlow](https://blowstack.com/tools/cloud-services-hub/amazon-appflow)**: AWS STS provides temporary credentials for Amazon AppFlow's service-linked role, allowing AppFlow to manage connector credentials in AWS Secrets Manager without long-term access keys.
- **[Amazon Athena](https://blowstack.com/tools/cloud-services-hub/amazon-athena)**: AWS STS supplies temporary credentials for the execution role configured on an Athena for Apache Spark workgroup. The role controls access to resources such as the S3 buckets used by Spark calculations.
- **[Amazon Augmented AI (Amazon A2I)](https://blowstack.com/tools/cloud-services-hub/amazon-augmented-ai-(amazon-a2i))**: AWS STS lets Amazon A2I assume the execution role specified for a human review workflow. The resulting credentials authorize access to the workflow's input data and S3 output location.
- **[Amazon Aurora](https://blowstack.com/tools/cloud-services-hub/amazon-aurora)**: AWS STS lets Aurora assume IAM roles associated with a database cluster for supported AWS integrations. For example, a cluster can use role credentials to import data from S3 or invoke Lambda functions.
- **[Amazon Aurora Serverless](https://blowstack.com/tools/cloud-services-hub/amazon-aurora-serverless)**: AWS STS provides temporary credentials for IAM roles associated with Aurora Serverless v2 clusters. Supported database integrations use these roles for operations such as accessing S3 data.
- **[Amazon Bedrock](https://blowstack.com/tools/cloud-services-hub/amazon-bedrock)**: AWS STS lets Amazon Bedrock assume service roles for features such as agents, knowledge bases, and model customization. These roles grant temporary access to the data sources, vector stores, and other resources required by each feature.
- **[Amazon Bedrock AgentCore](https://blowstack.com/tools/cloud-services-hub/amazon-bedrock-agentcore)**: AWS STS provides temporary credentials for AgentCore Runtime execution roles. These credentials let hosted agents access authorized AWS resources without embedding long-term access keys.
- **[Amazon Braket](https://blowstack.com/tools/cloud-services-hub/amazon-braket)**: AWS STS supplies temporary credentials for the IAM roles used by Braket Hybrid Jobs and managed notebooks. Role policies control access to job inputs, results, container images, and other supporting resources.
- **[Amazon CloudFront](https://blowstack.com/tools/cloud-services-hub/amazon-cloudfront)**: AWS STS enables CloudFront to assume its VPC origins service-linked role. CloudFront uses that role to manage the network interfaces needed to reach origins inside a VPC.
- **[Amazon CodeGuru](https://blowstack.com/tools/cloud-services-hub/amazon-codeguru)**: AWS STS enables CodeGuru Reviewer to assume its service-linked role. The role authorizes operations needed to analyze associated repositories and publish code review findings.
- **[Amazon Cognito](https://blowstack.com/tools/cloud-services-hub/amazon-cognito)**: AWS STS exchanges identities authenticated through Cognito identity pools for temporary IAM role credentials. Cognito can obtain credentials for authenticated or guest users, with role policies limiting their AWS access.
- **[Amazon Comprehend](https://blowstack.com/tools/cloud-services-hub/amazon-comprehend)**: AWS STS lets Amazon Comprehend assume data access roles for asynchronous analysis and custom model workflows. Those roles authorize access to training data, analysis inputs, and output locations in S3.
- **[Amazon Connect](https://blowstack.com/tools/cloud-services-hub/amazon-connect)**: AWS STS enables Amazon Connect to assume its service-linked role to access resources configured for a contact center. These permissions support integrations such as streaming contact data to Kinesis.
- **[Amazon Data Firehose](https://blowstack.com/tools/cloud-services-hub/amazon-kinesis-data-firehose)**: AWS STS lets Firehose assume delivery stream IAM roles. The temporary credentials authorize operations such as writing records to S3, invoking a transformation Lambda function, or delivering data to OpenSearch.
- **[Amazon DataZone](https://blowstack.com/tools/cloud-services-hub/amazon-datazone)**: AWS STS lets Amazon DataZone assume domain execution and environment roles. These roles authorize DataZone to manage catalog resources, provision environments, and coordinate access to published data.
- **[Amazon Detective](https://blowstack.com/tools/cloud-services-hub/amazon-detective)**: AWS STS enables Amazon Detective to assume its service-linked role. Detective uses the role to perform supporting operations such as retrieving AWS Organizations information for organization-wide behavior graphs.
- **[Amazon DevOps Guru](https://blowstack.com/tools/cloud-services-hub/amazon-devops-guru)**: AWS STS enables DevOps Guru to assume its service-linked role. The resulting permissions let it inspect supported resources and monitoring data when generating operational insights.
- **[Amazon DocumentDB (with MongoDB compatibility)](https://blowstack.com/tools/cloud-services-hub/amazon-documentdb-(with-mongodb-compatibility))**: AWS STS participates directly in Amazon DocumentDB IAM database authentication. Supported MongoDB drivers use STS GetCallerIdentity requests to establish the IAM identity connecting to the database, including identities using temporary role credentials.
- **[Amazon EC2 Auto Scaling](https://blowstack.com/tools/cloud-services-hub/amazon-ec2-auto-scaling)**: AWS STS enables EC2 Auto Scaling to assume its service-linked role. This role authorizes scaling operations such as launching and terminating instances and registering instances with load balancers.
- **[Amazon ECS Anywhere](https://blowstack.com/tools/cloud-services-hub/amazon-ecs-anywhere)**: AWS STS provides temporary credentials for IAM roles assigned to ECS Anywhere tasks. The ECS credential mechanism delivers task-role credentials to containers running on registered external instances.
- **[Amazon EKS Anywhere](https://blowstack.com/tools/cloud-services-hub/amazon-eks-anywhere)**: AWS STS can exchange projected Kubernetes service account tokens from an EKS Anywhere cluster for IAM role credentials through AssumeRoleWithWebIdentity. This requires configuring the cluster's OIDC issuer as an IAM identity provider and establishing the role's trust policy.
- **[Amazon Elastic Block Store (Amazon EBS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-block-store-(amazon-ebs))**: AWS STS lets Amazon Data Lifecycle Manager assume execution roles for EBS snapshot lifecycle policies. Those roles authorize scheduled snapshot creation, copying, retention, and deletion.
- **[Amazon Elastic Container Registry (Amazon ECR)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-container-registry-(amazon-ecr))**: AWS STS enables ECR to assume its replication service-linked role. ECR uses the role to replicate container images into configured destination registries.
- **[Amazon Elastic Container Service (Amazon ECS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-container-service-(amazon-ecs))**: AWS STS issues temporary credentials for ECS task roles and task execution roles. ECS delivers task-role credentials to application containers and uses execution-role permissions for operations such as pulling images and sending container logs.
- **[Amazon Elastic File System (Amazon EFS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-file-system-(amazon-efs))**: AWS STS enables EFS to assume the role used for file system replication. The role authorizes replication operations against the destination file system, including supported cross-account configurations.
- **[Amazon Elastic Kubernetes Service (Amazon EKS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-kubernetes-service-(amazon-eks))**: AWS STS supports IAM roles for service accounts through AssumeRoleWithWebIdentity and supplies credentials for EKS Pod Identity through AssumeRoleForPodIdentity. Both mechanisms give pods temporary AWS credentials governed by IAM role policies.
- **[Amazon ElastiCache](https://blowstack.com/tools/cloud-services-hub/amazon-elasticache)**: AWS STS enables ElastiCache to assume its service-linked role. ElastiCache uses the role to manage supporting resources such as network interfaces and security group associations.
- **[Amazon EventBridge](https://blowstack.com/tools/cloud-services-hub/amazon-eventbridge)**: AWS STS lets EventBridge assume execution roles configured for rules, schedules, and pipes. Those roles authorize actions such as invoking targets, reading source records, and sending events across accounts.
- **[Amazon Forecast](https://blowstack.com/tools/cloud-services-hub/amazon-forecast)**: AWS STS lets Amazon Forecast assume IAM roles configured for dataset imports and exports. The temporary credentials authorize access to the relevant S3 locations and encryption keys.
- **[Amazon Fraud Detector](https://blowstack.com/tools/cloud-services-hub/amazon-fraud-detector)**: AWS STS lets Amazon Fraud Detector assume data access roles for supported training and batch workflows. These roles authorize reading event data from S3 and writing batch prediction results.
- **[Amazon FSx](https://blowstack.com/tools/cloud-services-hub/amazon-fsx-(for-all-types))**: AWS STS enables Amazon FSx to assume service-linked roles used to manage file system infrastructure. These roles authorize operations on supporting resources such as VPC network interfaces.
- **[Amazon GameLift](https://blowstack.com/tools/cloud-services-hub/amazon-gamelift)**: AWS STS supplies temporary credentials for IAM roles assigned to GameLift fleets. Game server processes can obtain fleet role credentials through GameLift's supported credential mechanism instead of storing access keys on fleet instances.
- **[Amazon GuardDuty](https://blowstack.com/tools/cloud-services-hub/amazon-guardduty)**: GuardDuty analyzes AWS STS activity recorded in CloudTrail management events. This helps detect suspicious role assumptions and anomalous use of temporary credentials.
- **[Amazon HealthLake](https://blowstack.com/tools/cloud-services-hub/amazon-healthlake)**: AWS STS lets HealthLake assume data access roles specified for import and export jobs. The role credentials authorize reading or writing FHIR data in S3.
- **[Amazon Inspector](https://blowstack.com/tools/cloud-services-hub/amazon-inspector)**: AWS STS enables Amazon Inspector to assume its service-linked roles. Inspector uses these permissions to discover resources and perform vulnerability assessment operations.
- **[Amazon Kendra](https://blowstack.com/tools/cloud-services-hub/amazon-kendra)**: AWS STS lets Kendra assume IAM roles configured for indexes and data source connectors. These roles authorize operations such as reading source documents, retrieving connector secrets, and writing logs.
- **[Amazon Keyspaces (for Apache Cassandra)](https://blowstack.com/tools/cloud-services-hub/amazon-keyspaces-(for-apache-cassandra))**: AWS STS enables Amazon Keyspaces to assume its replication service-linked role. The role supports the service operations required for multi-Region replication.
- **[Amazon Lex](https://blowstack.com/tools/cloud-services-hub/amazon-lex)**: AWS STS lets Amazon Lex assume bot runtime roles. These roles grant temporary access to configured resources such as Polly voices, Comprehend analysis, and conversation log destinations.
- **[Amazon Lightsail](https://blowstack.com/tools/cloud-services-hub/amazon-lightsail)**: AWS STS enables Lightsail to assume service-linked roles for supported resource management features. For example, its export role authorizes exporting Lightsail snapshots to Amazon EC2.
- **[Amazon Macie](https://blowstack.com/tools/cloud-services-hub/amazon-macie)**: AWS STS enables Macie to assume its service-linked role and sensitive data discovery role. These roles authorize S3 inventory inspection and access to objects selected for sensitive data analysis.
- **[Amazon Managed Blockchain](https://blowstack.com/tools/cloud-services-hub/amazon-managed-blockchain)**: AWS STS enables Managed Blockchain to assume its service-linked role. The service uses that role to manage supporting infrastructure such as network resources for blockchain networks.
- **[Amazon Managed Grafana](https://blowstack.com/tools/cloud-services-hub/amazon-managed-grafana)**: AWS STS lets Amazon Managed Grafana assume workspace and cross-account data source roles. This gives dashboards temporary, policy-controlled access to sources such as CloudWatch and Amazon Managed Service for Prometheus.
- **[Amazon Managed Service for Apache Flink](https://blowstack.com/tools/cloud-services-hub/amazon-managed-service-for-apache-flink)**: AWS STS lets Managed Service for Apache Flink assume an application's execution role. The role authorizes access to configured sources, destinations, application artifacts, and log groups.
- **[Amazon Managed Service for Prometheus](https://blowstack.com/tools/cloud-services-hub/amazon-managed-service-for-prometheus)**: AWS STS enables managed Prometheus scrapers to assume their service-linked role. The role provides the permissions needed to discover and collect metrics from configured EKS environments.
- **[Amazon Managed Streaming for Apache Kafka](https://blowstack.com/tools/cloud-services-hub/amazon-managed-streaming-for-apache-kafka)**: AWS STS enables Amazon MSK to assume service-linked roles for cluster infrastructure and execution roles for MSK Connect connectors. Connector roles authorize access to the AWS resources used by a connector.
- **[Amazon Managed Workflows for Apache Airflow (Amazon MWAA)](https://blowstack.com/tools/cloud-services-hub/amazon-managed-workflows-for-apache-airflow-(amazon-mwaa))**: AWS STS lets Amazon MWAA assume an environment's execution role. The role authorizes access to DAG files, task queues, encryption keys, and monitoring destinations.
- **[Amazon MemoryDB for Redis](https://blowstack.com/tools/cloud-services-hub/amazon-memorydb-for-redis)**: AWS STS enables MemoryDB to assume its service-linked role. MemoryDB uses the role to manage supporting network resources for clusters.
- **[Amazon Monitron](https://blowstack.com/tools/cloud-services-hub/amazon-monitron)**: AWS STS enables Monitron to assume its service-linked role. The role supports operations such as looking up users and groups through IAM Identity Center.
- **[Amazon MQ](https://blowstack.com/tools/cloud-services-hub/amazon-mq)**: AWS STS enables Amazon MQ to assume its service-linked role. Amazon MQ uses the role to manage network interfaces and other supporting resources for brokers.
- **[Amazon Neptune](https://blowstack.com/tools/cloud-services-hub/amazon-neptune)**: AWS STS lets Neptune assume IAM roles associated with a database cluster. For example, the bulk loader uses an associated role to read graph data from S3.
- **[Amazon OpenSearch Service](https://blowstack.com/tools/cloud-services-hub/amazon-opensearch-service)**: AWS STS lets OpenSearch Service assume roles for features such as manual snapshots and OpenSearch Ingestion pipelines. These roles authorize access to snapshot buckets, pipeline sources, and destinations.
- **[Amazon Personalize](https://blowstack.com/tools/cloud-services-hub/amazon-personalize)**: AWS STS lets Amazon Personalize assume service roles for dataset imports and batch workflows. The role credentials authorize reading input data and writing results in S3.
- **[Amazon Q](https://blowstack.com/tools/cloud-services-hub/amazon-q)**: AWS STS lets Amazon Q Developer operational investigations assume configured IAM roles to inspect AWS resources. The role policies define which operational data an investigation can access.
- **[Amazon Q Business](https://blowstack.com/tools/cloud-services-hub/amazon-q-business)**: AWS STS lets Amazon Q Business assume service roles configured for applications and data source connectors. These roles authorize access to source content, connector secrets, and supporting AWS resources.
- **[Amazon QuickSight](https://blowstack.com/tools/cloud-services-hub/amazon-quicksight)**: AWS STS lets QuickSight assume IAM roles used to access AWS data sources. These roles authorize operations such as reading S3 datasets and querying Athena, including supported cross-account access.
- **[Amazon RDS Proxy](https://blowstack.com/tools/cloud-services-hub/amazon-rds-proxy)**: AWS STS lets RDS Proxy assume its configured IAM role. The role authorizes retrieving database credentials from Secrets Manager and decrypting them when required.
- **[Amazon Rekognition](https://blowstack.com/tools/cloud-services-hub/amazon-rekognition)**: AWS STS lets Rekognition assume IAM roles for supported video analysis and bulk image workflows. For example, a video analysis notification role authorizes publishing job completion messages to SNS.
- **[Amazon Route 53](https://blowstack.com/tools/cloud-services-hub/amazon-route-53)**: AWS STS enables Route 53 Resolver to assume its service-linked role. Resolver uses the role to manage network interfaces required by Resolver endpoints.
- **[Amazon SageMaker Data Wrangler](https://blowstack.com/tools/cloud-services-hub/amazon-sagemaker-data-wrangler)**: AWS STS supplies temporary credentials for the SageMaker execution roles used by Data Wrangler. Those roles control access to imported datasets, query services, and output locations.
- **[Amazon SageMaker Ground Truth](https://blowstack.com/tools/cloud-services-hub/amazon-sagemaker-ground-truth)**: AWS STS lets Ground Truth assume the execution role configured for a labeling job. The role authorizes access to input objects, output locations, and other resources required by the labeling workflow.
- **[Amazon Security Lake](https://blowstack.com/tools/cloud-services-hub/amazon-security-lake)**: AWS STS lets Security Lake assume roles used by data lake operations and custom sources. Custom source providers can assume a configured role to write security records to the designated S3 location.
- **[Amazon Simple Email Service (Amazon SES)](https://blowstack.com/tools/cloud-services-hub/amazon-simple-email-service-(amazon-ses))**: AWS STS lets SES assume an IAM role configured on an email receiving rule's S3 action. The role authorizes storing received messages in the destination bucket and using the configured encryption key.
- **[Amazon Simple Notification Service (Amazon SNS)](https://blowstack.com/tools/cloud-services-hub/amazon-simple-notification-service-(amazon-sns))**: AWS STS lets SNS assume IAM roles configured for delivery status logging. SNS uses the resulting credentials to publish delivery success and failure information to CloudWatch Logs.
- **[Amazon Textract](https://blowstack.com/tools/cloud-services-hub/amazon-textract)**: AWS STS lets Textract assume the notification role supplied to asynchronous document analysis jobs. The role authorizes publishing job completion notifications to SNS.
- **[Amazon Timestream](https://blowstack.com/tools/cloud-services-hub/amazon-timestream)**: AWS STS lets Timestream assume the execution role configured for a scheduled query. The role authorizes running the query, writing results, publishing notifications, and reporting errors.
- **[Amazon Timestream for InfluxDB](https://blowstack.com/tools/cloud-services-hub/amazon-timestream-for-influxdb)**: AWS STS enables Timestream for InfluxDB to assume its service-linked role. The service uses the role to manage supporting infrastructure, including network interfaces and database credential secrets.
- **[Amazon Transcribe](https://blowstack.com/tools/cloud-services-hub/amazon-transcribe)**: AWS STS lets Transcribe assume data access roles for supported transcription and Call Analytics jobs. These roles authorize access to audio inputs and configured output destinations.
- **[Amazon Translate](https://blowstack.com/tools/cloud-services-hub/amazon-translate)**: AWS STS lets Amazon Translate assume the data access role specified for a batch translation job. The role authorizes reading source documents and writing translated documents in S3.
- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: AWS STS supports interface VPC endpoints, allowing workloads to reach regional STS APIs through private IP addresses. Endpoint policies can further restrict which STS requests may pass through an endpoint.
- **[Amazon WorkSpaces](https://blowstack.com/tools/cloud-services-hub/amazon-workspaces)**: AWS STS enables WorkSpaces to assume its service-linked roles. These roles authorize the supporting resource and network operations needed to provision and manage desktops.
- **[Amazon WorkSpaces Applications](https://blowstack.com/tools/cloud-services-hub/amazon-appstream-2)**: AWS STS provides temporary credentials for IAM roles assigned to WorkSpaces Applications fleets and image builders. Applications in a streaming session can receive role credentials through the service's application credential mechanism.
- **[Amazon WorkSpaces Secure Browser](https://blowstack.com/tools/cloud-services-hub/amazon-workspaces-web)**: AWS STS enables WorkSpaces Secure Browser to assume its service-linked role. The role authorizes management of network interfaces that connect browser sessions to a configured VPC.
- **[AWS Amplify](https://blowstack.com/tools/cloud-services-hub/aws-amplify)**: AWS STS lets Amplify Hosting assume configured service roles for application builds and deployments. Compute roles can also provide temporary AWS credentials to supported server-side application code.
- **[AWS App Runner](https://blowstack.com/tools/cloud-services-hub/aws-app-runner)**: AWS STS provides temporary credentials for App Runner access roles and instance roles. Access roles authorize image retrieval from ECR, while instance roles grant permissions to the running application.
- **[AWS AppConfig](https://blowstack.com/tools/cloud-services-hub/aws-appconfig)**: AWS STS lets AppConfig assume retrieval roles configured for externally stored configuration data. AppConfig extensions can also use configured IAM roles to perform actions against other AWS resources.
- **[AWS Application Discovery Service](https://blowstack.com/tools/cloud-services-hub/aws-application-discovery-service)**: AWS STS enables Application Discovery Service to assume its continuous export service-linked role. The role authorizes creating and managing the S3, Glue, Athena, and Firehose resources used to export discovery data.
- **[AWS Application Migration Service](https://blowstack.com/tools/cloud-services-hub/aws-application-migration-service)**: AWS STS enables Application Migration Service to assume service-linked and migration roles. These roles authorize management of replication infrastructure and the launching of test and cutover instances.
- **[AWS AppSync](https://blowstack.com/tools/cloud-services-hub/aws-appsync)**: AWS STS lets AppSync assume service roles attached to data sources. Those roles authorize resolver operations against resources such as DynamoDB tables, Lambda functions, and OpenSearch domains.
- **[AWS Audit Manager](https://blowstack.com/tools/cloud-services-hub/aws-audit-manager)**: AWS STS enables Audit Manager to assume its service-linked role. Audit Manager uses the role to collect evidence from supported AWS services and manage assessment evidence.
- **[AWS Auto Scaling](https://blowstack.com/tools/cloud-services-hub/aws-auto-scaling)**: AWS STS enables Application Auto Scaling to assume service-linked roles for scalable resource types. These roles authorize adjusting resources such as ECS service task counts and DynamoDB provisioned capacity.
- **[AWS Backup](https://blowstack.com/tools/cloud-services-hub/aws-backup)**: AWS STS lets AWS Backup assume IAM roles specified for backup and restore operations. Role permissions determine which protected resources AWS Backup can access and restore.
- **[AWS Batch](https://blowstack.com/tools/cloud-services-hub/aws-batch)**: AWS STS provides temporary credentials for Batch job roles, task execution roles, and service roles. These separate permissions for application code from permissions used to launch jobs, retrieve images, and publish logs.
- **[AWS Budgets](https://blowstack.com/tools/cloud-services-hub/aws-budgets)**: AWS STS lets AWS Budgets assume the execution role configured for a budget action. The role authorizes actions such as applying an IAM policy or stopping selected EC2 and RDS resources when a threshold is reached.
- **[AWS Certificate Manager (ACM)](https://blowstack.com/tools/cloud-services-hub/aws-certificate-manager-(acm))**: AWS STS enables ACM to assume its service-linked role for private certificate management. ACM uses the role to request replacement certificates from AWS Private CA during managed renewal.
- **[AWS Chatbot](https://blowstack.com/tools/cloud-services-hub/aws-chatbot)**: AWS STS lets AWS Chatbot assume channel and user roles when executing AWS commands from chat. Role policies and channel guardrails limit the operations available to chat users.
- **[AWS Clean Rooms](https://blowstack.com/tools/cloud-services-hub/aws-clean-rooms)**: AWS STS lets Clean Rooms assume configured analysis roles to access collaboration data. The roles authorize access to underlying tables, S3 data, and encryption keys while analysis rules govern permitted queries.
- **[AWS Client VPN](https://blowstack.com/tools/cloud-services-hub/aws-client-vpn)**: AWS STS enables Client VPN to assume its service-linked role. Client VPN uses the role to manage network interfaces and supporting endpoint resources.
- **[AWS Cloud9](https://blowstack.com/tools/cloud-services-hub/aws-cloud9)**: AWS STS enables Cloud9 to assume its service-linked role. Cloud9 uses the role to manage EC2 environment resources and their lifecycle.
- **[AWS CloudHSM](https://blowstack.com/tools/cloud-services-hub/aws-cloudhsm)**: AWS STS enables CloudHSM to assume its service-linked role. The role authorizes management of the network interfaces and security groups required by CloudHSM clusters.
- **[AWS CloudShell](https://blowstack.com/tools/cloud-services-hub/aws-cloudshell)**: AWS STS enables CloudShell to assume its service-linked role for VPC environments. The role authorizes creating and managing network interfaces that connect a CloudShell environment to the selected VPC.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: CloudTrail records AWS STS API activity, including role assumptions and requests for federated credentials. Events identify the caller and session details, supporting audits of how temporary credentials were issued.
- **[AWS CodeArtifact](https://blowstack.com/tools/cloud-services-hub/aws-codeartifact)**: AWS STS supplies the service bearer token mechanism used by CodeArtifact authorization tokens. Calling GetAuthorizationToken requires sts:GetServiceBearerToken in addition to the applicable CodeArtifact permission.
- **[AWS CodeBuild](https://blowstack.com/tools/cloud-services-hub/aws-codebuild)**: AWS STS lets CodeBuild assume the service role configured for a build project. The role grants temporary access to source artifacts, build outputs, container registries, logs, and other build resources.
- **[AWS CodeConnections](https://blowstack.com/tools/cloud-services-hub/aws-codeconnections)**: AWS STS lets CodeConnections' repository synchronization features assume configured IAM roles. For example, CloudFormation Git sync uses a role to read deployment configuration and update the associated stack.
- **[AWS CodeDeploy](https://blowstack.com/tools/cloud-services-hub/aws-codedeploy)**: AWS STS lets CodeDeploy assume deployment service roles. These roles authorize operations such as updating deployment targets, managing load balancer traffic, and coordinating ECS or Lambda deployments.
- **[AWS CodePipeline](https://blowstack.com/tools/cloud-services-hub/aws-codepipeline)**: AWS STS lets CodePipeline assume pipeline service roles and action roles. Action roles can provide scoped, cross-account access to deployment resources and artifact stores.
- **[AWS Compute Optimizer](https://blowstack.com/tools/cloud-services-hub/aws-compute-optimizer)**: AWS STS enables Compute Optimizer to assume its service-linked role. The role authorizes reading resource configuration and monitoring information used to generate optimization recommendations.
- **[AWS Config](https://blowstack.com/tools/cloud-services-hub/aws-config)**: AWS STS lets AWS Config assume its recorder role or service-linked role. These roles authorize inspecting resource configurations and delivering configuration history and snapshots.
- **[AWS Control Tower](https://blowstack.com/tools/cloud-services-hub/aws-control-tower)**: AWS STS lets Control Tower assume administrative and execution roles across governed accounts. These roles authorize landing zone setup, account enrollment, and deployment of governance resources.
- **[AWS Data Exchange](https://blowstack.com/tools/cloud-services-hub/aws-data-exchange)**: AWS STS enables Data Exchange to assume its license management service-linked role. The role authorizes interactions with AWS License Manager for managing data subscription entitlements.
- **[AWS Data Pipeline](https://blowstack.com/tools/cloud-services-hub/aws-data-pipeline)**: AWS STS lets Data Pipeline assume its pipeline service role. The role authorizes orchestration operations such as launching EC2 instances and EMR clusters for pipeline activities.
- **[AWS Database Migration Service (AWS DMS)](https://blowstack.com/tools/cloud-services-hub/aws-database-migration-service-(aws-dms))**: AWS STS lets DMS assume roles configured for endpoints and service operations. For example, an S3 endpoint role grants access to migration data, while other roles authorize retrieving database credentials from Secrets Manager.
- **[AWS DataSync](https://blowstack.com/tools/cloud-services-hub/aws-datasync)**: AWS STS lets DataSync assume IAM roles configured for supported storage locations. An S3 location role grants the temporary permissions needed to read, write, and verify transferred objects.
- **[AWS DeepRacer](https://blowstack.com/tools/cloud-services-hub/aws-deepracer)**: AWS STS lets DeepRacer assume service roles used by its training and simulation workflows. These roles authorize access to model artifacts and supporting SageMaker and simulation resources.
- **[AWS Device Farm](https://blowstack.com/tools/cloud-services-hub/aws-device-farm)**: AWS STS enables Device Farm to assume its service-linked role for VPC connectivity. The role authorizes creating and managing network interfaces used to reach private test resources.
- **[AWS DevOps Agent](https://blowstack.com/tools/cloud-services-hub/aws-devops-agent)**: AWS STS lets DevOps Agent assume configured IAM roles to investigate operational issues in AWS accounts. The roles define which resources, telemetry, and operational data the agent can inspect.
- **[AWS Directory Service](https://blowstack.com/tools/cloud-services-hub/aws-directory-service)**: AWS STS enables Directory Service to assume service-linked roles for supported directory operations. For example, a dedicated role supports seamless domain joining by retrieving directory information and managing computer accounts.
- **[AWS Distro for OpenTelemetry](https://blowstack.com/tools/cloud-services-hub/aws-distro-for-opentelemetry)**: AWS STS can supply temporary role credentials to the AWS Distro for OpenTelemetry Collector's AWS authentication components. Configuring role assumption allows telemetry exporters to send data to authorized AWS destinations, including destinations in another account.
- **[AWS Elastic Beanstalk](https://blowstack.com/tools/cloud-services-hub/aws-elastic-beanstalk)**: AWS STS lets Elastic Beanstalk assume environment service roles. These roles authorize operations such as enhanced health monitoring and managed platform updates.
- **[AWS Elastic Disaster Recovery](https://blowstack.com/tools/cloud-services-hub/aws-elastic-disaster-recovery)**: AWS STS enables Elastic Disaster Recovery to assume its service-linked and recovery roles. These roles authorize managing replication resources and launching recovery instances.
- **[AWS Entity Resolution](https://blowstack.com/tools/cloud-services-hub/aws-entity-resolution)**: AWS STS lets Entity Resolution assume execution roles configured for matching and ID mapping workflows. The roles authorize reading source data and writing workflow results.
- **[AWS Fargate](https://blowstack.com/tools/cloud-services-hub/aws-fargate)**: AWS STS supplies temporary credentials for IAM roles used by workloads running on Fargate. For ECS tasks, execution-role credentials support image retrieval and logging, while task-role credentials are exposed to application containers.
- **[AWS Fault Injection Service](https://blowstack.com/tools/cloud-services-hub/aws-fault-injection-simulator-(aws-fis))**: AWS STS lets Fault Injection Service assume the execution role configured for an experiment. The role limits which resources the experiment can target and which fault actions it can perform.
- **[AWS Firewall Manager](https://blowstack.com/tools/cloud-services-hub/aws-firewall-manager)**: AWS STS enables Firewall Manager to assume service-linked roles for organization-wide security administration. The roles authorize inspecting resources and managing protections required by configured security policies.
- **[AWS Global Accelerator](https://blowstack.com/tools/cloud-services-hub/aws-global-accelerator)**: AWS STS enables Global Accelerator to assume its service-linked role. The role authorizes management of network interfaces used to route accelerator traffic to supported VPC endpoints.
- **[AWS Glue DataBrew](https://blowstack.com/tools/cloud-services-hub/aws-glue-databrew)**: AWS STS lets DataBrew assume IAM roles configured for projects and jobs. These roles authorize reading datasets, writing transformed output, and publishing job logs.
- **[AWS Health Dashboard](https://blowstack.com/tools/cloud-services-hub/aws-health-dashboard)**: AWS STS enables AWS Health to assume its Organizations service-linked role. The role supports organization-wide access to Health events affecting member accounts.
- **[AWS IAM Identity Center (AWS Single Sign-On)](https://blowstack.com/tools/cloud-services-hub/aws-iam-identity-center-(aws-single-sign-on))**: AWS STS supplies temporary role sessions for AWS account access granted through IAM Identity Center permission sets. Users receive short-lived credentials for the corresponding account role rather than IAM user access keys.
- **[AWS IoT Core](https://blowstack.com/tools/cloud-services-hub/aws-iot-core)**: AWS STS lets the AWS IoT credentials provider assume IAM roles referenced by role aliases. Devices authenticate with X.509 certificates and receive temporary AWS credentials scoped by the role and applicable policies.
- **[AWS IoT Device Defender](https://blowstack.com/tools/cloud-services-hub/aws-iot-device-defender)**: AWS STS lets IoT Device Defender assume roles configured for audit and notification features. These roles authorize security checks against IoT resources and publication of audit notifications.
- **[AWS IoT Device Management](https://blowstack.com/tools/cloud-services-hub/aws-iot-device-management)**: AWS STS lets IoT Device Management assume roles used by bulk registration workflows. A registration role grants access to provisioning templates and device registration data stored in S3.
- **[AWS IoT Greengrass](https://blowstack.com/tools/cloud-services-hub/aws-iot-greengrass)**: AWS STS supplies the temporary credentials obtained through the Greengrass token exchange role. Greengrass components use these credentials to access permitted AWS resources without storing long-term access keys.
- **[AWS IoT SiteWise](https://blowstack.com/tools/cloud-services-hub/aws-iot-sitewise)**: AWS STS enables IoT SiteWise to assume service-linked and configured service roles. These roles support operations such as gateway management and access to customer-managed storage resources.
- **[AWS Lake Formation](https://blowstack.com/tools/cloud-services-hub/aws-lake-formation)**: AWS STS lets Lake Formation assume roles associated with registered S3 locations. Lake Formation vends scoped temporary credentials to supported analytics services according to the caller's data permissions.
- **[AWS Launch Wizard](https://blowstack.com/tools/cloud-services-hub/aws-launch-wizard)**: AWS STS enables Launch Wizard to assume its service-linked role. The role authorizes deployment and management of AWS resources required by supported application deployments.
- **[AWS License Manager](https://blowstack.com/tools/cloud-services-hub/aws-license-manager)**: AWS STS enables License Manager to assume service-linked roles for license administration. These roles support resource discovery, organization-wide license tracking, and management of supported licensed infrastructure.
- **[AWS Managed Services (AMS)](https://blowstack.com/tools/cloud-services-hub/aws-managed-services-(ams))**: AWS STS lets AMS assume authorized roles in managed AWS accounts. These temporary sessions provide the permissions needed to operate, monitor, and maintain customer resources.
- **[AWS Management Console](https://blowstack.com/tools/cloud-services-hub/aws-management-console)**: Temporary credentials issued by AWS STS can be exchanged through the AWS federation sign-in endpoint for a console sign-in token. This lets a federation broker create an AWS Management Console session with the permissions and lifetime of the underlying temporary session.
- **[AWS Marketplace](https://blowstack.com/tools/cloud-services-hub/aws-marketplace)**: AWS STS enables AWS Marketplace to assume its license management service-linked role. The role supports managing entitlements and licenses for subscribed Marketplace products through AWS License Manager.
- **[AWS Migration Hub](https://blowstack.com/tools/cloud-services-hub/aws-migration-hub)**: AWS STS enables Migration Hub to assume its service-linked role. The role authorizes access to discovery and migration information used to track application migration progress.
- **[AWS Network Firewall](https://blowstack.com/tools/cloud-services-hub/aws-network-firewall)**: AWS STS enables Network Firewall to assume its service-linked role. The role authorizes management of the network resources required to deploy and operate firewall endpoints.
- **[AWS Organizations](https://blowstack.com/tools/cloud-services-hub/aws-organizations)**: Organizations service control policies can restrict AWS STS operations in member accounts, including role assumption. These policies provide organization-wide guardrails on obtaining temporary credentials without granting permissions themselves.
- **[AWS Outposts](https://blowstack.com/tools/cloud-services-hub/aws-outposts)**: AWS STS enables Outposts to assume its service-linked role. Outposts uses the role to manage supporting AWS resources, including network interfaces associated with Outposts infrastructure.
- **[AWS PrivateLink](https://blowstack.com/tools/cloud-services-hub/aws-privatelink)**: AWS STS exposes regional APIs through PrivateLink interface endpoints. Workloads can request temporary credentials over private connectivity without sending those requests through an internet gateway or NAT gateway.
- **[AWS Resilience Hub](https://blowstack.com/tools/cloud-services-hub/aws-resilience-hub)**: AWS STS lets Resilience Hub assume configured assessment roles, including roles in other accounts. These roles authorize reading application resource configurations and the information needed to assess resilience.
- **[AWS Resource Access Manager (AWS RAM)](https://blowstack.com/tools/cloud-services-hub/aws-resource-access-manager-(aws-ram))**: AWS STS enables AWS RAM to assume its service-linked role for sharing with AWS Organizations. The role authorizes reading organization structure and membership information needed to evaluate resource shares.
- **[AWS Resource Groups and Tag Editor](https://blowstack.com/tools/cloud-services-hub/aws-resource-groups-and-tag-editor)**: AWS STS lets Resource Groups assume the role configured for a tag-sync task. The role authorizes discovering tagged resources and updating membership of the associated resource group.
- **[AWS Security Hub](https://blowstack.com/tools/cloud-services-hub/aws-security-hub)**: AWS STS enables Security Hub to assume its service-linked role. Security Hub uses the role to inspect supported resource configurations and perform operations required by security checks and organization administration.
- **[AWS Service Catalog](https://blowstack.com/tools/cloud-services-hub/aws-service-catalog)**: AWS STS lets Service Catalog assume launch roles assigned to products through launch constraints. These roles authorize provisioning and updating product resources without giving end users the same underlying permissions.
- **[AWS Shield](https://blowstack.com/tools/cloud-services-hub/aws-shield)**: AWS STS lets the Shield Response Team assume a customer-authorized access role. The role and its external ID enable scoped access to help investigate and mitigate DDoS attacks.
- **[AWS Snow Family](https://blowstack.com/tools/cloud-services-hub/aws-snow-family)**: AWS STS lets Snow Family assume the service role associated with a data transfer job. The role authorizes access to the S3 buckets involved in importing or exporting data.
- **[AWS Systems Manager](https://blowstack.com/tools/cloud-services-hub/aws-systems-manager)**: AWS STS lets Systems Manager assume execution roles for Automation and other supported management workflows. Cross-account Automation can assume roles in target accounts to perform approved operations on their resources.
- **[AWS Transfer Family](https://blowstack.com/tools/cloud-services-hub/aws-transfer-family)**: AWS STS lets Transfer Family assume IAM roles assigned to users and workflows. User roles and optional session policies scope file access to authorized S3 objects or EFS resources.
- **[AWS Transit Gateway](https://blowstack.com/tools/cloud-services-hub/aws-transit-gateway)**: AWS STS enables Transit Gateway to assume its service-linked role. The role authorizes creating and managing network interfaces required by VPC attachments.
- **[AWS Trusted Advisor](https://blowstack.com/tools/cloud-services-hub/aws-trusted-advisor)**: AWS STS enables Trusted Advisor to assume its service-linked role. The role authorizes inspecting supported resource configurations to generate checks and recommendations.
- **[AWS User Notifications](https://blowstack.com/tools/cloud-services-hub/aws-user-notifications)**: AWS STS enables User Notifications to assume its service-linked role. The role authorizes managing EventBridge resources used to collect events for configured notifications.
- **[AWS Verified Access](https://blowstack.com/tools/cloud-services-hub/aws-verified-access)**: AWS STS enables Verified Access to assume its service-linked role. The role authorizes management of network interfaces used by Verified Access endpoints.
- **[AWS WAF](https://blowstack.com/tools/cloud-services-hub/aws-waf)**: AWS STS enables AWS WAF to assume its logging service-linked role for Firehose log delivery. The role authorizes sending web ACL request logs to the configured delivery stream.
- **[EC2 Image Builder](https://blowstack.com/tools/cloud-services-hub/ec2-image-builder)**: AWS STS lets Image Builder assume roles for image creation, lifecycle management, and cross-account distribution. These roles authorize operations such as managing build infrastructure and distributing AMIs into destination accounts.
- **[Elastic Load Balancing (ELB)](https://blowstack.com/tools/cloud-services-hub/elastic-load-balancing-(elb))**: AWS STS enables Elastic Load Balancing to assume its service-linked role. The role authorizes management of network interfaces and other supporting resources required by load balancers.
- **[Red Hat OpenShift Service on AWS (ROSA)](https://blowstack.com/tools/cloud-services-hub/red-hat-openshift-service-on-aws-(rosa))**: AWS STS provides temporary credentials for ROSA account roles and OpenShift operator roles. In STS-based deployments, operators exchange service account identity tokens for narrowly scoped AWS role credentials.
- **[VMware Cloud on AWS](https://blowstack.com/tools/cloud-services-hub/vmware-cloud-on-aws)**: AWS STS supports the cross-account role access established when VMware Cloud on AWS connects to a customer AWS account. The delegated role authorizes management of the AWS network resources needed for the connected VPC.

## What is AWS Security Token Service (AWS STS)

AWS Security Token Service (AWS STS) is a web service that enables you to request temporary, limited-privilege credentials for AWS Identity and Access Management (IAM) users or for users that you authenticate (federated users). Its primary function is to enhance the security posture of your AWS environment by enforcing the principle of least privilege, ensuring that entities within your environment have only the permissions they absolutely need to accomplish their tasks, and only for a limited period. This mitigates the risks associated with long-standing credentials which, if compromised, could lead to unauthorized access to your resources.

AWS STS plays a crucial role in the management of temporary credentials. It allows the creation of unique, temporary credentials that can be assigned to users or systems, automatically expiring after a definable period. This effectively reduces the risk of credential leakage or misuse since these credentials, even if compromised, are only valid for a short duration. Additionally, AWS STS provides the ability to grant cross-account access without the need to share long-term credentials, but the assumed role must have a trust policy authorizing the caller. This facilitates secure collaboration between different business units or companies while maintaining tight control over resource access.

For cross-account AssumeRole requests, only the calling account's STS quota is consumed; the target account's quota is not consumed.

One of the distinguished features of AWS STS is its integration with other AWS services and identity providers. It facilitates the federation of user identities by enabling users to sign in with their credentials from external identity providers like corporate directories, thus avoiding the need to create separate IAM users in AWS. This capability not only streamlines user access management but also leverages the security mechanisms of the external identity providers, such as multi-factor authentication.

AWS STS supports several use cases, including granting access to AWS resources from applications running on EC2 instances, managing permissions for applications on mobile devices or IoT devices, and providing access to AWS resources for users from external systems. By granting temporary access, AWS STS ensures that the principle of least privilege can be applied more effectively and securely across these diversified environments.

In operational terms, AWS STS is easy to implement through the AWS Management Console, the AWS Command Line Interface (CLI), or the AWS SDKs. It allows the generation of credentials dynamically, thereby enabling automation and integration into various application flows. The service itself is designed to be highly available and resilient, ensuring that the mechanism for generating and distributing temporary credentials does not become a bottleneck or single point of failure in your architecture.

AWS recommends using Regional STS endpoints rather than the global (legacy) endpoint to reduce latency and build in redundancy.

For requests made using AWS credentials, the default STS request quota is 600 requests per second per account per Region, shared by AssumeRole, DecodeAuthorizationMessage, GetAccessKeyInfo, GetCallerIdentity, GetFederationToken, and GetSessionToken.

STS requests made by AWS service principals do not consume your accounts' STS requests-per-second quota.

In conclusion, AWS Security Token Service is a critical component of AWS's security and identity services, offering a robust mechanism for managing temporary credentials and enabling secure, efficient access management across AWS environments. Its capabilities support the core security principles of least privilege and defense in depth, making it an indispensable tool for architects and developers looking to design secure cloud-based solutions.

## Free AWS Security Token Service (AWS STS) tools

- [AWS Access Key ID Decoder](https://blowstack.com/tools/aws-access-key-id-decoder): Decode an access key ID to its account and key type, and fix credential errors.
- [AWS Credentials Chain Troubleshooter](https://blowstack.com/tools/aws-credentials-chain-troubleshooter): Check role profiles - role_arn, source_profile, credential_source, MFA - per tool.
- [AWS IAM Access Denied Decoder](https://blowstack.com/tools/aws-iam-access-denied-decoder): Fix "not authorized to perform: sts:AssumeRole" and decode encoded authorization messages.
