Readme & FAQ updates #1
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jamsajones
commented
Nov 26, 2018
README.md
Outdated
| * connect applications using API, | ||
| * Bootstrap Envoy and connect to XDS endpoint provided by App Mesh. | ||
| * Configure routes | ||
| * ~~[optional] configure dashboards using cloudwatch or grafana etc.~~ To be added later based on what Tony provides |
jamsajones
commented
Nov 26, 2018
README.md
Outdated
|
|
||
| * About Features/Use cases: (https://github.com/awslabs/aws-app-mesh/issues) | ||
| * About Usage clarifications/ Issues: (https://github.com/awslabs/aws-app-mesh/issues) | ||
| * Other discussion: [Get invited to #containers on AWS Developers [awsdevelopers.slack.com]](slack) |
jamsajones
commented
Nov 26, 2018
README.md
Outdated
|
|
||
| ### Questions? | ||
|
|
||
| * About Features/Use cases: (https://github.com/awslabs/aws-app-mesh/issues) |
There was a problem hiding this comment.
Line breaks please
jamsajones
commented
Nov 26, 2018
FAQ.md
Outdated
| Today, App Mesh is distributes a build of version 1.8.0 with an extensions for SigV4 that to ensure Envoy is authenticated propery with AWS authentication systems.We plan to upstream this change to Envoy soon.<br/> | ||
| 1. **How do your nodes authenticate so that a malicious service on my cluster doesn't connect itself to the mesh?** <br/> | ||
| We have added Sigv4 based Authentication for Envoy proxies that connect to the App Mesh service via standard AWS authentication. We plan to upstream this change to Envoy soon.<br/> | ||
| 1. **Can I use App Mesh with Windows containers?** (true?)<br/> |
jamsajones
commented
Nov 26, 2018
FAQ.md
Outdated
| 1. **Can I use App Mesh with Windows containers?** (true?)<br/> | ||
| No. Today, Envoy is not supported by Windows.<br/> | ||
| 1. **Are the service limits during the preview?**<br/> | ||
| You can create 1 mesh per account with 10 virtual nodes (10 versioned services or 10 deployments) and 10 virtual routers per mesh and 1 route in each virtual router. If you need more, let us know [link]<br/> |
There was a problem hiding this comment.
Make sure these are correct.
jamsajones
commented
Nov 26, 2018
FAQ.md
Outdated
| 1. **How do I get started with using App Mesh APIs?**<br/> | ||
| You can use App Mesh APIs to create the mesh and virtual nodes to represent your services. You then need to create virtual routers to configure traffic routes between these services. You then setup endpoints (statsd or Prometheus) to export metrics and logs from the mesh proxy and configure these endpoints in the Envoy bootstrap configuration - see detailed guide here (link). Then, you add App Mesh images into ECS task definition or EKS pod specification along with the environment variables required to virtual nodes. When these services get deployed, Envoys connect to App Mesh to get all the configuration required to handle all inbound and outbound task traffic according to the specified traffic routes.<br/> | ||
| 1. **Which version of Envoy do you use?**<br/> | ||
| Today, App Mesh is distributes a build of version 1.8.0 with an extensions for SigV4 that to ensure Envoy is authenticated propery with AWS authentication systems.We plan to upstream this change to Envoy soon.<br/> |
shubharao
reviewed
Nov 27, 2018
| 1. **What can I do with App Mesh when it is generally available?**<br/> | ||
| You can use App Mesh to send metrics, logs and traces to services of your choice. You can insert tracing to visualize a service map with details of API calls between services. You can configure traffic policies like health checks, retries and circuit breaks for the clients that connect to your services. You can also perform traffic routing on several other protocols, and based on HTTP headers and query parameters.<br/> | ||
| 1. **How do I get started with using App Mesh APIs?**<br/> | ||
| You can use App Mesh APIs to create the mesh and virtual nodes to represent your services. You then need to create virtual routers to configure traffic routes between these services. You then setup endpoints (statsd or Prometheus) to export metrics and logs from the mesh proxy and configure these endpoints in the Envoy bootstrap configuration - see detailed guide here (link). Then, you add App Mesh images into ECS task definition or EKS pod specification along with the environment variables required to virtual nodes. When these services get deployed, Envoys connect to App Mesh to get all the configuration required to handle all inbound and outbound task traffic according to the specified traffic routes.<br/> |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.