When following the steps to upload a lambda function to AWS, the timeout value under Advanced Settings can only be set to 60 secs but in fact it can be set to up to 5 mins (300 secs) through the AWS Lambda Console on the web.

It looks like the code is that needs to be set to 300 is:

com.amazonaws.eclipse.lambda/src/com/amazonaws/eclipse/lambda/upload/wizard/page/FunctionConfigurationComposite.java
94 private static final int MAX_TIMEOUT = 60;

The CloudFormation Editor could be improved with better error reporting and bracket matching.

Right now, if you make a single mistake in the JSON text an error highlight appears but it is not usually close to where the error happened.

The most common types of errors are mismatched brackets - it would be great for the editor to automatically highlight the corresponding brackets when hovering over it or moving the cursor to a bracket.

The feature of formatting the template does not help if the template is not valid JSON - this would be a great way to detect basic errors of extra commas or mismatched brackets.

JSON editing is a pain and anything you can do to improve this would be a great help.

On Windows the order of dialog buttons should be [OK] [Cancel] and not the other way around.

The Select a region can be found in Preferences > AWS Toolkit > Configure Regional Account (the tab item with the green plus sign).

Hello,

The following message came up when I tried opening an Elastic Beanstalk environment:

!ENTRY org.eclipse.ui 2 0 2016-04-12 16:27:56.298 !MESSAGE The 'org.eclipse.ui.startup' extension from 'com.amazonaws.eclipse.elasticbeanstalk' does not provide a 'class' attribute. This usage is deprecated and a 'class' attribute should be provided. The release after Mars (4.5) will no longer support the deprecated usage!

I am running Eclipse 4.5 (Mars) Java EE with openjdk-7-jdk. Should I try Luna?

Thanks,
Dylan

It appears as if this plug-in doesn't support Lambda functions that implement the RequestStreamHandler interface. I'm trying to upload them via the 'Upload function to Lamba' option from within Eclipse and it presents me with the following error.

https://cloudup.com/cCMd-BarFLP

I am aiming to get started with CloudFormation and a good editor should help a lot in learning CF and in writing this efficiently. I have used Eclipse before and was expecting capabilities perhaps akin to the JDT editors in the CloudFormation Template Editor.

Assuming that AWS Toolkit for Eclipse and Visual Studio are providing similar features the following video shows the kind of capabilities I was looking for: AWS Toolkit for Microsoft Visual Studio at https://www.youtube.com/watch?v=3QydWLiCqWk

Also I briefly looked into source code of the eclipse editor plugin as well as found a schema mentioned which appears to indicate that this should work much better.

I installed the OS X version of Eclipse recommend at http://docs.aws.amazon.com/AWSToolkitEclipse/latest/GettingStartedGuide/tke_setup_prereqs.html (eclipse-jee-kepler-R-macosx-cocoa-x86_64.tar.gz) and I am running this on OS X 10.9.5. However I am also seeing this on a Windows 7 machine.

I can open the editor on a file called cloudformer.template.json with context Menu then Open With/Other.. and then select 'Amazon CloudFormation Template Editior'. The Editor appears to open fine and I can edit as if in a basic JSON editor as expected.

However I do not get see much additional assistance. For example when introducing errors such as changing "true" to "tr sd ue".
Content assist appears to react only for:

• The Type Value
• At the top level suggesting Conditions, Mappings, Outputs, and Parameters. When I select Conditions it actually merges the value with the AWSTemplateFormatVersion value leading to a syntax error.

I'd be happy to provide more details as needed.

If you add the Attributes API, not reflected in the refresh.
"Item Names adn Attributes" and "Data -> Edit"

Most of the dialogs from the AWS Toolkit don't have a window title (i.e. the Shell's text is empty). Is that on purpose?

Unless i'm missing something, there doesn't appear to be a way to easily see the EC2 Instances names. There is no column for it, or no way to add a column for it. Ok, you can see it in the tags, but for me it's buried in there amongst other tags.

The AWS Console recognizes the utility of this, why not the eclipse plugin? I, for one, would like to see a name column, or an easy way to customize the table.

I'm trying to deploy a project to Tomcat and I'm getting the following error

