<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/tutorial-how-to-configure-sso-for-aws-resources-with-okta-and-saml-sunbkvkqw" -->

---
title: Tutorial: How to Configure SSO for AWS Resources with...
description: A step-by-step tutorial walks through configuring single sign-on for AWS EC2 access using Okta as the identity provider, SAML for authentication, and Teleport...
canonical: https://daily.dev/posts/tutorial-how-to-configure-sso-for-aws-resources-with-okta-and-saml-sunbkvkqw
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Tutorial: How to Configure SSO for AWS Resources with Okta and SAML | daily.dev
og:description: A step-by-step tutorial walks through configuring single sign-on for AWS EC2 access using Okta as the identity provider, SAML for authentication, and Teleport...
og:url: https://daily.dev/posts/tutorial-how-to-configure-sso-for-aws-resources-with-okta-and-saml-sunbkvkqw
og:image: https://api.daily.dev/og/posts/SUnbKVKqw.png
og:image:alt: Tutorial: How to Configure SSO for AWS Resources with Okta and SAML
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Tutorial: How to Configure SSO for AWS Resources with Okta and SAML

**[Teleport](https://daily.dev/sources/teleport)** · 11 min read · 0 upvotes · 0 comments

## Summary

A step-by-step tutorial walks through configuring single sign-on for AWS EC2 access using Okta as the identity provider, SAML for authentication, and Teleport for role-based access control. It covers launching EC2 instances behind a Teleport bastion host, setting up Okta users, groups, and a SAML app, creating a Teleport SAML connector that maps Okta groups to Teleport roles, and verifying that developers and DBAs are restricted to their respective app or database servers.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://goteleport.com/blog/how-to-setup-aws-sso-with-okta-saml>

## Questions this post answers

### How do I map Okta groups to Teleport roles using a SAML connector?

Configure a Teleport SAML connector resource with an attributes_to_roles section that maps Okta group names (from the SAML group attribute statement) to Teleport role names, for example mapping the okta-admin group to the admin role, okta-dev to dev, and okta-dba to dba. The connector also requires the identity provider metadata XML downloaded from Okta's sign-on tab.

_daily.dev surfaces practical SSO and RBAC configuration guides for engineers wiring up identity providers._

### How do I restrict SSH access to specific EC2 instances based on Okta group membership using Teleport?

Create Teleport roles with node_labels matching a label assigned to specific EC2 instances, such as name=appserver or name=dbserver, then map each Okta group to the corresponding role via the SAML connector's attributes_to_roles setting. Users in the okta-developer group get a role scoped to appserver nodes, while okta-dba users get a role scoped to dbserver nodes, and access outside the matching label is denied.

_Teams enforcing least-privilege SSH access can find setup walkthroughs like this through daily.dev._

### How do I set up Teleport as an SSO-enabled bastion host for AWS EC2 instances?

Launch a Teleport proxy on a public-subnet EC2 instance, install Teleport Enterprise, and configure it with a cluster name and ACME email using teleport configure. Join private-subnet application and database servers to the cluster with generated node tokens, then switch the auth_service authentication type to saml in /etc/teleport.yaml (or apply a cluster_auth_preference resource on Teleport Cloud) so logins route through Okta.

_Engineers building bastion-host access architectures can track configuration walkthroughs on daily.dev._

## Similar posts on daily.dev

- [Avoid shared database accounts with federated IAM authentication](https://daily.dev/posts/avoid-shared-database-accounts-with-federated-iam-authentication-43szq2clb) · AWS Database Blog · 0 upvotes · 0 comments
- [The Ultimate Guide to Single Sign-On in 2025](https://daily.dev/posts/the-ultimate-guide-to-single-sign-on-in-2025-pxybfj6ei) · Security Boulevard · 0 upvotes · 0 comments
- [Examples of SAML Providers](https://daily.dev/posts/examples-of-saml-providers-aneafft7f) · Security Boulevard · 0 upvotes · 0 comments

---

Tags: [#aws](https://daily.dev/tags/aws), [#authentication](https://daily.dev/tags/authentication), [#okta](https://daily.dev/tags/okta)

[View this post on daily.dev](https://daily.dev/posts/tutorial-how-to-configure-sso-for-aws-resources-with-okta-and-saml-sunbkvkqw)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Tutorial: How to Configure SSO for AWS Resources with Okta and SAML","url":"https://daily.dev/posts/tutorial-how-to-configure-sso-for-aws-resources-with-okta-and-saml-sunbkvkqw","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/tutorial-how-to-configure-sso-for-aws-resources-with-okta-and-saml-sunbkvkqw"},"datePublished":"2026-08-23T12:19:07.044Z","dateModified":"2026-08-23T12:31:16.548Z","description":"A step-by-step tutorial walks through configuring single sign-on for AWS EC2 access using Okta as the identity provider, SAML for authentication, and Teleport...","image":"https://media.daily.dev/image/upload/s--0_ODbtD2--/f_auto/v1722860399/public/Placeholder%2008","thumbnailUrl":"https://media.daily.dev/image/upload/s--0_ODbtD2--/f_auto/v1722860399/public/Placeholder%2008","isAccessibleForFree":true,"articleSection":"Teleport","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Teleport","logo":"https://media.daily.dev/image/upload/s--Dw-Bbw6O--/c_limit,w_256/f_auto,q_auto/v1787487494/logos/teleport?_a=BAMAMicg0","url":"https://daily.dev/sources/teleport"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/tutorial-how-to-configure-sso-for-aws-resources-with-okta-and-saml-sunbkvkqw","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"aws,authentication,okta","timeRequired":"PT11M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Teleport","item":"https://daily.dev/sources/teleport"},{"@type":"ListItem","position":3,"name":"Tutorial: How to Configure SSO for AWS Resources with Okta and SAML"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/tutorial-how-to-configure-sso-for-aws-resources-with-okta-and-saml-sunbkvkqw#faq","mainEntity":[{"@type":"Question","name":"How do I map Okta groups to Teleport roles using a SAML connector?","acceptedAnswer":{"@type":"Answer","text":"Configure a Teleport SAML connector resource with an attributes_to_roles section that maps Okta group names (from the SAML group attribute statement) to Teleport role names, for example mapping the okta-admin group to the admin role, okta-dev to dev, and okta-dba to dba. The connector also requires the identity provider metadata XML downloaded from Okta's sign-on tab. daily.dev surfaces practical SSO and RBAC configuration guides for engineers wiring up identity providers."}},{"@type":"Question","name":"How do I restrict SSH access to specific EC2 instances based on Okta group membership using Teleport?","acceptedAnswer":{"@type":"Answer","text":"Create Teleport roles with node_labels matching a label assigned to specific EC2 instances, such as name=appserver or name=dbserver, then map each Okta group to the corresponding role via the SAML connector's attributes_to_roles setting. Users in the okta-developer group get a role scoped to appserver nodes, while okta-dba users get a role scoped to dbserver nodes, and access outside the matching label is denied. Teams enforcing least-privilege SSH access can find setup walkthroughs like this through daily.dev."}},{"@type":"Question","name":"How do I set up Teleport as an SSO-enabled bastion host for AWS EC2 instances?","acceptedAnswer":{"@type":"Answer","text":"Launch a Teleport proxy on a public-subnet EC2 instance, install Teleport Enterprise, and configure it with a cluster name and ACME email using teleport configure. Join private-subnet application and database servers to the cluster with generated node tokens, then switch the auth_service authentication type to saml in /etc/teleport.yaml (or apply a cluster_auth_preference resource on Teleport Cloud) so logins route through Okta. Engineers building bastion-host access architectures can track configuration walkthroughs on daily.dev."}}]}
```

