Logistics and ride dispatch
Dispatch Pro
A real-time logistics platform: Flutter apps, Spring Boot services and a Kafka event pipeline on AWS.
Freelance · AWS
I am one senior engineer who runs real products on AWS. I used it on Dispatch Pro with Docker and Kubernetes pipelines, on Raheeb for media handling beside an Azure back end, and on Loade Driver, a delivery driver app. I join your team remotely, by the project or month by month.
A security group, a route or the wrong address, found in that order.
The step-by-step fixThe wrong login user for the image, or the wrong key.
The step-by-step fixThe authorization message has to be decoded to see which policy blocked it.
The step-by-step fixA profile without a default region, which matters in scripts.
The step-by-step fixA signing detail, often the region or a trailing character in a key.
The step-by-step fixThe kubeconfig points at an endpoint that is stopped or unreachable.
The step-by-step fixThe ones shown on the projects: storage for media, cloud hosting, and Docker and Kubernetes pipelines.
I can tidy what runs and what is unused. I do not promise savings figures.
Yes. I start with a written inventory and a backup before I change anything.
No. Raheeb used Azure for the service layer, and my own servers run on plain Ubuntu.
I have written fix pages on SSH timeouts and on the wrong default user, so I start with the network rule, the key and the user name before looking anywhere else.
Proof
Logistics and ride dispatch
A real-time logistics platform: Flutter apps, Spring Boot services and a Kafka event pipeline on AWS.
Consumer app
A consumer app shipped to both stores from one Flutter codebase on a .NET and Azure back end.
Logistics · Driver app
The driver side of a delivery platform: live jobs, routing and earnings, past 5K Google Play downloads.
From the fix library
Error parsing parameter '--steps': Expected: '=', received: 'EOF' for input:aws emr --steps fails: Error parsing parameter, Expected '=', received 'EOF'A client error (400) occurred when calling the HeadObject operation: Bad Requestaws s3 cp fails with 'An error occurred (400) when calling the HeadObject operation'Error: Running AWS SAM projects locally requires Docker. Have you got it installed?sam local fails: Running AWS SAM projects locally requires DockerUnable to load AWS credentials from the /AwsCredentials.properties file on the classpathThe AWS SDK for Java cannot find credentials, and AwsCredentials.properties does nothingsoftware.amazon.awssdk.core.exception.SdkClientException: Unable to load credentials from any of the providers in the chain AwsCredentialsProviderChainThe Java SDK finds no AWS credentials on an EC2 instance or in a container on itMissing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1The AWS SDK in Node.js cannot find any credentialsMonth by month
Next step
A discovery call within 48 hours, and a kickoff typically inside two weeks.