Unable to create new environment: No Solution Stack named '64bit Amazon Linux 2014.03 v1.0.2 running Tomcat 7 Java 7' found. (Service: AWSElasticBeanstalk; Status Code: 400; Error Code: InvalidParameterValue; Request ID: c91cd645-f630-11e3-9298-5711ea681218)
No Solution Stack named '64bit Amazon Linux 2014.03 v1.0.2 running Tomcat 7 Java 7' found. (Service: AWSElasticBeanstalk; Status Code: 400; Error Code: InvalidParameterValue; Request ID: c91cd645-f630-11e3-9298-5711ea681218)

Whereas the current version on AWS is listed as
Tomcat 7 Java 7 on 64bit Amazon Linux 2014.03 v1.0.3.

I've tried updating my plugin in eclipse, but it says it's up to date.

Steps:

1. open the Install New Software dialog and enter https://aws.amazon.com/eclipse
2. select the AWS Core Management Tools and AWS Deployment Tools
3. press Next and again Next

On the upcoming page, there are two licensess to be accepted that are apparently the same Apahce v2 licnese. One of them should be enough.

When deploying a CloudFormation template using the 'Run on AWS' -> Update Stack menu item, the list of stacks that is populated in the drop down includes all stacks past and present. The list keeps growing even if the corresponding stacks have been deleted in CloudFormation.
This makes it confusing to find the exact name of the stack that needs to be updated.
It would be better to query CloudFormation for the current list of Created stacks that can be selected for Update.

You have to open the Java build path libraries again...

Hi,
I am using the AWS toolkit for Eclipse for DynamoDB . When i double click on the table and open query editor and try to add items. it shows only the Hash and Range Key does not allow to add additional attributes like in the Console. the Examples shows the screenshot where all different columns are shown with option to edit them . but i dont see that option at all in my eclipse plugin . i am using the Neon .3 JEE and also installed latest toolkit version

2.3.1.v201703211023
AWS Toolkit for Eclipse Core (Required)

After installing the AWS Toolkit for Eclipse and restarting Eclipse, a dialog appears that asks for credentials (see below). However, this is unexpected as the use may not even want to lok into an AWS account right now. Wouldn't it be better to defer the login until actually necessary?

On a technical note, the dialog requires plug-in activation of one or more AWS plug-ins which violates the lazy activation policy of Eclipse.

From a clean installation of Eclipse Mars, with a clean installation of AWS, and after connecting with a user with "administrator" permissions, select "EC2 Security groups" then "default VPC security group".

An NPE is triggered as follows:

!ENTRY org.eclipse.jface 4 2 2015-07-15 12:28:01.360
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface".
!STACK 0
java.lang.NullPointerException
at com.amazonaws.eclipse.ec2.ui.securitygroups.PermissionsComposite$PermissionsTableProvider.formatPortRange(PermissionsComposite.java:179)
at com.amazonaws.eclipse.ec2.ui.securitygroups.PermissionsComposite$PermissionsTableProvider.getColumnText(PermissionsComposite.java:144)
at org.eclipse.jface.viewers.TableColumnViewerLabelProvider.update(TableColumnViewerLabelProvider.java:66)
at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:154)
at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:949)
at org.eclipse.jface.viewers.AbstractTreeViewer$UpdateItemSafeRunnable.run(AbstractTreeViewer.java:114)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:1029)
at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:473)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2176)
at org.eclipse.jface.viewers.AbstractTreeViewer.createTreeItem(AbstractTreeViewer.java:843)
at org.eclipse.jface.viewers.AbstractTreeViewer$1.run(AbstractTreeViewer.java:818)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:791)
at org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:611)
at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:762)
at org.eclipse.jface.viewers.AbstractTreeViewer.internalInitializeTree(AbstractTreeViewer.java:1541)
at org.eclipse.jface.viewers.TreeViewer.internalInitializeTree(TreeViewer.java:790)
at org.eclipse.jface.viewers.AbstractTreeViewer$5.run(AbstractTreeViewer.java:1525)
at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1462)
at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:366)
at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1423)
at org.eclipse.jface.viewers.AbstractTreeViewer.inputChanged(AbstractTreeViewer.java:1517)
at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:292)
at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1701)
at com.amazonaws.eclipse.ec2.ui.securitygroups.PermissionsComposite$4.run(PermissionsComposite.java:339)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
at org.eclipse.equinox.launcher.Main.run(Main.java:1515)

For testing I am running DynamoDB on my computer (OS X) inside a Docker container trayio/dynamodb-local as follows:

dev $ docker run -i -t -p 7777:7777 tray/dynamodb-local -inMemory -port 7777

