Until recently, an online matrimony service provider Matrimony.com implemented
traditional disaster recovery through a secondary data center in Mumbai. The
business needed a technology infrastructure that could both keep up with demand
and help drive further growth. Purchasing duplicate storage, compute and
connectivity resources for the secondary location as its business scaled, translated
to additional cost burden — all of which might never actually be used. Given the
“always-on” nature of the business it was of paramount importance that the
application availability remains high. Keeping all the above factors into
consideration, the business decided to leverage the benefits of the public cloud by
migrating their core matrimony applications to AWS.
After thorough evaluation, Matrimony.com engaged Powerup and decided to use
AWS to build its business continuity and DR solution.
The approach – A pilot with DR
After thorough evaluation, it was decided to use AWS to build its business continuity
and DR solution with a ‘Pilot-light’ DR strategy was chosen and a minimal
environment of the entire DC setup to be run on AWS. All applications, database
and High Availability (HA) proxy instances were replicated to instances of minimal
size to optimize cost — a classic backup-and-restore scenario. AWS allows
maintenance of a pilot-light model by configuring and running only the most critical
core elements of a system. When required in case of a recovery, one can rapidly
provision a full-scale production environment around the critical core by upgrading
Powerup built a replica of all required servers and launched it using AWS
CloudFormation (CF) templates. For Matrimony.com, the legacy applications
required Powerup to use the same IP addresses in the new environment as well.
Powerup used Asymmetric routing mechanism to accommodate multiple IP
addresses and resolve connectivity issues on the secondary IP addresses. Load
balancers were required to have custom static private IPs to accommodate legacy
applications. However, Elastic Load balancer did not support this. To resolve this
issue, Powerup set up highly available HAProxy as an alternative to the internal load
balancer traffic with Keep-Alive. Keep-alive, when enabled, allows the load balancer
to reuse connections to the instance, which reduces the CPU utilization. In this case,
failover support was enabled between two HA Proxy servers by load balancing
between DC and DR for periodic application check. Code commit was used to update
the code to both DC and DR environments simultaneously.
Powerup complied with customer data centre security guidelines and the migration
was successful. Multiple VPCs were created for production, recovery and
management applications. All application servers were migrated using AWS Server
Migration Service(SMS) by replicating server VMs as cloud-hosted Amazon Machine
Images (AMIs) ready for deployment. Lambda was used to trigger the creation of
new AMIs. Database servers were deployed on EC2, replicated using native
replication techniques. The Configuration of the environment is automated by AWS
Compiled by Jeremiah Peter and Inputs from Amita PM
According to a recent survey by a US-based consultancy
firm, organizations spend anywhere between $12 to $20 from the time they
receive an invoice until they reconcile it. The statistic is a stark reminder
of how organizations, in pursuit of grand cost-cutting measures, often overlook
gaping loopholes in their RPA adoption policy- All or nothing!
This blog makes a compelling case to implement RPA incrementally in strategic processes to yield satisfactory results. Streamlining the invoice management process is, undoubtedly, a judicious leap in that direction.
Unstructured invoice dilemma
In a real-world scenario, data in invoices are not standardized and the quality of submission is often diverse and unpredictable. Under these circumstances, conventional data extraction tools lack the sophistication to parse necessary parameters and, often, present organizations the short end of the stick.
Consequently, most invoice processing solutions available today fail to reconcile the format variance within the invoices. The Powerup Invoice Processing Application is a simple Web Application (written in HTML and Python) that leverages cloud OCR (Optical Character Recognition) services, to extract text from myriad invoice formats. Powered by an intelligent algorithm, the solution uses the pattern-matching feature to extract data (e.g. Date MM-DD-YYYY) and breaks free from the limitations of traditional data extraction solutions.
A high-level peek into the solution
Subsequently, the string is converted to a human-readable format through a script, which uses a Python-based Regex library to identify desirable parameters in the invoice such as date, invoice number, order number, unit price, etc. The extracted parameters are passed back to the web application after successful validation. The entire process lasts not more than 10 seconds. The video below demonstrates how Powerup has successfully deployed the complete process:
Another noteworthy feature of the solution is that it seamlessly
integrates with popular ERP systems such as SAP, QuickBooks, Sage, Microsoft
Dynamics, etc. Given that ERP systems stash critical accounts payable documents
(purchase orders, invoices, shipping receipts), a versatile solution requires
integration with the organization’s ERP software to complete the automation
A brief look at the advantages offered by invoice processing automation can help you assess the value delivered by the solution.
The adoption of Powerup Invoice Processing Application helped organizations benefit from:
Deeply optimized invoice processing TAT resulting in quicker payment cycles
Up to 40% cost savings in procurement and invoice processing
Highly scalable solution that can process multiple invoices in a few minutes
Fewer errors and elimination of human data-entry errors
Free-form parameter pattern-matching
Easy integration with ERP software
Readily implementable solution; no change required from vendor’s end
While procurement teams in various organizations struggle to strike a
trade-off between low funds dispensation and high-cost savings, measures that
enable them to cut expenses and improve efficiencies in the invoicing process
are a welcome respite.
Tools such as the Powerup Invoice Processing Application can help organizations infuse automation and agility into its processes, as well as, knockdown process complexities into manageable parts. Moreover, the time and cost efficiencies achieved in these undertakings can be passed on to other functions that can significantly bolster the organization’s service offerings. To find out how your organization can be positively impacted, sign up for a free demo session here.
Written by Priyanka Sharma, DevOps Architect, Powerupcloud Technologies
Till now we have practised a lot on the OnDemand Nodes of K8s Cluster. This post demonstrates how to use Spot Instances as K8s worker nodes, and shows the areas of provisioning, automatic scaling, and handling interruptions (termination) of K8s worker nodes across your cluster. Spot Instances can save you up to 70–90% cost as compared to OnDemand.Though Spot EKSInstances are cheaper, you cannot run all your worker nodes as Spot. You must have some OnDemand Instances as a backup because Spot Instances can betray you anytime with the interruptions 😉
In this article, we are discussing how you can use Spot Instances on EKS Cluster as well as the cluster you own on EC2 Servers.
Refer to our public Github Repo which contains the files/templates we have used in the implementation. This blog is covering the below-mentioned points:
AWS EKS is a managed service that simplifies the management of Kubernetes servers. It provides a highly available and secure K8s control plane. There are two major components associated with your EKS Cluster:
EKS control plane which consists of control plane nodes that run the Kubernetes software, like etcd and the Kubernetes API server.
EKS worker nodes that are registered with the control plane.
With EKS, the need to manage the installation, scaling, or administration of master nodes is no longer required i.e. AWS will take care of the control plane and let you focus on your worker nodes and application.
EC2 Server to provision the EKS cluster using AWSCLI commands.
The latest version of AWSCLI Installed on your Server
IAM Permissions to create the EKS Cluster. Create an IAM Instance profile with the permissions attached and assign to the EC2 Server.
EKS Service Role
Kubectl installed on the server.
Provision K8s Cluster with EKS
Execute the below command to provision an EKS Cluster:
We have provisioned the EKS worker nodes using a cloud formation template provided by AWS. The template is available in our Github repo as well i.e. provision-eks-worker-nodes/amazon-eks-node group-with-spot.yaml. The template will provision three Autoscaling Groups:
2 ASG with Spot Instances with two different Instance types as given in the parameters
1 ASG with OnDemand Instance with Instance type as given in the parameter
Create a Cloudformation stack and provide the values in the parameters. For the AMI parameter, enter the ID from the below table:
| Region | AMI | |-------------------------| ---------------------- | | US East(Ohio)(us-east-2)| ami-0958a76db2d150238 |
Launch the stack and wait for the stack to be completed. Note down the Instance ARN from the Outputs.
Open the file “aws-cm-auth.yaml ” and replace the <ARN of instance role (not instance profile)> snippet with the NodeInstanceRole value that you recorded in the previous procedure, and save the file.
kubectl apply -f aws-auth-cm.yaml kubectl get nodes --watch
Wait for the nodes to be ready.
Kubernetes Operations with KOPS
Kops is an official Kubernetes project for managing production-grade Kubernetes clusters. It has commands for provisioning multi-node clusters, updating their settings including nodes and masters, and applying infrastructure changes to an existing cluster. Currently, Kops is actually the best tool for managing k8s cluster on AWS.
Note: You can use kops in the AWS regions which AWS EKS doesn't support.
Ec2 Server to provision the cluster using CLI commands.
Route53 domain, (for example, k8sdemo.powerupcloud.com) in the same account from where you are provisioning the cluster. Kops uses DNS for identifying the cluster. It adds the records for APIs in your Route53 Hosted Zone.
Note: For public hosted zone, you will have to add the NS records for the above domain to your actual DNS. For example, we have added an NS record for "k8sdemo.powerupcloud.com" to "powerupcloud.com". This will be used for the DNS resolution. For the private hosted zone, ensure to add the VPCs.
IAM Permissions to create the cluster resources and update DNS records in Route53. Create an IAM Instance profile with the permissions attached and assign to the EC2 Server.
S3 bucket for the state store.
Log into the EC2 server and execute the below command to install Kops on the Server:
Refer to our previous blog for the explanation of the arguments in the above command.
kops update cluster --yes
Once the above command is successful, we will have a private K8s Cluster ready with Master and Nodes in the private subnets.
Use the command “kops validate cluster CLUSTER_NAME” to validate the nodes in your k8s cluster.
Create Instance Groups for Spot and OnDemand Instances
Kops Instance Group helps in the grouping of similar instances which maps to an Autoscaling Group in AWS. We can use the “kops edit” command to edit the configuration of the nodes in the editor. The “kops update” command applies the changes to the existing nodes.
Once we have provisioned the cluster, we will have two Instance groups i.e. One for master and One for Nodes. Execute the below command to get available Instance Groups:
kops get ig
Edit nodes instance group to provision spot workers. Add the below Key Values. Set the max price property to your bid. For example, “0.10” represents a spot-price bid of $0.10 (10 cents) per hour.
it may take a long time to become available (or may never become available),
and maybe reclaimed by AWS at any time.
Amazon EC2 can interrupt your Spot Instance when the Spot price exceeds your maximum price, when the demand for Spot Instances rises, or when the supply of Spot Instances decreases. Whenever you are opting for Spot, you should always be prepared for the interruptions.
So, we are creating one interrupt handler on the clusters which will run as a daemonset on the OnSpot Worker Nodes. The workflow of the Spot Interrupt Handler can be summarized as:
Identify that a Spot Instance is being reclaimed.
Use the 2-minute notification window to gracefully prepare the node for termination.
Taint the node and cordon it off to prevent new pods from being placed.
Drain connections on the running pods.
To maintain desired capacity, replace the pods on remaining nodes
Create the Spot Interrupt Handler DaemonSet on both the k8s clusters using the below command:
If the number of pods increases with the application load, the cluster autoscaler will provision more worker nodes in the Autoscaling Group. If the Spot Instance is not available, it will opt for OnDemand Instances.
Initial Settings in the ASG:
Scale up the number of pods for one deployment, for example, product page. Execute:
Written by Tejaswee Das, Software Engineer, Powerupcloud Technologies
Technological advancement in the area of Artificial Intelligence & Machine Learning has not only helped systems to become more intelligent but has also made them more vocational. You can just speak to the phone & add items to your shopping list or just instruct your laptop to read your email. In this fast-growing era of voice-enabled automation, Amazon’s Alexa enabled devices are changing the way people go through their daily routines. In fact, it has introduced a new term in the dictionary, Intelligent Virtual Assistant (IVA).
Technopedia defines Intelligent Virtual Assistant as an engineered entity residing in software that interfaces with humans in a human way. This technology incorporates elements of interactive voice response and other modern artificial intelligence projects to deliver full-fledged “virtual identities” that converse with users.”
Some of the most commonly used IVAs are Google Assistant, Amazon Alexa, Apple Siri, Microsoft Cortana, with Samsung Bixby joining the already brimming list lately. Although IVAs seem to be technically charged, they bring enormous automation & value. Not only do they make jobs for humans easier, but they also optimize processes and reduce inefficiencies. These systems are so seamless, that just a simple voice command is required to get tasks completed.
The future of personalized customer experience is inevitably tied to “Intelligent Assistance”. –Dan Miller, Founder, Opus Research
So let’s bring our focus to Alexa, Amazon’s IVA. Alexa is Amazon’s cloud-based voice service, which can interface with multiple devices on Amazon. Alexa gives you the power to create applications, which have the capability to interact in natural language, making your systems more intuitive to interact with technology. Its capabilities mimic those of other IVAs such as Google Assistant, Apple Siri, Microsoft Cortana, and Samsung Bixby.
The Alexa Voice Service (AVS) is Amazon’s intelligent voice recognition and natural language understanding service that allows you to voice-enable any connected device that has a microphone and a speaker.
Powerupcloud has worked on multiple use-cases, where they have developed Alexa voice automation. One of the most successful & adopted use cases being one of the largest General Insurance providers.
This blog series aims at giving a high-level overview of building your first Alexa Skills. It has been divided into two parts, first, covering the required configurations for setting up the Alexa skills, while the second focuses on the approach for training the model and programming.
Before we dive in to start building our first skill, let’s have a look at some Alexa terminologies.
Alexa Skill — It is a robust set of actions or tasks that are accomplished by Alexa. It provides a set of built-in skills (such as playing music), and developers can use the Alexa Skills Kit to give Alexa new skills. A skill includes both the code (in the form of a cloud-based service) and the configuration provided on the developer console.
Alexa Skills Kit — A collection of APIs, tools, and documentation that will help us work with Alexa.
Utterances — The words, phrases or sentences the user says to Alexa to convey a meaning.
Intents — A representation of the action that fulfils the user’s spoken request.
Click on Create Skill, and then select Custom Model to create your Custom Skill.
Please select your locale carefully. Alexa currently caters to English (AU), English (CA), English (IN), English (UK), German (DE), Japanese (JP), Spanish (ES), Spanish (MX), French (FR), and Italian (IT). We will use English (IN) while developing the current skill.
Select ‘Start from Scratch’
Alexa Developer Console
Enter an Invocation Name for your skill. Invocation name should be unique because it identifies Skills. Invocation Name is what you say Alexa to invoke or activate your skill.
There are certain requirements that your Invocation name must strictly adhere to.
Invocation name should be two or more words and can contain only lowercase alphabetic characters, spaces between words, possessive apostrophes (for example, “sam’s science trivia”), or periods used in abbreviations (for example, “a. b. c.”). Other characters like numbers must be spelt out. For example, “twenty-one”.
Invocation names cannot contain any of the Alexa skill launch phrases such as “launch”, “ask”, “tell”, “load”, “begin”, and “enable”. Wake words including “Alexa”, “Amazon”, “Echo”, “Computer”, or the words “skill” or “app” are not allowed. Learn more about invocation names for custom skills.
Changes to your skill’s invocation name will not take effect until you have built your skill’s interaction model. In order to successfully build, your skill’s interaction model must contain an intent with at least one sample utterance. Learn more about creating interaction models for custom skills.
Endpoint — The Endpoint will receive POST requests when a user interacts with your Alexa Skill. So this is basically the backend for your Alexa Skill. You can host your skill’s service endpoint either using AWS Lambda ARN, which is recommended, or a simple HTTPS endpoint. Advantages of using an AWS Lambda ARN are :
We are using Lambda in the N.Virginia (us-east-1) region.
Once we are in a supported region, we can go ahead to create a new function. There are three different options for creating your function. You can create a function from scratch or you can also use available Blueprints and Serverless Application Repositories.
C# / .NET
We will discuss programming Alexa with different languages in the next part of this series.
Go back to the Endpoint section in Alexa Developer Console, and add the ARN we had copied from Lambda in AWS Lambda ARN Default Region.
ARN format — arn:aws:lambda:us-east-1:XXXXX:function:function_name
In, part 2, we will discuss the training our model — adding Intents & Utterances, finding walkarounds for some interesting issues we faced, making workflows using dialog state, understanding the Alexa Request & Response JSON, and finally our programming approach in Python.
Written by Gopinath P, Project Manager at Powerupcloud Technologies.
When you are one of the top Health Insurance service providers in a country such as India, with a population of over 1.3 billion people, you should know that your customer care team is going to be working around the clock to resolve customer queries & issues.
Powerup engaged with Future Generali India Insurance Company Ltd., where currently the Customer care team is the single point of contact for handling servicing queries and complaints from the customers to facilitate an end to end process in a Life insurance policy. Ensuring a high level of customer satisfaction remains core to such businesses. An approx. of 30,000 queries on a monthly basis have been received on this dedicated call centre. These calls are currently catered to by manual agents, which might lead to a higher load on agents & marred by manual inefficiencies.
A separate team looks into the selling of the policies, increasing business volumes & driving revenue. Being a completely manual process, this creates a bottleneck into no of sales and a host of times, creates incorrect recommendations on policies to be sold. Resulting in a high amount of customer churn & lost business.
When we at Powerup were approached with the above problem statement, we first analyzed the call recordings from their call centre. Most of the queries could be classified under a limited set of service queries. In addition, while enquiring about a policy, the user is generally looking out for a set of recommendations on policy, premium & payment terms, which would suit the user requirements. Powerup solution specialists designed a solution that could not only support customer queries but also recommends the most relevant policies to the customers, helping them sign up & close deals much faster. Powerup’s Botzer was a perfect fit for the Insurance giant, with readymade modules & integration available.
Botzer is an AI-Powered enterprise chatbot, which allows customized business solutions to be deployed & hosted in the customer’s account, integrating with multiple Enterprise Systems. Powered by intelligent Natural Language Processing & Machine Learning algorithms, it is capable of understanding even the most complex customer queries. On Botzer, customer support was automated for this Life Insurance giant across channels, including their website, customer mobile apps & Social channels, such as Facebook Messenger as well.
The customer response time was reduced to within 3 minutes to complex queries, as compared to 24 hours earlier. The resolution rate also increased by more than 50%, while the agent load reduced by 60% for inbound calls.
The bot not only improved the post-sales support but also gave targeted recommendations to the customers, basis their preferences & lifestyle, allowing them to buy policies within minutes.
The bot also performs sentiment analysis on the queries coming in from the users, responding to the users’ basis the identified sentiment. A positive sentiment sends the customer a happy & a blushing reply, while negative sentiment is replied to with an empathetic tone to the customer. If the bot is not able to respond to a query, the query is passed to a live agent to engage with the customer.
The bot also automates workflows to accelerate & close sales. While recommendations are given to the customers’ basis their preferences, the bot then connects users to a live agent to close the deal.
With Botzer, we not only automated their customer support, consolidating the customer support experience across channels but also provided a comprehensive set of analytics. These custom-built dashboards allowed the business to view user profiles, user preferences, journeys & how they have transacted with the system. Marketing & Customer servicing teams gain customer buying behaviour & preferences insights, allowing them to design high performing campaigns, resulting in higher ROI.
Written by Rishabh Sood, Associate Director — Advanced Services Group at Powerupcoud Technologies
Chatbots as a concept are not new. In fact, under the domain of Artificial Intelligence, the origin of chatbots is quite early, tracing back to as early as 1955. Alan Turing published “Complete Machinery & Intelligence”, starting an unending debate, “Can machines think?”, laying the foundation of the Turing test & eventually leading to ELIZA in 1966, the 1st ever chatbot. It failed to pass the Turing test but did start a horde of chatbots to follow, each one more mature than its predecessor.
The next few years saw a host of chatbots, from PARRY to ALICE, but hardly any saw the light of the day. The actual war on the chatbots started with the larger players coming into the picture. Apple led with Siri in 2010, followed closely by Google Now, Amazon’s Alexa & Microsoft’s Cortana. These chatbots made life a tad easier for the users, as they could now speak to Siri to book an Uber or tell Alexa to switch off the lights (another way to make our lives more cushioned). While these chatbots did create a huge value to users in terms of making their daily chores automated (& speak to a companion, for the lonely ones), business still was a long way from extracting benefits from the automated conversational channel.
Fast track to the world of today & we see chatbots part of every business. Every company has budgets allocated for automating at least 1 process on chatbots. Oracle says that 80% of the businesses are already using or have plans to start using chatbots for major business functions by 2020. Chatbots have been implemented across companies & functions, primarily with a focus on automating support systems (internal as well as external). Most of the bots available in the market today respond to user queries basis keywords/phrases match. The more advanced bots today use the concept of intent matching & entities extraction to respond to more complex user queries. A handful of bots today even interact with the enterprise systems to provide real-time data to the users. Most of the commercially successful bots in the market today are text-based interactions.
Most of the bots in action today augment tasks, which are repeatable/predictable in nature. Such tasks, if not automated, would require considerable human effort, if not automated. These chatbots are powered by Natural Language Processing engines to identify user’s intent (verb or action), which then is passed to the bot’s brain to execute a series of steps, to generate a response for the identified intent. A handful of bots also contain Natural Language Generation engines to generate conversations, with a human touch to it. Sadly, 99.9% of today’s implementations will still fail more than 60 years old Turing test.
It’s true that the conversational Engines, as chatbots are often referred to as, have been there for a couple of years, but the usefulness of their existence will now be brought to test. The last couple of months have seen a considerable improvement in how the conversational engines add value to the businesses, that someone refers to as the chatbot 2.0 wave.
At Powerup, we continuously spend efforts on researching & making our products & offerings better, to suit the increasing market demands. So, what can one expect from this new wave of bots? For starters, the whole world is moving towards voice-based interactions, the text remains only for the traditional few. So, the bots need to be equipped with the smart & intelligent voice to text engines, which can understand different accents & word pronunciations, in addition, to be able to extract the relevant text from the noise in the user’s query, to deliver actual value. The likes of Google & Microsoft have spent billions of dollars on voice to text engines, but the above still remains a tough nut to crack, keeping the accuracy of the voice-based system limited in the business world.
With the voice-based devices, such as Amazon Echo & Google Home, bring convenience & accessibility together. Being available for cheap & in mass (the smart speakers’ market is slated to grow to $11.79 billion by 2023), makes it a regular household item, rather than a luxury. The bots will have to start interacting with users via such devices, not limited to the traditional channels of Web & Social. This will not only require the traditional voice to text layers to be built in, but specific skills (such as Alexa Voice Services for Alexa compatible devices) to be written. A key factor here is how the user experience on a platform that is purely voice-based (although Echo Spot also has a small screen attached to it), where visual rendering is almost nil, is seamless & equally engaging for the users, as is on traditional channels.
In 2017, 45% of the people globally were reported to have preferred speaking to a chatbot, rather than a human agent. 2 years down the line, chatbots are all set to become mainstream, rather than alternative sources of communication. But this poses a greater challenge for the companies into the business. The bots will now have to start delivering business value, in terms of ROI, conversions, conversation drops & metrics that matter to the business. HnM uses a bot that quizzes the users to understand their references & then show clothing recommendations basis the above-identified preferences. This significantly increased their conversion on customer queries.
The new age of chatbots has already started moving in a more conversational direction, rather than the rule-based response generation, which the earlier bots were capable of. This means the bots now understand human speech better & are able to sustain conversations with humans for longer periods. This has been possible due to the movement of the traditional intent & entity models on NLP to advancement on Neural networks & Convolutional networks, building word clouds & deriving relations on these to understand user queries.
Traditionally, Retail has remained the biggest adopter of the chatbots. According to Statista.com, Retail remained to occupy more than 50% of the chunk in the chatbots market till 2016. With the advancement being brought into the world of chatbots at lightning speed, other sectors are picking up the pace. Healthcare & Telecommunications, followed by Banking are joining the race of deriving business outputs via chatbots, reporting 27%, 25% & 20% acceptance in the area in 2018. The new wave of bots is slated to narrow this gap across sectors in terms of adoption further. A study released by Deloitte this year highlights the increase of internal chatbot use-cases growing more than customer-facing functions, reporting IT use-cases to be the highest.
Chatbots have always remained as a way of conversing with users. Businesses have always focused on how the experience on a chatbot can be improved for the end customer, while technology has focused on how chatbots can be made more intelligent. The bots, being one of the highest growing channels of communication with the customers, generates a host of data in the form of conversational logs. Business can derive a host of insights from this data, as the adoption of bots among customers increases over the next couple of years. A challenge that most businesses will face would be the regulatory authorities, such as GDPR in the EU. How business work around these, would be interesting to see.
Mobile apps remain the widest adopted means of usage & communication in the 21 st century, but the customers are tired of installing multiple apps on their phones. An average user installs more than 50 apps on a smartphone, the trend is only going to change. With multiple players consolidating the usage of apps, users will limit the no of apps that get the coveted memory on their mobile phones. This will give an opportunity to the businesses to push chatbots as a communication channel, by integrating bots not only on their websites (mobile compatible of course) but other mobile adaptable channels, such as Google Assistant.
According to Harvard Business Review researchers, a 5-minute delay in responding to a customer query increases the chances of losing the customer by 100%, while a 10-minute delay increases this chance 4 times. This basic premise of customer service is taken care of by automated conversational engines, chatbots.
Chatbots have a bright future, especially with the technological advancement, availability & adaptability increasing. How the new age bots add value to the business, remains to be seen and monitored.
It would be great to hear what you think the future of automated user engagement would be and their degree of influence.
In our last blog post, we have explained how to tag the EC2, RDS, and S3 in bulk numbers by aws-tagger.
Since this tool won’t support bulk volume/snapshots tagging so we have configured another tool for completing the tagging.
In this blog post, we are going to explain about Volume and Snapshots tagging by this amazing tool called Graffiti Monkey.
The Graffiti Monkey goes around tagging things. By looking at the tags an EC2 instance has, it copies those tags to the EBS Volumes that are attached to it, and then copies those tags to the EBS Snapshots.
Install graffiti monkey on the EC2 machine.
Create an IAM user with the access key and secret key to provide permission to graffiti monkey.
Create the config file(YAML) with all tags details needs to copy to the EC2.
Let’s start the hands-on:
Login to your EC2 Linux machine:
i)First, install pip on the machine.
yum install python-pip
ii)Second, install the graffiti-monkey
pip install graffiti_monkey
Create the config file (YAML) in the AWS-EC2 machine. (Below is the sample)
We are going to use the same YAML file here for all the accounts as the tags are common for all of them.
If you add the new tags in EC2, then you need to add the new tags to this YAML file also as per the requirement.
Written by Mudita Misra, Cloud Engineer, Powerupcloud Technologies
Why and How the aws-tagger is useful for us?
Use case: “What if we have bulk AWS untagged resources and we need to get the billing based on tags in one or two daytime then how will we do it??”
In this article, we are going to explain how we can do the AWS resource tagging for bulk in number resources in just a few minutes.
There was a requirement for one of our customers where we were having multiple accounts with bulk resources-EC2, RDS and S3. These resources have to be tagged with 8–9 Business tags for billing/segregation purposes. So we have explored and implemented aws-tagger to make the tagging someway easier.
Tagging AWS resources is hard because each resource type has a different API which is slightly different. The AWS bulk tagging tool eliminates these differences so that you can simply specify the resource ID and the tags and it takes care of the rest.
Note: Any tags that already exist on the resource will not be removed, but the values will be updated if the tag key already exists. Tags are case sensitive.
Install aws-tagger on the local/EC2-machine
Create IAM user with access key and secret key to provide permission to aws-tagger to apply the tags on the resources.
Create the CSV file with all tags details.
Let’s start the hands-on:
We can do it from our local machine and also we can have one AWS EC2 Linux/Windows machine from customer private network(if concerned).
i)First, install pip on the machine.
yum install python-pip
ii)Second, install the aws-tagger
pip install aws-tagger
We will create access key and secret key for this IAM to provide permission to our EC2/local to tag the resources into the account.
We need to attach the below permission to the IAM user from different respective accounts.
I hope this is helpful, please comment below in case of any implementation issues.
Any EC2 volumes that are attached to the instance will be automatically tagged but in case of bulk resources, we won’t recommend aws tagger. We will be coming up with a new method for tagging volumes and snapshots in our next part.
Keep following the blog post for the upcoming part on how to tag Volumes and Snapshots attached to EC2 instances.
For more resources, you can follow below Github link:
Written by Priyanka Sharma, DevOps Architect, Powerupcloud Technologies
Recently, we have got an opportunity to develop and deploy an application on a Kubernetes cluster running on AWS Cloud. We have developed a sample PHP application which will parse the CSV file and upload the content of the file into a MySQL RDS Instance. The application UI also supports some other functionalities like updating/deleting a particular row from the database, store and view processed files via AWS S3 bucket and view all the records of MySQL database. The Kubernetes Cluster is being provisioned using KOPS tool. This article discusses the following points:
“kubectl get svc” will give the provisioned Loadbalancer Endpoint. Create a DNS Record for the Endpoint, for example, app.demo.powerupcloud.com.
Basic Authentication is enabled for the main page.
The browse field will accept the CSV file only.
After uploading, the data will be imported into the database by clicking the “Import” button.
The processed files can be viewed by clicking on the “View Files” button.
“View Data” button will list the records from the database in tabular format.
The data record can be edited inline and updated into the database by clicking the “Archive” button.
A particular row can be deleted from the database by clicking the “Delete” button.
The application is running on two different nodes in different subnets and is being deployed under a Classic LoadBalancer.
The Gitlab Instance and Runner are running as pods on the Kubernetes Cluster.
The application code is available in the Gitlab Repository along with Dockerfile and .gitlab-ci.yml
The pipeline is implemented in Gitlab Console using .gitlab-ci.yml file.
Whenever a commit is pushed to the Repository, the pipeline is triggered which will execute the following steps in a pipeline:
Build: Build a docker image from the Dockerfile and push to AWS ECR Repo.
Deploy: Updates the docker image for the already running application pod on Kubernetes Cluster.
Application in Action
Hit the Gitlab Service:
Sign in with the credentials.
Create a new Project and push the code. It will look like:
The Pipelines will look like:
View Processed Files:
“Archive” will update the database.
Delete will delete the row from the database.
Note:We don’t recommend the application code to use in any scenario. It’s just for our testing purpose. It is not written using the best practices. This article showcases the provisioning of Kubernetes cluster using KOPS with best practices and the deployment of any PHP application on the cluster using Gitlab pipelines.
Hope you found it useful. Keep following our blogs for the more interesting articles on Kubernetes. Do visit the previous parts of this series.