What’s New on May 9: Deploy Microservices, SPAs, and Cloud Resources on AWS — Fast

What’s New on May 9: Deploy Microservices, SPAs, and Cloud Resources on AWS — Fast

Anand Muthukrishnan

May 9, 2025

Deploy fast:

Your dev team have to ship fast, ridiculously fast on their environments, no matter what they ship. That’s one of our top goals here at LocalOps.

Last week, we released Github integration that enables teams to just deploy on their AWS account in minutes by pushing commits to their Git repo. No more signing into servers, running deployment scripts or migration scripts etc., Or no more setting up or optimising CI/CD configuration yourself. We automate all of that for you by fitting into your regular git-push workflow on Github. Learn more.

We just pushed a major change to our build setup today.

From now, the build infrastructure that pulls your code & builds the docker image out of your Dockerfile, is dedicated, isolated & different from the infrastructure used by your neighbouring accounts within LocalOps. This means that when you push your code, it gets pulled and built right away. Builds no longer have to wait for their turn. If you are in hurry to deploy that hot fix in production, this change is a life saver.

Deploy Microservices:

In any app environment LocalOps spins for you, you can launch and run any number of services, deploy any number of times by just pushing to your Github branch. What if your services want to talk to each other? Say you have micro-services architecture in your application and each component depends on other services for fulfiling specific business logic.

Make way for Service Alias 🎉

Each service that exposes a port, gets a new unique `service alias`. It is a string that you can see in Service screen and which you can use a alias for the specific service’s internal DNS host name.

You can add this `service alias` as `secret` in the dependent service. At run time, LocalOps replaces that string with the actual internal DNS host name. Your code can simply consume the secret as environment variable and connect to the service.

Learn more in our docs here - https://docs.localops.co/micro-services

Deploy Single page apps (SPA):

We’ve made new guides available for you to deploy React, Angular, Ember and VueJS apps seamlessly with same automation, on your AWS account.

Checkout https://docs.localops.co/single-page-apps/react.

Extend with additional cloud resources using your Pulumi/Terraform/OpenTofu scripts:

You may want to create RDS database, S3 bucket, SNS topic or a SQS queue to fulfill business logic. We wanted to make this process easier so that you can write Terraform or Pulumi scripts to create these resources for each of your environments. So we have exposed VPC and subent IDs that we provision and manage in your AWS account. You can use these IDs as variables in your IaC stack (Terraform/Pulumi/OpenTofu) to create any cloud resource you need in AWS.

Checkout our documentation to learn more - https://docs.localops.co/extend-terraform-pulumi

Access cloud resources using roles and not keys:

To access those cloud resources like S3, we have made it easier for you to do it without passing around static IAM keys as secrets. Static IAM keys are un-safe and may get stolen. LocalOps makes a IAM role available at run time for all your services to access cloud resources using AWS recommended role based access method. Your code can can simply use AWS SDK to make calls without requiring keys.

Checkout our documentation to learn more - https://docs.localops.co/extend-terraform-pulumi