With the aws cli I can access the local DynamoDB with the --endpoint-url parameter as follows:

dev $ aws dynamodb list-tables --endpoint-url http://$(docker-machine ip default):7777
TABLENAMES       gamesdocker-machine ip default
# where 
dev $ docker-machine ip default
192.168.99.100

I tried to configure an AWS account from the AWS Explorer to do this but I could not find the correct option. It would be very cool to explore the local DynamoDB content with a UI.

Is there some way to configure this?

I got stuck after cloning this repository and importing all projects into a new workspace.

There seems to be no target platform definition and I haven't found instructions how to setup the Eclipse IDE to make changes to the AWS Toolkit for Eclipse.

The second menu in the Update CloudFormation Stack wizard shows the values of the parameters but you have to edit at least one value to proceed. If I want to keep the parameter values the same as before, I'm forced to edit the text field and make a change and revert it before I can move to the next step.
Please make it optional to edit the values of the parameters - there are many cases where the template is being updated but the parameters stay unchanged.

with tomcat 8 on aws it is not possible to deploy a java 8 web app using 3.1 web module facet.

Steps:
latest Springsource Tool Suite. Install AWS toolkit. create simple spring starter project with web module using java 1.8 and packaging war.
try to add to Elastic Beanstalk tomcat 8.

works on local tomcat 8 Server.

Hi all,
I've used the default and latest version of Eclipse: Mars and installed AWS Toolkit. But when I try to create a new AWS java project, it can not find the AWS java sdk at all. I am sure it is in the installed software list. I guess it might be an incompatible issue of the Mars version. Could anybody help? Thanks!

I used the Create new AWS Java Project wizard to create a sample Java project and deploy it to ElasticBeanstalk (EB). I noticed that it automatically copied my AWS credentials and placed them in the clear in a property file that was bundled and uploaded to EB.
The sample app then uses the credentials to query EC2 instances, S3 buckets and DyanmoDB tables.
This is not recommended as EC2 Instance Profiles should be used instead to grant these specific permissions.

@fulghum @david-at-aws
I am trying to deploy a sample application using beanstalk. I installed AWS Core management tools, AWS deployment tools , AWS data management tools on eclipse. The version of AWS Toolkit for eclipse is 2.3.1. I was unable to create beanstalk environment :

Unable to create new environment: No Solution Stack named '64bit Amazon Linux 2014.09 v1.0.0 running Tomcat 7 Java 7' found. (Service: AWSElasticBeanstalk; Status Code: 400; Error Code: InvalidParameterValue; Request ID: d110a588-cb2b-11e6-9f23-e38f4be429de)

Note : I am using JDK 1.8 and I set up AWS tomcat server 8.

I understand that that 64bit Amazon Linux 2014.09 v1.0.0 running Tomcat 7 Java 7 is deprecated now and the current one supported is 64bit Amazon Linux 2016.09 v2.4.0 running Tomcat 8 Java 8. This is a new solution stack name. I had not mentioned solution stack name - "64bit Amazon Linux 2014.09 v1.0.0 running Tomcat 7 Java 7" when creating the beanstalk environment. I think its taking it by default because of AWS toolkit version being 2.3.1.

I think it is the version issue with AWS toolkit and I have tried to upgrade seeing docs but in vain. I did read that this issue has been fixed with v2.5 onwards. On eclipse Neon and Luna, I am not able to upgrade AWS toolkit to above 2.3.1 because https://aws.amazon.com/eclipse and https://aws.amazon.com/eclipse/site.xml is not updated with the same. But I am not really sure if v2.3.1 is the cause of this problem.

So I really need some help using latest version of toolkit and getting the right solution stack.
Any help will be appreciated.
Thanks :)

it would be helpful to be able to make use of UpdateFunctionCode API to make code update and publishing version on Lambda as an atomic call
currently, i don't see this is supported

When trying to create an AWS Lambda project forthe first time, I see the following error message:

The selected input type requires the AWS Java SDK dependency. Please install the SDK first (Window -> Preference -> AWS Toolkit -> AWS SDK for Java) and then retry.

To solve the problem, I need to close the New AWS Lambda wizard (thereby discarding all input I already made), memorize the path the the preference page and finally open the page.

It would help if there was some sort of a link to open the preference page

I have seen that Display.getCurrent().getActiveShell() is used in several places to obtain the parent shell to open a dialog or wizard.

