Clear steps. Agreed scope. You stay in control.
We agree what you need, review your AWS setup and explain the priorities. Any implementation is planned and approved separately.
Four clear steps
Scope
Agree your goals, the systems involved and the work to be delivered.
Assess
Review your AWS setup to identify risks, waste and areas for improvement.
Explain
Walk through the findings, business impact and recommended priorities.
Improve
Where requested, implement approved changes, check the results and hand over documentation.
You stay in control
Agreed access
We agree which accounts and systems we need to review, and the permissions required.
Read-only reviews
Assessments inspect your setup. They do not make changes to your resources.
Approved changes
Implementation is planned separately and needs your written approval before work starts.
Access removed after delivery
Your team controls access. Removing the agreed access is part of the handover.
Technical details for IT teams and MSPs
Access and permissions
Use client-managed IAM roles or IAM Identity Center access with permissions limited to the agreed scope. Reviews use read-only permissions; any additional access for implementation is agreed separately. Cross-account role trust, including an external ID where appropriate, is agreed with your team.
Credentials and account control
We do not request root account credentials. Do not send passwords, access keys or private keys through email or contact forms. Your team provisions access and removes role trust, assignments and any other agreed access at handover.
Evidence and findings
Findings reference relevant resource IDs, configurations and metrics where appropriate. We explain the business impact, technical rationale, priorities and trade-offs so your team can review the recommendations.
Change planning and validation
Before implementation, agree the scope, dependencies, change window, approval owner and rollback approach. Changes use Infrastructure as Code or controlled configuration updates as appropriate. Results are checked against the agreed validation steps and documented for handover.
What you receive
Deliverables are agreed at the start, with the detail your business and technical team need.
Findings report
A clear business summary backed by technical findings and supporting evidence.
Prioritised action plan
Recommended actions, why they matter and what should be addressed first.
Walkthrough and handover
A discussion of the findings and next steps, plus change records and operational notes where implementation is included.
Working alongside your IT team or MSP
Bring in AWS expertise alongside the people who already support your business. We agree how we will work together before access or delivery begins.
Clear responsibilities
Agree what Kervora will deliver and what stays with your team or provider.
Agreed communication
Confirm customer contacts, progress updates, escalation routes and who approves changes.
Practical handover
Share findings and any agreed change records, with clear next steps for ongoing support.
Common questions
What access will you need?
For assessments, we agree read-only access to the relevant AWS accounts and systems. We do not request root account credentials. Any additional permissions needed for implementation are agreed separately.
Will you change anything during the review?
No. Assessments inspect your setup without changing resource configurations. Any implementation is planned separately, with your written approval before changes begin.
What happens after the review?
We walk you through the findings, supporting evidence and prioritised action plan. Your team or MSP can take the recommendations forward, or discuss implementation support with Kervora.
Can you work with our existing IT team or MSP?
Yes. We agree responsibilities, customer communication and approvals before work starts, then coordinate access, findings and handover with the people managing the environment.
What should I share when I get in touch?
A short description of your AWS setup, the problem you want to solve and any deadlines is enough to start. Do not send passwords, access keys, private keys or sensitive customer data. Technical access is arranged separately.
Ready to discuss the next step?
Tell us what you need help with. We’ll agree a practical way forward with you.