The document discusses the concept of a service mesh, highlighting its features such as microservices communication, traffic management, security, and observability. It details technical aspects and benefits of a service network, including service discovery, security policies, and managed IP prefixes, while also noting drawbacks like the requirement for service clients to be in the VPC and lack of cross-region support. The content is presented by Aaron Walker, Technology Director at Base2Services.

1. The Service Mesh you actually want!!
@aaronwalker – Technology Director - @base2services

2. What is a
Service
Mes(s)h

3. Service Mes(s)h Features
Microservices
Communication
Traffic
Management
Service
Discovery
Security and
Authentication
Observability
and Monitoring
Resilience and
Failover

4. Deployment
complexity

5. Just don’t ask me to do it a scale

6. Technically not a Service Mesh….. It’s BETTER ;)

7. Service

8. Service Network
• Logical boundary
• Service Discovery
• Connectivity
• Access and observability
policies
• Exposed as link-local IP
address (169.254.171.0/24)

9. Security

10. Auth Polices
• IAM resource policies
associated at the Service
Network or Service Level

11. Security
Groups
Associate a security group to the
VPC assoications in Lattice
Enforce additional network-level
security for the service network
Provides managed IP prefix lists
for VPC lattice

12. Network
ACLs
Use VPC Network ACLs to
limit Service Network access
at the subnet level
Leverage VPC Lattice IP prefix
lists to restrict inbound and
outbound traffic

13. Signature Version 4 (SigV4) authenticated
requests

14. VPC Lattice
Benefits

15. Lets See it in
Action

16. Demo

17. What I don’t Like
Pricing Model Lattice service clients need
to be in the VPC (Road Map)
No Cross Region Service
Network Support (Yet!!!)

18. ©base2services Pty Ltd 2023. All rights reserved. The Cloud Services People
Aaron Walker, Technology Director
@base2Services
a.walker@base2services.com
@aaronwalker
linkedin.com/in/aaronpwalker
base2services.com