IT-Tools
Browser-based encoding, conversion and calculation tools for developers
Screenshot from verification · Click to enlarge
Application tests passed; AWS environment evidence comes from the referenced platform verification.
Quick Deploy
Use the recommended configuration, or customize it below.
Recommended configuration
- Version
- v2024.10.22-7ca5933
- AWS Regions
- us-east-1
- Instance
- t3.small
- Persistent data volume
- No application data disk
Customize configuration
Change the version, region or resources. Larger resources have not been verified separately.
Before creating resources
Check these prerequisites yourself. This website cannot inspect your AWS account and never asks for AWS access keys.
- Use an AWS account with permission to create CloudFormation, IAM, VPC, EC2, EBS and log resources in us-east-1. Budget for a running instance before continuing.
- Private access is the default. Install AWS CLI and the Session Manager plugin locally, sign in to the same account, and obtain permission to start SSM sessions. Port 8080 must be available.
- No domain is needed for private access. To serve users over HTTPS later, prepare a domain you control and initialize the administrator privately first.
Est. AWS cost · Shown in AWSNo application data disk is created, but the instance and root disk still incur charges. Check the region and public IPv4 costs; traffic, snapshots and logs may cost extra. This is not a quote or spending limit; custom configurations need a new estimate.
Save your work using the app's browser download or export feature and keep a local backup. The server does not persist application data; browser storage is not a backup.
Download or export your work before deleting the stack. Deletion terminates the host and deletes its default root disk; there is no application data disk to retain. Check for other billable resources, including any snapshots and logs.
Deployment steps and post-deploy actions
Create, connect, then initialize
These are instructions, not live deployment status. Stack creation, a working connection and administrator setup are three separate steps.
- Review stack "corenova-it-tools-v2024-10-22-7ca5933" in CloudFormation. Keep the private access parameters and pinned image, confirm the resource costs and IAM acknowledgement, then choose Create stack.
- Wait for CREATE_COMPLETE, usually about 10 minutes. If creation fails or rolls back, inspect Events before retrying.
- Open the stack's Outputs tab:
InstanceIdInstance ID — use it to open an SSM shell or locate the hostSSMPortForwardCommandPort-forward command — run locally and keep the session openResolvedLaunchUrlPrivate access URL — open after starting the SSM tunnel
- Copy SSMPortForwardCommand into your local terminal. Keep the session open, then visit http://localhost:8080 in your browser. The public IP is not the default app entry point.
The command forwards local port 8080 to instance port 80 over SSM; port 22 stays closed. Closing the terminal ends access. Use the same AWS account and region as the stack.
- Complete the application's first-run setup through this private connection, then sign out and sign back in. CREATE_COMPLETE alone does not mean an administrator has been created.
Optional: enable protected HTTPS
After private initialization, point your domain's DNS to the instance, allow the certificate challenge on port 80 and intended HTTPS clients on port 443, then open an SSM shell. Replace both example values before running:
sudo /opt/corenova/bin/enable-https.sh app.example.com [email protected] --confirm-initializedThis requests a trusted certificate and configures renewal. Failure must leave private access in place. HTTPS keeps an additional proxy login; retrieve it only through SSM from /opt/corenova/credentials/admin.txt. This is not an anonymous public site or webhook endpoint.
Access, HTTPS and troubleshootingIf a step fails
- Permissions, rollback or timeout: open CloudFormation Events and locate the first CREATE_FAILED resource. Do not create repeated stacks before inspecting the cause.
- Connection refused or access denied: check the SSM session, AWS account/region and local port 8080. For DNS, certificate or administrator errors, stay on the private connection; never work around them by opening public HTTP.
- Share the app/version, region, failed resource and a redacted error. Never share passwords, access keys, session tokens or unredacted logs. Clean failed stacks and inspect any remaining billable resources.
Good to know
- Tools run in the browser. This deployment has no server-side document storage; retain important inputs and results yourself.
Next steps
- Save your work using the app's browser download or export feature and keep a local backup. The server does not persist application data; browser storage is not a backup.
- To upgrade to a newer verified version: Version history
Download or export your work before deleting the stack. Deletion terminates the host and deletes its default root disk; there is no application data disk to retain. Check for other billable resources, including any snapshots and logs.
Versions
View full version history| Versions | Verified At | Verified | Status | AWS Tested |
|---|---|---|---|---|
| v2024.10.22-7ca5933 | Sep 24, 2026 | Verified | New Version | AWS · referenced |
Technical information
FAQ
How do I access IT-Tools after deployment?
After CREATE_COMPLETE, run SSMPortForwardCommand from the stack Outputs in your local terminal and keep it running. Open http://localhost:8080 to initialize the application privately. Public access stays blocked until you explicitly enable HTTPS.
How do I save my work, and are there still AWS charges?
There is no application data disk. Save your work using the app's browser download or export feature and keep a local backup. The server does not persist application data; browser storage is not a backup. The instance and root disk still incur charges. Deleting the stack terminates the host and deletes its default root disk, with no application data disk to retain. Check for other billable resources such as snapshots and logs.