How to sell other state car

When I planned to move from Gurgaon to Pune I was in dilemma over whether to sell my Gurgaon registered car in Gurgaon or take it with me to Pune.

Since the new company I was joining was paying for relocation so car shifting cost was not an issue.

But, when you move between different states of India you get a grace period after which you have to register your car in the new state(Maharashtra) after taking NOC from the home state(Haryana). You also have to pay a hefty amount for road tax and registration charges in new state depending upon your car price and how old it is. Theoretically you can get the refund of the money you spent on road tax while registering the car in Haryana and use it to register the car in Maharashtra, but I couldn’t find any clear guideline on how to get this refund. Also, on internet I have read stories of many people trying to get refund from last many years but no luck.    You can read more about how to pay “one time tax” in Team BHP post about how to pay OTT on your vehicle of other state.

Since my car was only 3 years old and in good condition I didn’t want to sell it. But after knowing about the hassles of transferring the car I planned to sell it in Gurgaon itself.  When I approached few dealers all of them offered a paltry amount . I was not happy to sell my car at such low price so I finally decided to take it with me to Pune.

I used the car for few months in Pune and after that, I got an onsite opportunity. Now, I was again in dilemma as I have to get rid of my car and when I decided to sale it in Pune people were either not willing to buy an other state car or they offered very low price.  I had one option to ship the car back to Gurgaon where one of my relative can sell it.

Steps to Sell the Car

While searching for other options I came across Cars24. I visited their Hinjawadi office and told them about my car’s situation. They thoroughly inspected the car and found it to be in good condition. They told me that they will put my car for bidding and within 30 minutes let me know the offered price. They also told me that they will deduct about Rs 10500 for transferring my car back to Haryana and another Rs 3000 for service charges like registering my car on the new owner’s name etc. I thought lets check the price offered. After half an hour agent came back to me with the offered price. To my surprise the price offered was more than what was offered to me in Gurgaon when I tried to sell the car few months back.  Even after their standard deductions I found the deal to be good.

So I agreed to sell my car. They offered me two payment option. One is of instant payment where they will pay me the amount instantly after deducting Rs 20000 which will be paid to me after my car reaches Haryana. Also, they will deduct Rs 1000 for instant payment charges. Else, I can get the whole amount after few days. I opted for instant payment.

After providing them my car keys, and documents like insurance, registration etc. , my  personal info and photographs, the payment was done instantly in my account. The whole process took less then 2 hours. The remaining 20000 was also transferred to my account after around 15 days. I was highly impressed with the way it was handled by the Cars 24 team.

But the last test of transferring the ownership was still pending. They said it will take 2-3 months to get the ownership transferred. But, I was nervous because if the car is not transferred to new owner and the car got into an accident then police may come looking for me. I contacted Cars24 after 2 months to check why the car is not yet registered on new owner’s name. They told me to wait for some more time. After about 1 month I got a mail that my car is now registered on new owner’s name. I checked on parivahan website and found that my car is now registered to a different owner.

This whole experience of selling my out of state car with Cars24 was smooth and it’s the easiest way I could find to sell my car quickly in a different state at a decent price.

Solved: How to lock Terraform provider version

While working with terraform you would have noticed that every time you execute a terraform plan it will download the latest version of terraform available for that provider.

While this is good if you are testing as you get the latest features but, it can create trouble in production if a buggy version gets deployed. So, it is always recommended that you lock down the version of provider. In this post we will show you how to do that.

It’s really very simple to lock down the provider version. You just have to add a snippet like below in your main.tf file .

provider "aws" {

     region="us-east-1"
 
     version="<=2.6.0"

}

In the above example we have specified that version 2.6.0 or older can be used.

The version argument value may either be a single explicit version or a version constraint string. Constraint strings use the following syntax to specify a range of versions that are acceptable:

>= 2.4.0: version 2.4.0 or newer
<= 2.4.0: version 2.4.0 or older
~> 2.4.0: any non-beta version >= 2.4.0 and < 2.5.0, e.g. 2.4.X
~> 2.4: any non-beta version >= 2.4.0 and < 3.0.0, e.g. 2.X.Y
>= 2.0.0, <= 3.0.0: any version between 2.0.0 and 3.0.0 inclusive

Give it a try and let us know if you have any query or suggestion.

Solved: How to configure Terraform backend on AWS S3

Terraform is a very useful tool for IaaS. As you would have already known that it create a .tfstate file to save the status of infra. If you are doing testing you can save the .tfstate locally on your laptop. But, if you are working in prod environment with team then it’s best that you save the .tfstate remotely so that it’s secure and can be used by other team members.

Here we will show you two ways of configuring AWS S3 as backend to save the .tfstate file.

  1. First way of configuring .tfstate is that you define it in the main.tf file. You will just have to add a snippet like below in your main.tf file.
terraform {

      backend "s3" {

          bucket="cloudvedas-test123"

          key="cloudvedas-test-s3.tfstate"

          region="us-east-1"

      }

}

Here we have defined following things.

bucket = The S3 bucket in which the .tfstate should be saved

key = The name of the .tfstate file

region = The region in which S3 backend bucket exists.

2 Another way of specifying the S3 backend is that you define it when you initialize the terraform using the init command. This can be useful when you want to invoke the terraform from a jenkins file.

  • Here is an example that you can  execute in windows command prompt. This will do the same thing as we did in first example.
terraform init -no-color -reconfigure -force-copy -backend-config="region="us-east-1"" -backend-config="bucket="cloudvedas-test123"" -backend-config="key="cloudvedas-test1-win-s3.tfstate""
  • If you want to execute from a linux shell use below syntax.
 terraform init -no-color -reconfigure -force-copy \
-backend-config="region=us-east-1" \
-backend-config="bucket=cloudvedas-test123" \
-backend-config="key=cloudvedas-test-s3.tfstate"

Give it a try and let us know in comments section if you have any query or suggestion.

Solved RDS : Access denied; you need the SUPER privilege for this operation

Access denied; you need the SUPER privilege for this operation

You may get this error while trying to set values for RDS AURORA MySQL from the command line. It can be setting for long running queries or slow queries or many others.

If, you are sure you are trying to execute these changes using the master user then you can’t set these from command line.

For RDS Aurora you will have to make these changes through Parameter groups of DB and Cluster.

  •  To make the change, login to your AWS RDS console.
  • On the left side panel click on Parameter Groups and select the group associated with your RDS Cluster and node.
  • Make changes in the parameter groups.
  • Once you have saved the changes in parameter group it will start applying to your RDS cluster.

Some parameter changes will require reboot of your cluster while others can be done without reboot.  You will see pending-reboot in your cluster if it needs reboot to change the parameter.  For more details about parameter groups refer this AWS doc.