{"id":17758,"date":"2017-05-19T17:55:18","date_gmt":"2017-05-19T13:55:18","guid":{"rendered":"https:\/\/www.msp360.com\/resources\/?p=17758"},"modified":"2021-01-26T14:43:27","modified_gmt":"2021-01-26T10:43:27","slug":"assuming-an-iam-role","status":"publish","type":"post","link":"https:\/\/www.msp360.com\/resources\/blog\/assuming-an-iam-role\/","title":{"rendered":"Assuming an IAM Role via CloudBerry Explorer"},"content":{"rendered":"

CloudBerry Explorer enables users to authenticate to Amazon S3 using regular credentials. Taking things further, we've implemented support for IAM roles in the latest iteration of CloudBerry Explorer \u2014 release 5.0.5. In this article, we talk about how this mechanism functions and how to assume a role in Explorer.
\n<\/p>\n

Introduction<\/h2>\n

Amazon has an extremely versatile authentication mechanism. That is to say, apart from regular cloud credentials, Amazon allows to create the so-called IAM roles.\u00a0An IAM role<\/em> is similar to a user, in that it is an AWS identity with permission policies that determine what the identity can and cannot do in AWS. Here how a created role looks in the AWS Console:<\/p>\n

\"Create<\/p>\n

Now let's see how you can assume the aforementioned role in CloudBerry Explorer. But before we begin, ensure that your CloudBerry Explorer is already authenticated to S3 using credentials of the user that's been assigned to the role you're trying to assume.<\/p>\n

\n
\n
FREE WHITEPAPER<\/div>\n
Mastering AWS IAM for Amazon S3<\/div>\n
Learn how to effectively manage the security of your Amazon S3 account to protect your and your clients' data<\/div>\n\"CTA\"<\/a><\/span><\/span>\n<\/div>\n
\"WP<\/div>\n<\/div>\n

Role assumption<\/h2>\n

Assuming a role in CloudBerry Explorer is no more complicated than adding a few strings in the settings<\/em> file. You can navigate to the file by going to\u00a0C:\\Users\\yourUserName\\AppData\\Local\\CloudBerryLab\\CloudBerry Explorer for Amazon S3\u00a0<\/em>in Windows Explorer. Alternatively, you can locate the file via CloudBerry Explorer itself. Under Tools, click Diagnostic.<\/p>\n

\"Role<\/p>\n

Click Open in Folder<\/strong>.<\/p>\n

\"Diagnostic<\/p>\n

Open the settings.list<\/em> file and add the following attributes to your S3 account (placed between <Settings> and <\/Settings>):<\/p>\n

    \n
  • \n
    <AssumedRoleARN>arn:aws:iam::YourAccountNumber:role\/RoleName<\/AssumedRoleARN><\/div>\n<\/li>\n
  • \n
    \u00a0<AssumedRoleExternalId>ExternalId<\/AssumedRoleExternalId><\/div>\n<\/li>\n<\/ul>\n

    \"Open<\/p>\n

    The values for the attributes can be fetched from the AWS Console.<\/p>\n

    \"AWS<\/p>\n

    Having done so, save the file and relaunch CloudBerry Explorer. Upon launching your role should be automatically assumed, and the permissions will be set in accordance with your role.<\/p>\n","protected":false},"excerpt":{"rendered":"

    CloudBerry Explorer enables users to authenticate to Amazon S3 using regular credentials. Taking things further, we’ve implemented support for IAM roles in the latest iteration of CloudBerry Explorer \u2014 release 5.0.5. In this article, we talk about how this mechanism functions and how to assume a role in Explorer.<\/p>\n","protected":false},"author":69,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[877,898,882],"tags":[],"class_list":["post-17758","post","type-post","status-publish","format-standard","hentry","category-blog-articles","category-msp360-explorer","category-msp360-news"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/posts\/17758","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/users\/69"}],"replies":[{"embeddable":true,"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/comments?post=17758"}],"version-history":[{"count":0,"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/posts\/17758\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/media?parent=17758"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/categories?post=17758"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/tags?post=17758"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}