SQS & CloudWatch

Amazon SQS (Simple Queue Service) is a managed queue component from AWS cloud service.  Amazon CloudWatch enables you to collect, access, and correlate this data on a single platform from across all your AWS resources, applications, and services.  User can view and analyze your queues' metrics from the Amazon SQS console, the CloudWatch console, using the AWS CLI, or using the CloudWatch API.

The combination of SQS and CloudWatch is powerful in terms of stability, scalability, resilency, performance, etc.  It is achievable by setting CloudWatch alarms for Amazon SQS metrics.

CloudWatch metrics for your Amazon SQS queues are automatically collected and pushed to CloudWatch at one-minute intervals. These metrics are gathered on all queues that meet the CloudWatch guidelines for being active. CloudWatch considers a queue to be active for up to six hours if it contains any messages or if any action accesses it.

CORS

 

Access-Control-Allow-Origin specifies either a single origin, which tells browsers to allow that origin to access the resource; or else — for requests without credentials — the " * " wildcard, to tell browsers to allow any origin to access the resource.

Cross-Origin Resource Sharing (CORS) is a mechanism that uses additional HTTP headers to tell browsers to give a web application running at one origin, access to selected resources from a different origin. A web application executes a cross-origin HTTP request when it requests a resource that has a different origin (domain, protocol, or port) from its own.

In AWS, S3 bucket is configured to allow cross-origin requests by adding CORS configuration to the bucket.

AWS XRay

“What gets measured, gets managed “ — Peter Drucker

AWS X-Ray is a service that collects data about requests of any underlying application. It also provides tools to view, filter, and gain insights into that data to identify issues and opportunities for optimization.

This week, my blog post is hosted in medium site at https://medium.com/trimble-maps-engineering-blog/x-ray-latency-measure-f73961b08959

Happy Blogging !

Everest survey succeeds with Trimble

 

Trimble is pioneer in GPS technology with market presence since mid 1980s.  As the industry leader, it generates a revenue of close to 4 billion USD per annum.

Trimble R10 GNSS System collects more accurate data faster and easier – no matter what the job or the environment.  As a proud testimony, Nepal government has completed fieldwork for measuring Everest’s height using Trimble's equipment.

Proud to be Trimble-ian !

Ref: https://www.gpsworld.com/everest-survey-succeeds-with-trimble-gnss/

AWS PO Preview

 

As part of the procure-to-pay process, AWS customers leverage Purchase Orders (“POs”) to procure AWS services and approve invoices for payment.  The current limitation is not able to track their PO information to ensure that valid POs are used for their invoices.  It can be maually achieved by connecting AWS Support service team.

Last week, AWS introduced Purchase order (preview) feature in AWS console app.  It allows the customers to configure multiple POs, define how they are mapped to invoices, and access invoices generated against their POs.  Now, the customer can manage PO status, track PO balance and expiration, and configure contacts to receive email notifications for PO expiration and balance depletion.

With the new PO Management capabilities, customers will be able to exercise greater control over their PO information, and leverage their procure-to-pay process more effectively with AWS.

Shift Left Security

In the current Covid situations, every activities (school, college, business, etc.) are online.  Risk is around web security breaches; it's too costly to resolve.

Shift Left Security is recent buzz word in the industry.  Objective is to build the pro-active security check from the development phase to the production move.

Bit-bucket blog ref: https://bitbucket.org/blog/shift-left-with-code-insights-for-bitbucket-cloud

Launch Template

AWS Launch Template is more advanced than Launch Configuration. 

Based on my work experience, it has been listed as below:

1. Version Management

It is possible to create one or more numbered launch template versions. Each version can have different launch parameters, as depicted in the above diagram.  But Launch configuration needs manual maintenance. 

2. Leverage the latest features

Launch template can leverage the latest features of Amazon EC2, such as T2 Unlimited instances.

3. EC2 Launch Model

Launch configuration creates EC3 instances using the given Auto Scaling group, where as launch templates enable you to store launch parameters.

4.Subnet collection

In terms of subnet configuration script, launch template specifies exactly one subnet, rather than a list used in launch configuration.