One such example can be found in the NewLambdaFunctionHandler

This can have unwanted side effects, for example, if the currently active shell is a progress dialog. Because the dialog is created as a child shell of the given parent shell, it is closed if the parent shell closes. This means that if the progress dialog is closed (usually because no more user jobs are running), the dialog that was opened this way is also closed - usually not what the user would expect.

Prefer to use a permanent shell as the parent, such as the shell of the active workbench window. For example PlatformUI.getWorkbench()getActiveWorkbenchWindow().getShell() or, when in a handler HandlerUtil.getActiveWorkbenchWindow().

Clicking through the AWS preference pages, when I hit the Toolkit Analytics page the entire dialog expands horizontally (see below).

Just a report here as I haven't had a chance to do any analysis.

Environment:

1. OS: Windows 10 Pro 64Bit
2. JDE 1.7
3. Eclipse Marse 1 Release (4.5.1) Build id 2015094-1200
4. Amazon Toolkit for Eclipse Core: Version v201511040938

Steps to recreate:

1. Open AWS Explorer (Works)
2. Open S3 (Works and lists buckets)
3. Right Click (Select Open in S3 Bucket Editor) - Nothing happens, no exception message.

I hope this helps.

Thanks

Joe

Steps:

1. create a new AWS Lambda project
2. in the generated LambdaFunctionHandler, navigate the method declaration and open the Context type.

Instead of showing the source code, only the class file editor opens. Having access to source code helps in many situations, such as debugging, unclear JavaDoc, etc. Besides that, there should be source attachements for consistency reasons as other AWS libraries come with sources.

From a brand new clean Eclipse Mars installation, along with a brand new clean AWS installation, when an attempt is made to configure credentials for the first time, all tabs result in an object being displayed called "Unable to connect".

This object has no context sensitive help, and doesn't respond to being double clicked. Without a reason given for "unable to connect" the end user is left guessing.

(After some googling for a while I stumbled on someone claiming that this was a permissions problem. Allocating "administrator" permissions allowed further progress, however users should not have to resort to google-archeology to get the job done).

The DynamoDB Explorer doesn't show any tables unless I create them from within the explorer. Is there a way it can display the tables that I created through the AWS Console or CLI?

Hi,
When I was trying to install aws toolkit for eclipse, I am getting an error "Cannot complete the install because one or more required items could not be found". I am using Eclipse 4.5(Mars) M1

when I use AmazonS3Client to connect amazon s3, Does the sdk authenticate S3 server? for example, it will authenticate the ca certificate of amazon

I'm using the Eclipse Plugin to upload java code to Lambda. Every time I do this, it does not pick up the existing S3 buckets but forces me to create a new bucket. This is bad since I now end up with lots of buckets, one for each time I upload a new code update.

I know this is the eclipse toolkit but a plugin for android studio would be very nice too since that is the way android is moving

I'm proposing that the CloudFormationV1.schema file be moved over to GitHub under a project, either existing or new, under the AWS org so that it can benefit from community review and contributions.

For example, I have found errors and omissions as described in #38 which could be rapidly corrected by submitting PRs from community members. Accepting these PRs would still be at the discretion of the AWS members who would continue to curate the schema content.

This would help to improve the accuracy of tools that rely on the schema for automated code generation such as:

• aws/aws-toolkit-eclipse
• stevenjack/cfndsl
• ezshield/posh-awscfn
• shalupov/idea-cloudformation

There seems to be no way to select and copy a key from DynamoDB or SimpleDB view. The editable elements can be selected and copied, but not the keys. This is quite frustrating, as keys tend to be UUIDs or other generated and hard to retype correctly strings.

Please add a way to copy the keys to the clipboard.

I don't understand how it would be possible to create workerservlets that could execute jobs that take longer that 60 seconds.

if the example at
https://github.com/aws/aws-toolkit-eclipse/blob/master/com.amazonaws.eclipse.elasticbeanstalk/templates/worker/src/WorkerServlet.java
is modified to contain Thread.sleep(120 * 1000); then the task gets submitted 10 times and then ends up in the dead letter queue.

Any help would be gratefully received.

In the Auto Scaling configuration for beanstalk environments, in the eclipse plugin it says Measurement Period and Breach Duration are in seconds. If you look at the AWS web console for those same configuration settings, it says they are in minutes.

Very confusing! I'm assuming the AWS web console is correct.

aws lambda current momory limit is 1536 but over 1024 cause error.

