Bobcares

Allow Lambda execution role to access AWS S3 bucket

by | Sep 22, 2021

Wondering how to allow Lambda execution role to access AWS S3 bucket? We can help you.

Here, at Bobcares, we assist our customers with several AWS queries as part of our AWS Support Services.

Today, let us see how our Support Techs perform this task.

How to allow Lambda execution role to access AWS S3 bucket?

Today, let us see the steps followed by our Support Techs in order to perform this task.

To give your Lambda function access to an Amazon S3 bucket in the same AWS account, do the following:

1.Firstly, create an AWS Identity and Access Management (IAM) role for the Lambda function that also grants access to the S3 bucket.

2.Then, configure the IAM role as the Lambda function’s execution role.

3.Finally, verify that the S3 bucket policy doesn’t explicitly deny access to your Lambda function or its execution role.

 

 

Create an IAM role for the Lambda function that also grants access to the S3 bucket

1.Firstly, follow the steps in Creating an execution role in the IAM console.

2.From the list of IAM roles, choose the role that you just created.

3.In the Permissions tab, choose Add inline policy.

4.Then, choose the JSON tab.

5.Enter a resource-based IAM policy that grants access to your S3 bucket.

IAM policy example that grants access to a specific S3 bucket

Important: Replace “arn:aws:s3:::AWSDOC-EXAMPLE-BUCKET/*” with your S3 bucket’s Amazon Resource Name (ARN).

{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "ExampleStmt",
"Action": [
"s3:GetObject"
],
"Effect": "Allow",
"Resource": [
"arn:aws:s3:::AWSDOC-EXAMPLE-BUCKET/*"
]
}
]
}

6.Next, choose Review policy.

7.For Name, enter a name for your policy.

8.Finally, choose Create policy.

 

 

Configure the IAM role as the Lambda function’s execution role

1.Firstly, open the Lambda console.

2.Then, choose your Lambda function.

3.Under Execution role, for Existing role, select the IAM role that you created.

4.Finally, choose Save.

 

 

Verify that the S3 bucket policy doesn’t explicitly deny access to your Lambda function or its execution role

To review or edit your S3 bucket policy, follow the instructions in Adding a bucket policy using the Amazon S3 console.

Important: If your S3 bucket and the function’s IAM role are in different accounts, you must also explicitly grant the required permissions on the S3 bucket policy.

Example IAM S3 bucket policy that grants a Lambda execution role cross-account access to an S3 bucket

Important: Replace “arn:aws:s3:::AWSDOC-EXAMPLE-BUCKET/*” with your S3 bucket’s ARN.

Replace “arn:aws:iam::123456789012:role/ExampleLambdaRoleFor123456789012” with your Lambda execution role’s ARN.

{
"Id": "ExamplePolicy",
"Version": "2012-10-17",
"Statement": [
{
"Sid": "ExampleStmt",
"Action": [
"s3:GetObject"
],
"Effect": "Allow",
"Resource": [
"arn:aws:s3:::AWSDOC-EXAMPLE-BUCKET/*"
],
"Principal": {
"AWS": [
"arn:aws:iam::123456789012:role/ExampleLambdaRoleFor123456789012"
]
}
}
]
}

[Need help with AWS queries? We’d be happy to assist you]

Conclusion

In short, we saw how our Support Techs Allow Lambda execution role to access AWS S3 bucket.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF