id
stringlengths
16
145
text
stringlengths
1
179k
title
stringclasses
1 value
aws_legacy_credentials_and_S3/howtosetupanawslambd_60_0.txt
Publish-AWSPowerShellLambda -ScriptPath .\FUNCTION-RoleManager-1\FUNCTION-RoleManager-1.ps1 -Name FUNCTION-RoleManager-1 -IAMRoleArn $role.Arn
aws_legacy_credentials_and_S3/pstoolsec2sghtml_16_0.txt
PS > New-EC2SecurityGroup -GroupName myPSSecurityGroup -GroupDescription "EC2-Classic from PowerShell"
aws_legacy_credentials_and_S3/AWSToolsLambdaComple_0_0.txt
Skip To Content
aws_legacy_credentials_and_S3/pstoolsec2sghtml_5_0.txt
If you need to connect to your instance, you must configure the security group to allow SSH traffic (Linux) or RDP traffic (Windows).
aws_legacy_credentials_and_S3/howtosetupanawslambd_70_0.txt
At this point, the Lambda PowerShell function should be ready to go. Let's test it out!
aws_legacy_credentials_and_S3/pstoolsec2sghtml_38_0.txt
PS > Get-EC2SecurityGroup -GroupIds sg-5d293231
aws_legacy_credentials_and_S3/howtosetupanawslambd_57_0.txt
#### Uploading the Lambda Function to AWS
aws_legacy_credentials_and_S3/powershelllambdacode_92_0.txt
Publish-LMFunction -Description "My C# Lambda Function" ` -FunctionName MyFunction ` -ZipFilename .\MyFunctionBinaries.zip ` -Handler "AssemblyName::Namespace.ClassName::MethodName" ` -Role "arn:aws:iam::123456789012:role/LambdaFullExecRole" ` -Runtime dotnetcore1.0 ` -Environment_Variable @{ "envvar1"="value";"envvar2...
aws_legacy_credentials_and_S3/howtosetupanawslambd_27_0.txt
### Preparing the S3 Bucket
aws_legacy_credentials_and_S3/pstoolsec2sghtml_52_0.txt
Did this page help you? - No
aws_legacy_credentials_and_S3/pstoolsec2sghtml_0_0.txt
[ ](/pdfs/powershell/latest/userguide/aws-pst-ug.pdf#pstools-ec2-sg "Open PDF")
aws_legacy_credentials_and_S3/pstoolsec2sghtml_51_0.txt
If you've got a moment, please tell us what we did right so we can do more of it.
aws_legacy_credentials_and_S3/AWSToolsLambdaComple_18_0.txt
foreach ( $paramName in $param2CmdletsMap . Keys ) { $cmdletNames = $param2CmdletsMap [ $paramName ]
aws_legacy_credentials_and_S3/AWSToolsLambdaComple_33_0.txt
$LM_SelectCompleters = { param ( $commandName , $parameterName , $wordToComplete , $commandAst , $fakeBoundParameter )
aws_legacy_credentials_and_S3/howtosetupanawslambd_56_0.txt
#Requires -Modules @{ModuleName='AWS.Tools.Common';ModuleVersion='4.0.2.0'}, @{ModuleName='AWS.Tools.S3';ModuleVersion='4.0.2.0'}, @{ModuleName='AWS.Tools.IdentityManagement';ModuleVersion='4.0.2.0'}# Select all the objects within the central configuration bucket$bucket = "awslambdapowershelldemo1"$objects = Get-S3Obj...
aws_legacy_credentials_and_S3/howtosetupanawslambd_40_0.txt
The updated policy is assigned to the role as an inline policy using the ` Write-IAMRolePolicy ` cmdlet. The AWS Lambda Basic Execution Role is an AWS managed policy assigned to the role using the ` Register-IAMRolePolicy ` .
aws_legacy_credentials_and_S3/AWSToolsLambdaComple_49_0.txt
[ Gallery Status ](https://aka.ms/psgallery-status/)
aws_legacy_credentials_and_S3/howtosetupanawslambd_21_0.txt
> _AWS Lambda supports custom run times, which support newer versions of .NET > Core other than the long-term service branches._
aws_legacy_credentials_and_S3/powershelllambdacode_17_0.txt
** Tools for PowerShell **
aws_legacy_credentials_and_S3/howtosetupanawslambd_19_0.txt
For a walkthrough on setting up the above prerequisites, check out the article _[ How to Set Up a PowerShell Development Environment for AWS Lambda on Windows ](https://sweetcode.io/how-set-up-powershell-development-environment- aws-lambda-window/) _ .
aws_legacy_credentials_and_S3/powershelllambdacode_87_0.txt
New-LMAlias -FunctionName "MylambdaFunction123" -RoutingConfig_AdditionalVersionWeight @{Name="1";Value="0.6} -Description "Alias for version 4" -FunctionVersion 4 -Name "PowershellAlias"
aws_legacy_credentials_and_S3/AWSToolsLambdaComple_25_0.txt
# Amazon.Lambda.FunctionVersion "Get-LMFunctionList/FunctionVersion" { $v = "ALL" break }
aws_legacy_credentials_and_S3/powershelllambdacode_151_0.txt
* For API details, see [ UpdateFunctionConfiguration ](https://docs.aws.amazon.com/powershell/latest/reference) in _AWS Tools for PowerShell Cmdlet Reference_ .
aws_legacy_credentials_and_S3/howtosetupanawslambd_58_0.txt
Now that you have the working directory created and the PowerShell code to send to AWS, it's time to publish the Lambda function to AWS. To do that, run the ` Publish-AWSPowerShellLambda ` cmdlet. This cmdlet wraps up the code in the PowerShell script into a zip file and publishes it to the AWS Lambda service.
aws_legacy_credentials_and_S3/pstoolsec2sghtml_14_0.txt
We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see **Migrate from EC2-Classic to a VPC** in the [ Amazon EC2 User Guide for Linux Instances ](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/vpc-migrate.html) or the [ Amazon EC2 User Gui...
aws_legacy_credentials_and_S3/howtosetupanawslambd_30_0.txt
> _S3 bucket names need to be globally unique and lowercase. If this example > name is taken, use any other name you'd like._
aws_legacy_credentials_and_S3/powershelllambdacode_155_0.txt
Write-LMFunctionConcurrency -FunctionName "MylambdaFunction123" -ReservedConcurrentExecution 100
aws_legacy_credentials_and_S3/powershelllambdacode_104_0.txt
** Tools for PowerShell **
aws_legacy_credentials_and_S3/pstoolsec2sghtml_11_0.txt
If you specify ` 0.0.0.0/0 ` , you are enabling traffic from any IP addresses in the world. For the SSH and RDP protocols, you might consider this acceptable for a short time in a test environment, but it's unsafe for production environments. In production, be sure to authorize access only from the appropriate individu...
aws_legacy_credentials_and_S3/powershelllambdacode_141_0.txt
** Tools for PowerShell **
aws_legacy_credentials_and_S3/howtosetupanawslambd_83_0.txt
[ Powershell ](/tag/powershell?source=tags_bottom_blogs) [ aws lambda ](/tag/aws-lambda?source=tags_bottom_blogs) [ AWS ](/tag/aws?source=tags_bottom_blogs)
aws_legacy_credentials_and_S3/pstoolsec2sghtml_28_0.txt
IpProtocol : tcp FromPort : 22 ToPort : 22 UserIdGroupPairs : {} IpRanges : {203.0.113.25/32}
aws_legacy_credentials_and_S3/powershelllambdacode_103_0.txt
The following code example shows how to use ` Remove-LMAlias ` .
aws_legacy_credentials_and_S3/howtosetupanawslambd_26_0.txt
> _If you'd rather skip straight to the code without the explanation, you can > download it[ here ](https://github.com/Snozzberries/AWS-Role-Manager) . _
aws_legacy_credentials_and_S3/powershelllambdacode_61_0.txt
C:\>Get-LMProvisionedConcurrencyConfig -FunctionName "MylambdaFunction123" -Qualifier "NewAlias1"
aws_legacy_credentials_and_S3/powershelllambdacode_170_0.txt
Did this page help you? - No
aws_legacy_credentials_and_S3/powershelllambdacode_106_0.txt
Remove-LMAlias -FunctionName "MylambdaFunction123" -Name "NewAlias"
aws_legacy_credentials_and_S3/powershelllambdacode_9_0.txt
* Actions
aws_legacy_credentials_and_S3/pstoolsec2sghtml_21_0.txt
To configure the security group to allow inbound traffic on TCP port 22 (SSH) and TCP port 3389, use the ` Grant-EC2SecurityGroupIngress ` cmdlet. For example, the following example script shows how you could enable SSH traffic from a single IP address, ` 203.0.113.25/32 ` .
aws_legacy_credentials_and_S3/powershelllambdacode_98_0.txt
The following code example shows how to use ` Publish-LMVersion ` .
aws_legacy_credentials_and_S3/pstoolsec2sghtml_27_0.txt
PS > (Get-EC2SecurityGroup -GroupNames myPSSecurityGroup).IpPermissions
aws_legacy_credentials_and_S3/AWSToolsLambdaComple_17_0.txt
Register-ArgumentCompleter @args } } else { if ( -not $global:options ) { $global:options = @{ CustomArgumentCompleters = @{ } ; NativeArgumentCompleters = @{ } } }
aws_legacy_credentials_and_S3/pstoolsec2sghtml_44_0.txt
![Warning](https://d1ge0kk1l5kms0.cloudfront.net/images/G/01/webservices/console/warning.png) **Javascript is disabled or is unavailable in your browser.**
aws_legacy_credentials_and_S3/powershelllambdacode_54_0.txt
Get-LMPolicy -FunctionName test -Select Policy
aws_legacy_credentials_and_S3/howtosetupanawslambd_45_0.txt
> _As you add additional accounts, you will need to add the Role Amazon > Resource Number (ARN) to allow Lambda functions in those accounts to access > the bucket._
aws_legacy_credentials_and_S3/AWSToolsLambdaComple_23_0.txt
$LM_Completers = { param ( $commandName , $parameterName , $wordToComplete , $commandAst , $fakeBoundParameter )
aws_legacy_credentials_and_S3/AWSToolsLambdaComple_44_0.txt
# XTZE4KhRJpd/gWbbtRsoK6OLymxfHFa2RG1wEoR9NcMK8wzugCHDVhUBETG9isox # ot52PhY7nMlfrAAYoke3pJ8lDYYA1secOV57kr2j/jMByRhLgnUWc1Su4hhV9a/O # HaxUQD/ged51GBBG2Ao/6H/x8Qx69tTzlDmW5F9OB0MsVNVNA+LhshMS3O1Nz5MB # V5PQ6g== # SIG # End signature block
aws_legacy_credentials_and_S3/howtosetupanawslambd_5_0.txt
[ ](https://hashnode.com/@adamtheautomator) [ ](/rss.xml)
aws_legacy_credentials_and_S3/howtosetupanawslambd_10_0.txt
· [ Jan 14, 2021 ](https://atablog.hashnode.dev/how-to-set-up-an-aws-lambda- powershell-function) ·
aws_legacy_credentials_and_S3/AWSToolsLambdaComple_39_0.txt
$LM_SelectMap = @{ "Select" = @( "Add-LMLayerVersionPermission" , "Add-LMPermission" , "New-LMAlias" , "New-LMEventSourceMapping" , "Publish-LMFunction" , "Remove-LMAlias" , "Remove-LMEventSourceMapping" , "Remove-LMFunction" , "Remove-LMFunctionConcurrency" , "Remove-LMFunctionEventInvokeConfig" , "Remo...
aws_legacy_credentials_and_S3/powershelllambdacode_36_0.txt
* For API details, see [ GetFunctionConcurrency ](https://docs.aws.amazon.com/powershell/latest/reference) in _AWS Tools for PowerShell Cmdlet Reference_ .
aws_legacy_credentials_and_S3/powershelllambdacode_70_0.txt
The following code example shows how to use ` Get-LMResourceTag ` .
aws_legacy_credentials_and_S3/powershelllambdacode_77_0.txt
The following code example shows how to use ` Get-LMVersionsByFunction ` .
aws_legacy_credentials_and_S3/powershelllambdacode_13_0.txt
**Example 1: Adds the three tags (Washington, Oregon and California) and their associated values to the specified function identified by its ARN.**
aws_legacy_credentials_and_S3/powershelllambdacode_171_0.txt
Thanks for letting us know this page needs work. We're sorry we let you down.
aws_legacy_credentials_and_S3/pstoolsec2sghtml_8_0.txt
## Prerequisites
aws_legacy_credentials_and_S3/AWSToolsLambdaComple_30_0.txt
$v | Where-Object { $_ -like "$wordToComplete*" } | ForEach-Object { New-Object System.Management.Automation.CompletionResult $_ , $_ , 'ParameterValue' , $_ } }
aws_legacy_credentials_and_S3/powershelllambdacode_68_0.txt
Get-LMProvisionedConcurrencyConfigList -FunctionName "MylambdaFunction123"
aws_legacy_credentials_and_S3/pstoolsec2sghtml_45_0.txt
To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions.
aws_legacy_credentials_and_S3/powershelllambdacode_31_0.txt
** Tools for PowerShell **
aws_legacy_credentials_and_S3/powershelllambdacode_150_0.txt
Update-LMFunctionConfiguration -FunctionName "MylambdaFunction123" -Handler "lambda_function.launch_instance" -Timeout 600 -Environment_Variable @{ "envvar1"="value";"envvar2"="value" } -Role arn:aws:iam::123456789101:role/service-role/lambda -DeadLetterConfig_TargetArn arn:aws:sns:us-east-1: 123456789101:MyfirstTopic
aws_legacy_credentials_and_S3/powershelllambdacode_44_0.txt
The following code example shows how to use ` Get-LMFunctionList ` .
aws_legacy_credentials_and_S3/howtosetupanawslambd_42_0.txt
### Assigning an S3 Bucket Policy
aws_legacy_credentials_and_S3/howtosetupanawslambd_47_0.txt
### Creating the Lambda Function
aws_legacy_credentials_and_S3/powershelllambdacode_165_0.txt
Kinesis
aws_legacy_credentials_and_S3/howtosetupanawslambd_81_0.txt
## Summary
aws_legacy_credentials_and_S3/pstoolsec2sghtml_15_0.txt
The following example uses the ` New-EC2SecurityGroup ` cmdlet to create a security group for ` EC2-Classic ` .
aws_legacy_credentials_and_S3/powershelllambdacode_75_0.txt
Key Value --- ----- California Sacramento Oregon Salem Washington Olympia
aws_legacy_credentials_and_S3/AWSToolsLambdaComple_4_0.txt
* [ Packages ](/packages) * [ Publish ](/packages/manage/upload) * [ Documentation ](https://go.microsoft.com/fwlink/?LinkID=825202&clcid=0x409)
aws_legacy_credentials_and_S3/powershelllambdacode_22_0.txt
* For API details, see [ GetAccountSettings ](https://docs.aws.amazon.com/powershell/latest/reference) in _AWS Tools for PowerShell Cmdlet Reference_ .
aws_legacy_credentials_and_S3/howtosetupanawslambd_76_0.txt
Finally, with the Lambda function ready to go, and the role objects uploaded to the bucket you can manually invoke the function and verify the new role was created.
aws_legacy_credentials_and_S3/powershelllambdacode_85_0.txt
** Tools for PowerShell **
aws_legacy_credentials_and_S3/howtosetupanawslambd_63_0.txt
### Configuring the Trigger
aws_legacy_credentials_and_S3/powershelllambdacode_37_0.txt
The following code example shows how to use ` Get-LMFunctionConfiguration ` .
aws_legacy_credentials_and_S3/AWSToolsLambdaComple_26_0.txt
# Amazon.Lambda.InvocationType "Invoke-LMFunction/InvocationType" { $v = "DryRun" , "Event" , "RequestResponse" break }
aws_legacy_credentials_and_S3/howtosetupanawslambd_7_0.txt
# How to Set Up an AWS Lambda PowerShell Function
aws_legacy_credentials_and_S3/powershelllambdacode_47_0.txt
Get-LMFunctionList | Sort-Object -Property CodeSize | Select-Object FunctionName, RunTime, Timeout, CodeSize
aws_legacy_credentials_and_S3/AWSToolsLambdaComple_2_0.txt
PowerShell Gallery
aws_legacy_credentials_and_S3/aws_s3_2_1.txt
nable Logging Delete Amazon S3 Objects and Buckets Did this page help you? - Yes Thanks for letting us know we're doing a good job! If you've got a moment, please tell us what we did right so we can do more of it. Did this page help you? - No Thanks for letting us know this page needs work. We're sorry we let you...
aws_legacy_credentials_and_S3/powershelllambdacode_163_0.txt
To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions.
aws_legacy_credentials_and_S3/AWSToolsLambdaComple_31_0.txt
$LM_map = @{ "CompatibleRuntime" = @( "Get-LMLayerList" , "Get-LMLayerVersionList" ) "FunctionVersion" = @( "Get-LMFunctionList" ) "InvocationType" = @( "Invoke-LMFunction" ) "LogType" = @( "Invoke-LMFunction" ) "Runtime" = @( "Publish-LMFunction" , "Update-LMFunctionConfiguration" ) "Starting...
aws_legacy_credentials_and_S3/howtosetupanawslambd_77_0.txt
The function is created but is on a schedule. This means you'd have to wait around for the function to kick off. To prevent waiting, go ahead and kick off the function manually using the code below.
aws_legacy_credentials_and_S3/powershelllambdacode_59_0.txt
** Tools for PowerShell **
aws_legacy_credentials_and_S3/AWSToolsLambdaComple_19_0.txt
if ( $cmdletNames -And $cmdletNames . Length -gt 0 ) { foreach ( $cn in $cmdletNames ) { $fqn = [string] :: Concat ( $cn , ":" , $paramName ) $global:options [ 'CustomArgumentCompleters' ] [ $fqn ] = $scriptBlock } } else { $global:options [ 'CustomArgumentCompleters' ] [ $paramNam...
aws_legacy_credentials_and_S3/powershelllambdacode_133_0.txt
"Washington","Oregon","California" | Remove-LMResourceTag -Resource "arn:aws:lambda:us-west-2:123456789012:function:MyFunction"
aws_legacy_credentials_and_S3/powershelllambdacode_12_0.txt
** Tools for PowerShell **
aws_legacy_credentials_and_S3/AWSToolsLambdaComple_16_0.txt
$cmdletNames = $param2CmdletsMap [ $paramName ] if ( $cmdletNames -And $cmdletNames . Length -gt 0 ) { $args [ "Command" ] = $cmdletNames }
aws_legacy_credentials_and_S3/aws_legacy_credentials_1_0.txt
[ ](/pdfs/powershell/latest/userguide/aws-pst-ug.pdf#shared-credentials-in- aws-powershell "Open PDF") [ AWS ](https://aws.amazon.com) [ Documentation ](/index.html) [ AWS Tools for PowerShell ](/powershell/index.html) [ User Guide ](pstools-welcome.html) Using an IAM Role with AWS Tools for PowerShell Using the Cre...
aws_legacy_credentials_and_S3/howtosetupanawslambd_82_0.txt
Through this post, you have worked with multiple AWS services, like CloudWatch, S3, IAM, and Lambda all through the AWS PowerShell tools. You also created a PowerShell Core Lambda function solving a real-world issue. You can use what you have learned to tackle other use cases. I encourage you to start looking into any ...
aws_legacy_credentials_and_S3/powershelllambdacode_148_0.txt
** Tools for PowerShell **
aws_legacy_credentials_and_S3/howtosetupanawslambd_66_0.txt
* Selects the Lambda function that you just published. * Creates a CloudWatch event rule to run hourly. * Assigns a target - the target identifies the action the event will take when triggered, which is the Lambda function. * Associates the target with the rule and applies permission for the Lambda function to be invok...
aws_legacy_credentials_and_S3/powershelllambdacode_94_0.txt
CodeSha256 : /NgBMd...gq71I= CodeSize : 214784 DeadLetterConfig : Description : My C# Lambda Function Environment : Amazon.Lambda.Model.EnvironmentResponse FunctionArn : arn:aws:lambda:us-west-2:123456789012:function:ToUpper FunctionName : MyFunction Handler : AssemblyName::Nam...
aws_legacy_credentials_and_S3/powershelllambdacode_45_0.txt
** Tools for PowerShell **
aws_legacy_credentials_and_S3/powershelllambdacode_15_0.txt
* For API details, see [ TagResource ](https://docs.aws.amazon.com/powershell/latest/reference) in _AWS Tools for PowerShell Cmdlet Reference_ .
aws_legacy_credentials_and_S3/powershelllambdacode_147_0.txt
The following code example shows how to use ` Update-LMFunctionConfiguration ` .
aws_legacy_credentials_and_S3/howtosetupanawslambd_15_0.txt
## Preparing your Environment
aws_legacy_credentials_and_S3/pstoolsec2sghtml_17_0.txt
sg-0a346530123456789
aws_legacy_credentials_and_S3/howtosetupanawslambd_64_0.txt
A Lambda function requires some other action to trigger it. It could be a specific time schedule, an event occurring in another AWS service, or simply manually triggered when needed. For this use case, create a scheduled trigger for every hour using a CloudWatch Event.
aws_legacy_credentials_and_S3/powershelllambdacode_21_0.txt
TotalCodeSizeLimit TotalCodeSizeUsed ------------------ ----------------- 80530636800 15078795
aws_legacy_credentials_and_S3/AWSToolsLambdaComple_36_0.txt
$asEnumerableType = $type . GetInterface ( 'System.Collections.Generic.IEnumerable`1' ) if ( $asEnumerableType -and $type -ne [System.String] ) { $type = $asEnumerableType . GetGenericArguments ( ) [ 0 ] } }