I ran into an issue deploying a java app using the eclipse toolkit.

The error message is:
Unable to create new environment: Status Code: 400, AWS Service: AWSElasticBeanstalk, AWS Request ID: b6c03eef-e1d6-11e3-8741-6571d7aece34, AWS Error Code: InvalidParameterValue, AWS Error Message: No Solution Stack named '64bit Amazon Linux 2013.09 v1.0.1 running Tomcat 7 Java 7' found.

Status Code: 400, AWS Service: AWSElasticBeanstalk, AWS Request ID: b6c03eef-e1d6-11e3-8741-6571d7aece34, AWS Error Code: InvalidParameterValue, AWS Error Message: No Solution Stack named '64bit Amazon Linux 2013.09 v1.0.1 running Tomcat 7 Java 7' found.

The problem is that the Solution Stack name '64bit Amazon Linux 2013.09 v1.0.1 running Tomcat 7 Java 7' is not valid.

The correct solution stack name should be "64bit Amazon Linux 2014.03 v1.0.2 running Tomcat 7 Java 7" (as seen from the output of CLI command 'aws elasticbeanstalk list-available-solution-stacks').

There does not seem to be a way to configure the Solution Stack Name in the eclipse toolkit. I.e. the drop down shows "Tomcat 7 Java 7" but does not allow one to set the actual Solution Stack Name.

Please also see a similar issue reported in the AWS Developer Forums here: https://forums.aws.amazon.com/thread.jspa?messageID=544685&tstart=0

Hi,

I couldn't see any items after entering the update site.

Version: Eclipse Java EE IDE for Web Developers, Neon.1a Release (4.6.1)
Site: https://aws.amazon.com/eclipse

Cheers,
Kenny

In Spring Tool Suite/Eclipse, when i got to EBS Storage. It returns a long list and IDE takes some time to resolve. The list returns all snapshots of the EBS, including those created much earlier than the EBS Volume ID.

Example volume, vol-ea260cad created on May 2nd 2015 has snapshots going back to 2008, snapshot ID: snap-d010f6b9. Enhancement would to only show snapshots greater than EBS creation date by default.

Because Eclipse uses JGIT for git integration, eGit does not work with AWS codecommmit in most places. I've opened a bugzilla ticket for the JGIT team here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=472415, but they (nor I) have expertise with AWS IAM auth.

Hey guys,

I'm the maintainer of cfndsl (A ruby DSL for generating CF) and I was talking to a few colleagues who use your eclipse plugin. They mentioned how it's able to auto complete and validate what's entered and that started making me think that there must be a schema somewhere that it's being checked against. After having a look around your code I found this:

CloudFormationV1.schema

Which seems like exactly that, a JSON schema.

My questions is two fold, is this a well maintained and generally up-to-date schema for the resources in CF?

If so would you mind if I added it as a dependency to cfndsl (I'll work out the best way of using it + caching etc) as this would really help with the ongoing maintenance of the project and help keep it as up-to-date as possible.

Steve

After installing and restarting AWS Toolkit for Eclipse, a pop-up dialog with bunch of errors shows up.

Internal Error when running initial setup wizard Internal Error when scanning legacy AWS account configuration Internal Error when starting the AWS toolkit plugin

And also on closing this, and if go to a particular AWS related tab from Preferences, error will show up.

Currently displayed page contains invalid values.

There seems to be a bug in the CloudFormation schema file at CloudFormationV1.schema for resource AWS::EC2::VPC property InstanceTenancy which is described with a type of Number but lists strings for its allowed-values -- here's the snippet:

          "InstanceTenancy": {
            "type": "Number",
            "allowed-values": [
              "default",
              "dedicated"
            ],
            "required": false,
            "description": "The allowed tenancy of instances launched into the VPC. A value of \"default\" means instances can be launched with any tenancy; a value of \"dedicated\" means instances must be launched with tenancy as dedicated."
          },

I'm submitting this ticket here, although I'm not sure it's the correct forum. I know that there has been some other discussion related to the schema file in #14.

If this is the not the correct mechanism to submit requests related to the CFN schema file, please advise.

The plugin installation is failing from Marketplace in Eclipse Neon Version.

I think it would be useful to add the ability to specify a AWS KMS master key for those that use server side encryption so that Lambda functions can be uploaded to S3 straight from the IDE using the Upload function to AWS Lambda option given by the AWS Lambda plugin.