You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Important note on security disclosures: If you think you’ve found a potential security issue, please do not post it in the Issues. Instead, please follow the instructions here or email AWS security directly.
Describe the bug
A clear and concise description of what the bug is.
mTLS walkthrough's provide examples for Gateway to application mtls configuration. However, this is not end to end. Considering a application with multiple backends in same mesh, we need an mtls example to shows following,
Validate that mTLS is configured from gateway -> blue (color) but no mTLS between blue -> green
Additional context
Add any other context about the problem here.
We can add a note about this stating, to enable support for east-west traffic, you can add backend listener pointing on client app pointing to server app.
The text was updated successfully, but these errors were encountered:
Important note on security disclosures: If you think you’ve found a potential security issue, please do not post it in the Issues. Instead, please follow the instructions here or email AWS security directly.
Describe the bug
A clear and concise description of what the bug is.
Note: mTLS enabled between
gateway -> app1
,app1 -> app2
,gateway-> app1 -> app2
Platform
EKS, ECS, EC2, etc.
To Reproduce
Steps to reproduce the behavior:
gateway -> blue (color)
but no mTLS betweenblue -> green
Additional context
Add any other context about the problem here.
to enable support for east-west traffic, you can add backend listener pointing on client app pointing to server app
.The text was updated successfully, but these errors were encountered: