Explore information related to iam


Not authorized to perform iam:PassRole error - Tips to fix it ?

This article covers ways to resolve AWS AccessDeniedException – I Can't Assume a Role error which happens when you try to create an Auto Scaling group without the PassRole permission. In fact, To pass a role (and its permissions) to an AWS service, a user must have permissions to pass the role to the service. This helps administrators ensure that only approved users can configure a service with a role that grants permissions. To allow a user to pass a role to an AWS service, you must grant the PassRole permission to the user's IAM user, role, or group.


Cause of AWS AccessDeniedException – I Can't Assume a Role error:

There are two possible causes for this AccessDenied error: the user in your development account doesn't have permission to call sts:AssumeRole, or the trust relationship in the production account is not configured correctly.


To create a role for Amazon RDS enhanced monitoring:

  • Sign in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam/.
  • Choose Roles, and then choose Create role.
  • Choose the AWS Service role type, and then choose the Amazon RDS Role for Enhanced Monitoring service. Then choose Next: Permissions.
  • Choose the AmazonRDSEnhancedMonitoringRole, permissions policy.
  • Choose Next: Tags.
  • (Optional) Add metadata to the user by attaching tags as key-value pairs. For more information about using tags in IAM.
  • Choose Next: Review.
  • For Role name, type a role name that helps you identify the purpose of this role. Role names must be unique within your AWS account. They are not distinguished by case. For example, you cannot create roles named both PRODROLE and prodrole. Because various entities might reference the role, you cannot edit the name of the role after it has been created.
  • (Optional) For Role description, type a description for the new role.
  • Review the role and then choose Create role.


Google Cloud Error Code 4033 - Fix it Now ?

This article covers methods to resolve Google Cloud Error Code 4033. Virtual Private Cloud (VPC) firewall rules apply to a given project and network. If you want to apply firewall rules to multiple VPC networks in an organization. 

VPC firewall rules let you allow or deny connections to or from your virtual machine (VM) instances based on a configuration that you specify. Enabled VPC firewall rules are always enforced, protecting your instances regardless of their configuration and operating system, even if they have not started up.


ec2 key permission denied – "Authentication failed, permission denied"

This article covers method to fix the error, ec2 key permission denied. 

"Permission denied (publickey)" and "Authentication failed, permission denied" errors occur if:

  • You're trying to connect using the wrong user name for your AMI.
  • The permissions are incorrect on the instance.
  • The incorrect SSH public key (.pub) file is in the authorized_keys file.


To fix this error, simply:

  • Verify that you're using the correct user name for your AMI.
  • Also Verify that the instance's permissions are correct and that the correct SSH public key is in the authorized_keys file.


Handle Errors in Serverless Applications with AWS

This article will guide you how to handle #errors in Serverless Applications with AWS Step Functions. Combining AWS Step Functions with AWS Lambda makes it simple to orchestrate #AWS #Lambda functions for serverless applications.

To help you deal with errors in Lambda applications, Lambda integrates with services like #Amazon CloudWatch and AWS X-Ray. You can use a combination of logs, metrics, alarms, and tracing to quickly detect and identify issues in your function code, API, or other resources that support your application.

Lambda functions can fail in three cases:

i. An unhandled exception is raised — whether if we received an invalid input, an external API failed, or just a programming bug occurred.

ii. Timeout — Lambda running longer than the configured timeout duration is violently closed with a ‘Task timed out after … seconds’ message. The default value is 6 seconds, and the maximal value is 5 minutes.

iii. Out of memory — In this case, the lambda usually terminates with ‘Process exited before completing request’. The ‘Memory Size’ is equal to ‘Max Memory Used’.



For Linux Tutorials

We create Linux HowTos and Tutorials for Sys Admins. Visit us on LinuxAPT.com

Also for Tech related tips, Visit forum.outsourcepath.com or General Technical tips on www.outsourcepath.com