Updates and improvements of year 2025
ops.json
in your Git repo to declare cloud resources for services to use. Including AWS
S3 buckets, SNS topics, SQS queues, RDS instances, ElasticCache clusters etc.,LocalOps will provision these resources in your cloud account with production grade security, when the corresponding
service is deployed.service alias
. It is a string that you can see in Service screen
and which you can use as an alias for the specific service’s internal DNS host name.You can add this service alias
as a 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<your-app-env-domain>
. You can access metrics and logs of all nodes, pods and containers running within the app
environment’s kubernetes cluster.If you are running your environment in AWS, you will also see a pre-configured CloudWatch data source in the
corresponding Grafana dashboard. You can access logs and metrics that are stored in CloudWatch.This is super useful if your application is using managed AWS services that are sending metrics/logs to CloudWatch.Go to “Monitor” tab in your environment to access the Grafana dashboard. Within Grafana, see Connections > Data sources
to see the Cloudwatch data source. Click on “Explore” next to it to see CloudWatch logs and metrics.Let us know what you think. Email us at help@localops.co.ServiceAccount
in your Helm deployment yaml spec as per our documentation.After the environment is provisioned, you can manually add/remove relevant IAM policies to the app specific IAM role we
provisioned earlier.