Feedback¶

We value your input. Your feedback directly influences our development priorities and helps us improve the SG Provisioner for all customers.

How to Submit¶

  • AWS Marketplace: Use the “Contact Seller” button on our product listing

  • Email: support@axontechlabs.com

  • Account Representative: Contact your dedicated representative if applicable

Feature Requests¶

Have an idea for new functionality, or want to modify how an existing feature works? We want to hear it.

When submitting a feature request, please include:

Field

Description

Feature Name

Short descriptive name (e.g., “Security Groups Configuration”)

Description

What the feature should do

Use Case

How you would use it in your workflow

Business Impact

Why this matters to your organization

Priority

Critical / High / Nice-to-Have

Example:

Feature Name: ElastiCache Scenario

Description: Add a 3-tier-elasticache-redis scenario with port 6379 for Redis cache tier.

Use Case: Our application uses Redis for session caching between the app and database tiers.

Business Impact: Currently requires manual security group creation for the cache layer, adding deployment time and risk of misconfiguration.

Priority: High

Feature Voting¶

Already see a feature you want on our Roadmap? Vote for it! Reference the feature name or ID in your message and tell us your use case. Features with the most votes get prioritized for the next release.

Documentation Feedback¶

Help us make our documentation clearer and more useful.

When submitting documentation feedback, please include:

Field

Description

Document

Which document (e.g., USER_GUIDE, TROUBLESHOOTING)

Section

Which section is affected

Issue

What’s unclear, missing, or incorrect

Suggestion

How you’d improve it (optional)

Example:

Document: SCENARIOS

Section: Customizing with Overrides

Issue: The override example doesn’t show how to add an egress rule to a tier that has no egress defined (e.g., the db tier).

Suggestion: Add an example showing additional_egress on the db tier for outbound replication traffic.

What We’re Looking For¶

  • Sections that are confusing or hard to follow

  • Missing topics or use cases

  • Incorrect or outdated information

  • Examples that would help clarify a concept

  • Typos or formatting issues

What Happens Next¶

  1. Acknowledgment — We confirm receipt within 2 business days

  2. Review — Our team evaluates the request

  3. Prioritization — Feature requests are added to the Roadmap based on demand and feasibility

  4. Updates — Check Release Notes for implemented changes