# Receiving a Validation Failure. An error occurred during component validation error **URL:** \ **Category:** Matillion ETL\ **Created:** [September 2, 2021, 1:11pm UTC](https://matillioncommunity.discourse.group/t/receiving-a-validation-failure-an-error-occurred-during-component-validation-error/1426 "2021-09-02T13:11:16Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![persistentengteam](https://avatars.discourse-cdn.com/v4/letter/p/a88e4f/32.png) [@persistentengteam](https://matillioncommunity.discourse.group/u/persistentengteam)\ **Post date:** [September 2, 2021, 1:11pm UTC](https://matillioncommunity.discourse.group/t/receiving-a-validation-failure-an-error-occurred-during-component-validation-error/1426/1 "2021-09-02T13:11:16Z")
Hi,   We are trying to upgrade from our existing Matillion Server hosted on AWS ( 1.37.5 ) to the latest version available on AWS marketplace for Matillion ETL – Snowflake ( 1.53.8 )   A separate Ec2- instance with the latest version is launched, keeping the existing Matiilion server running.   We performed the Migrate activity of the Project using the Migrate steps mentioned in the link below:   [https://www.matillion.com/resources/blog/best-practices-update-matillion](https://www.matillion.com/resources/blog/best-practices-update-matillion)   On successful migration of the Project, we are now facing the issue to Run the jobs.   The AWS Credentials ( along with IAM policy is same as before and was working for earlier version )   Now we get the error as:   Validation Failure. An error occurred during component validation: A request was made to create an S3 client with missing credentials.   IAM Policy:   {    "Version": "2012-10-17",    "Statement": [        {            "Effect": "Allow",            "Action": [                "s3:ListBucket",                "s3:ListAllMyBuckets"            ],            "Resource": [                "\*"            ]        },        {            "Effect": "Allow",            "Action": [                "s3:ListBucket",                "s3:ListAllMyBuckets"            ],            "Resource": [                "arn:aws:s3::: bucketname"            ]        },        {            "Effect": "Allow",            "Action": [                "\*"            ],            "Resource": [                "arn:aws:s3:::bucketname/\*"            ]        }    ] }   Can you please provide any pointers on the same ---
**Author:** ![Bryan](https://avatars.discourse-cdn.com/v4/letter/b/db5fbb/32.png) [@Bryan](https://matillioncommunity.discourse.group/u/Bryan)\ **Post date:** [September 3, 2021, 4:42pm UTC](https://matillioncommunity.discourse.group/t/receiving-a-validation-failure-an-error-occurred-during-component-validation-error/1426/2 "2021-09-03T16:42:19Z")
Hi [@persistentengteam](https://matillioncommunity.discourse.group/u/persistentengteam)​ , Is the IAM Policy in your post part of the error output or is this your actual IAM policy? One thing to check is that the new Ec2 with the new version of Matillion that you spun up has the same VPC, Subnet, IAM Role, and Security Group as your existing older Ec2. I have made this mistake in the past and forgot to set the IAM Role or Security Group and had various issues after that. Since you are taking such a major jump from 1.37 to 1.5X, there definitely could be some different security requirements that would drive an update to the policy the IAM role being used by Matillion. The article you posted looks like it has good info and the method you are following is definitely the correct and safest approach. Since the article is a little older, I am wondering if other Matillion or AWS changes since the article came out have driven perhaps other required changes that are not reflected in the article. If you are sure the Ec2 configurations are identical to the previous one and you are still getting the error, I would open a support case on this. Matillion is likely the only one that is going to know the little infrastructure details that have changed between those versions. Post back and let us know what you end up finding. Thanks posting! ---
**Author:** ![persistentengteam](https://avatars.discourse-cdn.com/v4/letter/p/a88e4f/32.png) [@persistentengteam](https://matillioncommunity.discourse.group/u/persistentengteam)\ **Post date:** [September 7, 2021, 2:54pm UTC](https://matillioncommunity.discourse.group/t/receiving-a-validation-failure-an-error-occurred-during-component-validation-error/1426/3 "2021-09-07T14:54:07Z")
Hi Bryan,   Thanks a ton for your valuable inputs.   We tried with IAM Role and attached it to the Ec2 instance instead of IAM policy and that did the trick for us.   [IAM Roles & Permissions (AWS) (matillion.com)](https://documentation.matillion.com/docs/2954248)   Once this was done, we had to change the credentials manager to point to Instance credentials in the Matillion environment.   Would like to post the subsequent errors and its resolution as well in this post, so it may come handy for others.   **Error 1:** _"Environments:_ _Communications link failure_   _The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server."_   This error was observed due to the default TLS implementation used by the matilion JDBC drivers for mysql. In our case we dont have the mysql over TLS and since its internal within the VPC, we disabled the same.   _File Name: /usr/share/emerald/WEB-INF/classes/jdbc-providers.properties_   _{"name"   : "MySQL",_ _"driver"  : "com.mysql.jdbc.Driver",_ _"url"    : "jdbc:mysql://\/\",_ _"fetchSize" : "Integer.MIN\_VALUE",_ _"limit"   : "limit-inline",_ _"prepmeta" : false,_ _"allowUpload" : true,_ _"ssl": "false", \<\<\<\<\<\<\<\<-------- this line needs to be added_ _"defaultProperties" : {"connectTimeout": "20000"}_ _},_     **Error 2:** _Insufficient Permissions: Request had insufficient authentication scope_   To resolve the above issue, we had to reauthorize the Google Drive API in matillion again and also verify the call back url.     Cheers !!!