Downloads of 220.127.116.11
The AWS Tools for PowerShell Core lets developers and administrators manage their AWS services from the PowerShell Core scripting environment.
PS> Save-Module -Name AWSPowerShell.NetCore -Path <path>
PS> Install-Module -Name AWSPowerShell.NetCore
See Documentation for more details.
### 18.104.22.168 (2016-12-02)
Roll-up release of all new features and services added during AWS re:Invent 2016:
* Amazon API Gateway
- Updated and added cmdlets to support publishing your APIs on Amazon API Gateway as products on the AWS Marketplace. You can use cmdlets to associate your APIs on API Gateway with Marketplace Product Codes. API Gateway will then send metering data to the Marketplace Metering Service on your behalf. New cmdlets also enable documenting your API.
* Amazon EC2
- Updated cmdlets with support for IPv6 new F1 Instance types.
* Amazon Pinpoint
- Added support for the new Amazon Pinpoint service. Amazon Pinpoint makes it easy to run targeted campaigns to improve user engagement. Pinpoint helps you understand your users behavior, define who to target, what messages to send, when to deliver them, and tracks the results of the campaign. Cmdlets for the new service have the noun prefix 'PIN' and can be viewed using the command 'Get-AWSCmdletName -Service PIN'.
* Amazon Simple Systems Management
- Updated cmdlets to support all new features announced during the conference.
* Amazon Lightsail
- Added support for the new Amazon Lightsail service, a simplified VM creation and management service. Cmdlets for the new service have the noun prefix 'LS' and can be viewed with the command 'Get-AWSCmdletName -Service LS'.
* Amazon Polly
- Added suport for the new Amazon Polly service. Amazon Polly service turns text into lifelike speech, making it easy to develop applications that use high-quality speech to increase engagement and accessibility. Cmdlets for this service have a noun prefix of 'POL' and can be viewed with the command 'Get-AWSCmdletName -Service POL'.
* Amazon Rekognition
- Added support for the new Amazon Rekognition service, a deep-learning based service to search, verify and organize images. With Rekognition, you can detect objects, scenes, and faces in images. You can also search and compare faces. Cmdlets for the service have the noun prefix 'REK' and can be viewed with the command 'Get-AWSCmdletName -Service REK'.
* AWS AppStream
- Added support for AWS AppStream, a fully managed desktop application streaming service that provides users instant access to their apps from a web browser. The cmdlets for the new service have the noun prefix 'APS' and can be viewed using the command 'Get-AWSCmdletName -Service APS'.
* AWS CodeBuild
- Added support for the new AWS CodeBuild service, a fully-managed build service in the cloud. CodeBuild compiles source code, runs tests, and produces packages that are ready to deploy. Cmdlets for this service have a noun prefix of 'CB' and can be viewed with the command 'Get-AWSCmdletName -Service CB'.
* AWS DirectConnect
- Updated cmdlets to support IPv6. The update includes two new cmdlets, New-DCBGPPeer (CreateBGPPeer API) and Remove-DCBGPPeer (DeleteBGPPeer API).
* AWS Elastic Beanstalk
- Updated cmdlets to support the new integration with AWS CodeBuild.
* AWS Lambda
- Added cmdlet Get-LMAccountSetting to support the new GetAccountSettings API, added dotnetcore 1.0 as a supported runtime, and added support for DeadLetterConfig and event source mappings with Kinesis streams.
* AWS OpsWorksCM
- Added support for the new AWS OpsWorks Managed Chef service, enabling single tenant Chef Automate server. The Chef Automate server is fully managed by AWS and supports automatic backup, restore and upgrade operations. Cmdlets for the new service have the noun prefix 'OWCM' and can be viewed using the command 'Get-AWSCmdletName -Service OWCM'.
* AWS Shield
- Added support for the new AWS Shield service. AWS Shield is a managed Distributed Denial of Service (DDoS) protection for web applications running on AWS. Cmdlets for this service have a noun prefix of 'SHLD' and can be viewed with the command 'Get-AWSCmdletName -Service SHLD'.
* AWS StepFunctions
- Added support for the new AWS StepFunctions service. AWS StepFunctions allows developers to build cloud applications with breakthrough reliability using state machines. Cmdlets for the new service have the noun prefix 'SFN' and can be viewed using the command 'Get-AWSCmdletName -Service SFN'.
* AWS X-Ray
- Added support for the new AWS X-Ray service. AWS X-Ray helps developers analyze and debug distributed applications. With X-Ray, you can understand how your application and its underlying services are performing to identify and troubleshoot the root cause of performance issues and errors. Cmdlets for the new service have the noun prefix 'XR' and can be viewed with the command 'Get-AWSCmdletName -Service XR'.
* AWS Import/Export Snowball
- Updated cmdlets to support a new job type, added cmdlets to support the new cluster apis, and the new AWS Snowball Edge device to support local compute and storage use cases.
Copyright 2012-2016 Amazon.com, Inc. or its affiliates. All Rights Reserved.
This module has no dependencies.
|AWSPowerShell.NetCore 3.3.283.0 (latest stable)||4030||Friday, May 18 2018|
|AWSPowerShell.NetCore 3.3.270.0||1617||Wednesday, April 25 2018|
|AWSPowerShell.NetCore 22.214.171.124||2115||Monday, March 26 2018|
|AWSPowerShell.NetCore 126.96.36.199||1571||Friday, March 02 2018|
|AWSPowerShell.NetCore 188.8.131.52||1136||Tuesday, February 13 2018|
|AWSPowerShell.NetCore 184.108.40.206||1139||Thursday, January 25 2018|
|AWSPowerShell.NetCore 220.127.116.11||94||Tuesday, January 23 2018|
|AWSPowerShell.NetCore 18.104.22.168||390||Tuesday, January 16 2018|
|AWSPowerShell.NetCore 22.214.171.124||148||Friday, January 12 2018|
|AWSPowerShell.NetCore 126.96.36.199||395||Tuesday, January 02 2018|
|AWSPowerShell.NetCore 188.8.131.52||348||Tuesday, December 19 2017|
|AWSPowerShell.NetCore 184.108.40.206||274||Wednesday, December 13 2017|
|AWSPowerShell.NetCore 220.127.116.11||274||Friday, December 08 2017|
|AWSPowerShell.NetCore 18.104.22.168||265||Saturday, December 02 2017|
|AWSPowerShell.NetCore 22.214.171.124||177||Tuesday, November 28 2017|
|AWSPowerShell.NetCore 126.96.36.199||78||Saturday, November 25 2017|
|AWSPowerShell.NetCore 188.8.131.52||397||Tuesday, November 14 2017|
|AWSPowerShell.NetCore 184.108.40.206||224||Thursday, November 09 2017|
|AWSPowerShell.NetCore 220.127.116.11||287||Wednesday, November 01 2017|
|AWSPowerShell.NetCore 18.104.22.168||101||Monday, October 30 2017|
|AWSPowerShell.NetCore 22.214.171.124||266||Tuesday, October 24 2017|
|AWSPowerShell.NetCore 126.96.36.199||311||Tuesday, October 17 2017|
|AWSPowerShell.NetCore 188.8.131.52||412||Monday, October 09 2017|
|AWSPowerShell.NetCore 184.108.40.206||542||Friday, September 29 2017|
|AWSPowerShell.NetCore 220.127.116.11||436||Friday, September 22 2017|
|AWSPowerShell.NetCore 18.104.22.168||662||Sunday, September 17 2017|
|AWSPowerShell.NetCore 22.214.171.124||307||Sunday, September 10 2017|
|AWSPowerShell.NetCore 126.96.36.199||775||Friday, August 25 2017|
|AWSPowerShell.NetCore 188.8.131.52||479||Thursday, August 17 2017|
|AWSPowerShell.NetCore 184.108.40.206||746||Friday, August 04 2017|
|AWSPowerShell.NetCore 220.127.116.11||392||Friday, July 28 2017|
|AWSPowerShell.NetCore 18.104.22.168||693||Friday, July 07 2017|
|AWSPowerShell.NetCore 22.214.171.124||488||Friday, June 23 2017|
|AWSPowerShell.NetCore 126.96.36.199||200||Monday, June 19 2017|
|AWSPowerShell.NetCore 188.8.131.52||282||Friday, June 09 2017|
|AWSPowerShell.NetCore 184.108.40.206||178||Monday, June 05 2017|
|AWSPowerShell.NetCore 220.127.116.11||59||Friday, June 02 2017|
|AWSPowerShell.NetCore 18.104.22.168||83||Wednesday, May 31 2017|
|AWSPowerShell.NetCore 22.214.171.124||128||Friday, May 26 2017|
|AWSPowerShell.NetCore 126.96.36.199||240||Friday, May 19 2017|
|AWSPowerShell.NetCore 188.8.131.52||197||Friday, May 12 2017|
|AWSPowerShell.NetCore 184.108.40.206||185||Friday, May 05 2017|
|AWSPowerShell.NetCore 220.127.116.11||165||Monday, May 01 2017|
|AWSPowerShell.NetCore 18.104.22.168||157||Monday, April 24 2017|
|AWSPowerShell.NetCore 22.214.171.124||236||Wednesday, April 12 2017|
|AWSPowerShell.NetCore 126.96.36.199||38||Tuesday, April 11 2017|
|AWSPowerShell.NetCore 188.8.131.52||73||Friday, April 07 2017|
|AWSPowerShell.NetCore 184.108.40.206||705||Saturday, April 01 2017|
|AWSPowerShell.NetCore 220.127.116.11||90||Wednesday, March 29 2017|
|AWSPowerShell.NetCore 18.104.22.168||125||Friday, March 24 2017|
|AWSPowerShell.NetCore 22.214.171.124||66||Wednesday, March 22 2017|
|AWSPowerShell.NetCore 126.96.36.199||116||Friday, March 17 2017|
|AWSPowerShell.NetCore 188.8.131.52||41||Thursday, March 16 2017|
|AWSPowerShell.NetCore 184.108.40.206||60||Monday, March 13 2017|
|AWSPowerShell.NetCore 220.127.116.11||126||Tuesday, March 07 2017|
|AWSPowerShell.NetCore 18.104.22.168||137||Tuesday, February 28 2017|
|AWSPowerShell.NetCore 22.214.171.124||161||Friday, February 24 2017|
|AWSPowerShell.NetCore 126.96.36.199||42||Thursday, February 23 2017|
|AWSPowerShell.NetCore 188.8.131.52||60||Monday, February 20 2017|
|AWSPowerShell.NetCore 184.108.40.206||29||Friday, February 17 2017|
|AWSPowerShell.NetCore 220.127.116.11||30||Wednesday, February 15 2017|
|AWSPowerShell.NetCore 18.104.22.168||96||Friday, February 10 2017|
|AWSPowerShell.NetCore 22.214.171.124||56||Wednesday, February 08 2017|
|AWSPowerShell.NetCore 126.96.36.199||160||Friday, January 27 2017|
|AWSPowerShell.NetCore 188.8.131.52||30||Thursday, January 26 2017|
|AWSPowerShell.NetCore 184.108.40.206||42||Wednesday, January 25 2017|
|AWSPowerShell.NetCore 220.127.116.11||239||Wednesday, January 18 2017|
|AWSPowerShell.NetCore 18.104.22.168||22||Tuesday, January 17 2017|
|AWSPowerShell.NetCore 22.214.171.124||57||Friday, January 13 2017|
|AWSPowerShell.NetCore 126.96.36.199||53||Monday, January 09 2017|
|AWSPowerShell.NetCore 188.8.131.52||46||Thursday, January 05 2017|
|AWSPowerShell.NetCore 184.108.40.206||55||Friday, December 30 2016|
|AWSPowerShell.NetCore 220.127.116.11||98||Friday, December 23 2016|
|AWSPowerShell.NetCore 18.104.22.168||24||Thursday, December 22 2016|
|AWSPowerShell.NetCore 22.214.171.124||117||Tuesday, December 20 2016|
|AWSPowerShell.NetCore 126.96.36.199||182||Friday, December 16 2016|
|AWSPowerShell.NetCore 188.8.131.52||109||Friday, December 09 2016|
|AWSPowerShell.NetCore 184.108.40.206||15||Thursday, December 08 2016|
|AWSPowerShell.NetCore 220.127.116.11||25||Wednesday, December 07 2016|
|AWSPowerShell.NetCore 18.104.22.168 (this version)||65||Saturday, December 03 2016|
|AWSPowerShell.NetCore 22.214.171.124||242||Wednesday, November 23 2016|
|AWSPowerShell.NetCore 126.96.36.199||34||Tuesday, November 22 2016|
|AWSPowerShell.NetCore 188.8.131.52||40||Saturday, November 19 2016|
|AWSPowerShell.NetCore 184.108.40.206||29||Thursday, November 17 2016|
|AWSPowerShell.NetCore 220.127.116.11||49||Monday, November 14 2016|
|AWSPowerShell.NetCore 18.104.22.168||613||Wednesday, October 26 2016|
|AWSPowerShell.NetCore 22.214.171.124||90||Thursday, October 20 2016|
|AWSPowerShell.NetCore 126.96.36.199||20||Wednesday, October 19 2016|
|AWSPowerShell.NetCore 188.8.131.52||31||Monday, October 17 2016|
|AWSPowerShell.NetCore 184.108.40.206||37||Friday, October 14 2016|
|AWSPowerShell.NetCore 220.127.116.11||40||Wednesday, October 12 2016|
|AWSPowerShell.NetCore 18.104.22.168||52||Friday, October 07 2016|
|AWSPowerShell.NetCore 22.214.171.124||65||Friday, September 30 2016|
|AWSPowerShell.NetCore 126.96.36.199||37||Wednesday, September 28 2016|
|AWSPowerShell.NetCore 188.8.131.52||66||Thursday, September 22 2016|
|AWSPowerShell.NetCore 184.108.40.206||15||Wednesday, September 21 2016|
|AWSPowerShell.NetCore 220.127.116.11||36||Monday, September 19 2016|
|AWSPowerShell.NetCore 18.104.22.168||54||Thursday, September 08 2016|
|AWSPowerShell.NetCore 22.214.171.124||141||Tuesday, August 23 2016|