Тёмный

AWS re:Invent 2022 - SaaS microservices deep dive: Simplifying multi-tenant development (SAS405) 

AWS Events
Подписаться 116 тыс.
Просмотров 22 тыс.
50% 1

At some point in building a SaaS environment, the attention shifts to how multi-tenancy will influence how the builders on your team design and code their multi-tenant microservices. Multi-tenancy requires you to introduce new mechanisms to address authorization, data access, tenant isolation, metrics, billing, logging, and a host of other considerations. In this session, dive deep into multi-tenant microservices, looking at the various patterns and strategies that can be used to bring a multi-tenant microservice to life without imposing added complexity on your SaaS builders.
Learn more about AWS re:Invent at go.aws/3ikK4dD.
Subscribe:
More AWS videos bit.ly/2O3zS75
More AWS events videos bit.ly/316g9t4
ABOUT AWS
Amazon Web Services (AWS) hosts events, both online and in-person, bringing the cloud computing community together to connect, collaborate, and learn from AWS experts.
AWS is the world’s most comprehensive and broadly adopted cloud platform, offering over 200 fully featured services from data centers globally. Millions of customers-including the fastest-growing startups, largest enterprises, and leading government agencies-are using AWS to lower costs, become more agile, and innovate faster.
#reInvent2022 #AWSreInvent2022 #AWSEvents

Наука

Опубликовано:

 

16 июл 2024

Поделиться:

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист
Посмотреть позже
Комментарии : 11   
@mshannoncarver
@mshannoncarver Год назад
Thank you Michael! Great, thorough, and useful info in this presentation!
@Mci146
@Mci146 Год назад
Thank you Michael for sharing your knowledge, great presentation!
@mccelik
@mccelik Год назад
Greatest presentation on this topic!
@srinivaskalyan4313
@srinivaskalyan4313 Год назад
Thank you very much. Useful details.
@awssupport
@awssupport Год назад
Happy to see you enjoyed the session, Srinivas! 📺🙌 ^RM
@user-lk7rh9vs2r
@user-lk7rh9vs2r Год назад
35:50 It is mentioned here that we can assign no permissions to the default identity, to prevent accidentally using a default identity that has more permissions. However, earlier it was mentioned that the session policy can only make permissions more restrictive than the default identity (to prevent privilege escalation)?
@awssupport
@awssupport Год назад
Hi Riva. 👋 I found this document that may help: go.aws/42RHP2N. This is also an excellent question to post to our community of experts over on re:Post: go.aws/aws-repost. 📬 ^SA
@ewenreynolds
@ewenreynolds 4 месяца назад
Yes. This confuses me too. could @awssupport clarify the apparent contradiction here please.
@PatrickWerz
@PatrickWerz Год назад
ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-NpThwz0z_D0.html Why has the STS direct call a higher latency than cognito doing this on behalf of the user? In the end both ways need to wait for sts, right?
@mattimarttinen
@mattimarttinen Год назад
Thank you, a wonderful presentation. I especially enjoyed the part about the data isolation and the clear examples. One thing bothers me though. This talk simultaneously promotes Cognito and talks about augmenting the access token with custom claims. As far as I know, this is not possible to do in Cognito.
@awssupport
@awssupport Год назад
I'm glad you enjoyed the presentation, Matti. I have also gone ahead and sent your detailed feedback forward for review. 🧐 ^NR
Далее
다리에 힘이 풀려버린 슈슈 (NG Ver.)
00:11
Просмотров 2,5 млн
Multi-tenant architecture in 20 minutes
18:56
Просмотров 111 тыс.
Tenant Isolation & Data Partitioning
1:04:39
Просмотров 6 тыс.
Я УКРАЛ ТЕЛЕФОН В МИЛАНЕ
9:18
Просмотров 115 тыс.
iPhone 15 Pro в реальной жизни
24:07
Просмотров 334 тыс.
Acer Predator Тараканьи Бега!
1:00
Просмотров 476 тыс.