Traffic Manager deployment guideline for AWS/Azure
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Dinusha Senanayaka reported as follows:
Can we include official docs for Traffic Manager deployment guideline for AWS/Azure ? Since TM is different from other components, it's good to document things like; how to include TM into auto scaling groups (for HA only), how to address not having static IP like concerns on both AWS, Azure. At the moment, we don't have any reference docs in this regard.
Also do we have a plan to include this doc [1] to the latest APIM versions too ?
[1] https://docs.wso2.com/display/CLUSTER44x/Clustering+API+Manager+in+Amazon+Web+Services
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked Clustering API Manager in Amazon Web Services document and the current APIM documentation structure. Identify where AWS and Azure Traffic Manager guidance belongs, covering the requested high-availability, auto-scaling, and non-static-IP concerns. Done means the deployment guidance is documented for both platforms and its applicability to the latest APIM versions is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, azure
- Domain
- cloud, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100