Plans
Tools
Industries
Event types
Platform & partners
Industries
Agencies & Organizers Public Sector & Government Universities & Research Mid-Market & Customer Days Congresses & Conventions AssociationsEvent types
By event type SoonLearn
Knowledge Hub Guides Glossary Templates & Tools BlogPlatform & partners
Integrations Changelog API Documentation Soon Event Partner NetworkTry badge printing for free
Print professional event badges on site. Test our badge printer with no setup fee.
Learn moreStreavent connects to AWS IAM Identity Center, the single sign-on service for AWS, as a SAML 2.0 application. Your organizers and staff sign in with the AWS identity your team already administers, and event access follows the roles you assign.
The problem
Your team already signs in through AWS IAM Identity Center: one identity, one set of permissions, one place admins manage. Then the event platform arrives with another login outside that directory, one more password to issue and revoke by hand. IAM Identity Center keeps your team on the AWS identity it already uses.
Data flow
The most common flows, each as a live sync.
arrow_forward From AWS IAM Identity Center
Your central AWS identities sign in via SAML 2.0. IAM Identity Center confirms who they are, Streavent handles the login and maps them to the right roles.
arrow_back
These are the most common flows, not all of them. Speakers, sponsors, agenda and more sync too, and you can create a whole event straight from your tool.
How it works
Your admins add Streavent to AWS IAM Identity Center as a SAML 2.0 application, one entry in the applications list they already manage.
Access is granted by assigning Streavent to the users and groups you already manage in IAM Identity Center, with no separate list to keep.
IAM Identity Center confirms who signs in, Streavent sets what they reach. Each account maps to a role, so an organizer opens the admin while operations staff.
For your team
Grant event access by assigning a user or group in IAM Identity Center, remove it the same way. No standalone event account to track outside your AWS directory.
Your event team signs in through the AWS access portal it already opens for work. No extra event password to request, store or reset before the event.
Sign-in runs through IAM Identity Center, so your existing multi-factor and access rules apply to the event too. One directory, one set of controls, the event included.
Availability
We set up the integration together during onboarding, tailored to your systems.
Customer Stories
Meet the people behind the events: real teams who plan, run, and scale their events with Streavent.
“We ran the entire event in one system and went live in under a week.”
“Our event app basically builds itself, with content syncing automatically from our CRM.”
“We deliver our AI webinars as professional livestreams in top quality, all from one platform.”
“We build event landing pages without an agency, and it shows a clear ROI.”
“Check-in was effortless, even volunteers were ready in minutes.”
“Digital, hybrid, in-person: the platform gives us full flexibility, with a truly professional look.”
“We ran check-in entirely through the platform, and the analytics help us improve every event.”
“Our CRM connects directly via API, so we build complete events in just a few clicks.”
“The all-in-one solution we scale up or down for every event, seamlessly integrated with our CRM.”
Show us your IAM Identity Center setup and your next event, and we will show you how Streavent connects as a SAML application: your users, your groups, your team signing in through the AWS portal it already uses.
FAQ
Streavent is added to AWS IAM Identity Center, the single sign-on service for AWS, as a SAML 2.0 application. Your team then signs in to the event through the AWS access portal instead of a separate Streavent password. IAM Identity Center confirms the identity, and Streavent maps each account to a role that sets what it can access. Access is assigned and removed by user and group in the IAM Identity Center console.
For your team. AWS IAM Identity Center is built for workforce access, so this integration signs in your organizers, operations and staff, the people who already have AWS identities. It is not meant as a public login for event attendees. For attendee sign-in you would use a consumer-facing provider, while AWS handles the people who run the event.
IAM Identity Center. The single sign-on integration runs through AWS IAM Identity Center, formerly AWS SSO, which is the service AWS provides for signing people in to applications over SAML. It is the workforce identity layer, distinct from the IAM users and roles you use to control access to AWS resources themselves.
Yes. You assign the Streavent application to the users and groups in IAM Identity Center that should have access, and only they can sign in. Inside Streavent, each account maps to a role, so an organizer reaches the admin while operations staff see only what they run. Removing a user or group assignment in IAM Identity Center removes their event access with it.
About
Ecosystem