Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide mTLS walkthrough for east-west traffic #481

Open
saiteja313 opened this issue Mar 14, 2022 · 0 comments
Open

Provide mTLS walkthrough for east-west traffic #481

saiteja313 opened this issue Mar 14, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@saiteja313
Copy link

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,
gateway -> app1 -> app2

Note: mTLS enabled between gateway -> app1, app1 -> app2, gateway-> app1 -> app2

Platform
EKS, ECS, EC2, etc.

  • EKS, ECS

To Reproduce
Steps to reproduce the behavior:

  1. Go to aws-app-mesh-examples/[howto-mutual-tls-file-provided]
  2. Follow instructions and deploy setup.
  3. 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.
@saiteja313 saiteja313 added the bug Something isn't working label Mar 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant