Tuesday, 27 May 2014

How does the AWS SDK retrieve credentials from IAM roles within EC2 instances

This is another in a series of videos that I am producing for my YouTube channel HowDoYouDoStuff.


In this video, I am going to show you how the AWS SDK retrieves credentials from IAM roles within EC2 instances


You can read the transcript below.


HTML 5 Player



Transcript

Hi guys. I'm Phil Stirpe.

In this video, I am going to show you how the AWS SDK is able to retrieve credentials for an IAM role from within EC2 instances.

This demo was recorded live during the delivery of a recent Developing on AWS course.



Due to the live (from the hip) nature of the demo, I did not produce a transcript for this video.


There you have it.

In this video, I have shown you how the AWS SDK is able to retrieve credentials for an IAM role from within EC2 instances.

Thanks for watching and please feel free to comment and suggest more video topics. Most of all, don't forget to subscribe to keep up with my videos as I release them.

Bye for now.




Flash Player








See you soon

Phil Stirpé
"I don't do average!"






Sunday, 18 May 2014

How to work with DynamoDB using the AWS Toolkit in Visual Studio

This is another in a series of videos that I am producing for my YouTube channel HowDoYouDoStuff.


In this video, I am going to show you how to work with DynamoDB using the AWS Toolkit in Visual Studio


You can read the transcript below.


HTML 5 Player



Transcript

Hi guys. I'm Phil Stirpe.

In this video, I am going to show you how to work with DynamoDB using the AWS Toolkit in Visual Studio.

In an earlier video I showed how to download and install the AWS toolkit into visual studio. And associate it with an IAM user authored created earlier in Amazon web services.

Here is that same user called Frank and if I click on the Edit Account button you can see that we have the access key and secret key which represent Frank’s credentials. These are required by the toolkit when I’m trying to carry out management tasks in visual studio, those credentials can be used to authenticate visual studio with Amazon web services.

By the way, if you did watch that earlier video where I associated with the IAM user you should know that I’ve updated the group that it belongs to, to grant it access to DynamoDB.

In this session I don’t want to look at how we might use the SDK to access DynamoDB programmatically. I just want to look at some of the management tasks that we can carry out in the AWS Explorer window.

So that’s going to be things like create a table, add records, delete a table.

Let’s start with creating a table. I’m just going to right click on DynamoDB and select Create Table.

Am going to go with a table named Trainers and put in a hash key name of TrainerName.

Many of the features available in the AWS console are available here. For example you could enable a range key.

You can specify the read and write capacity. I’ll leave the defaults here although you would be likely to enter higher values for production databases.

You could specify secondary indexes both local and global.

Finally, you could also create an alarm. This could be used to notify you if your throughput exceeds in this case 80% of what you had provisioned. For now I’ll leave all of these options alone. I just want to create a simple table.

Let me click the Create button and now you can see that the Trainers table has been created. A very straightforward process.

If you were working away in visual studio and needed a downloaded be table and didn’t have the time or inclination to create the table programmatically or from the command line or AWS console, it is very simple to do with this plug-in.

Let’s add some records. This is also a simple process.

So I’ll right click the Trainers node and select Open. This opens the query window and reveals the hash key. I can literally just start typing in trainer names.

So I’ll begin by entering a trainer name of Phil.

I’ll need some more so I’ll go with Matt, Mike and Geraldine.

Nice and simple.

And if we had range keys and secondary indexes they would all be available via this window.

I’ll just close down that window and deal with the last thing that I want to show you.

How about deleting a table? That is just a simple to do.

Right click the table, select delete, confirm. Gone.

Nothing too taxing I just wanted to show you how simple it was to add a table, insert records and then delete a table. All without leaving Visual Studio.

There you have it.

In this video, I have shown you how easy it is to work with DynamoDB using the AWS Toolkit in Visual Studio.

Thanks for watching and please feel free to comment on my blog (www.philipstirpe.com) and Facebook page (www.facebook.com/philip.stirpe.tutorials). Perhaps you could suggest more video topics? Most of all, don't forget to subscribe to keep up with my videos as I release them.

Bye for now.






Flash Player








See you soon

Phil Stirpé
"I don't do average!"






How to work with DynamoDB using the AWS Toolkit in Eclipse

This is another in a series of videos that I am producing for my YouTube channel HowDoYouDoStuff.


In this video, I am going to show you how to work with DynamoDB using the AWS Toolkit in Eclipse


You can read the transcript below.


HTML 5 Player



Transcript

Hi guys. I'm Phil Stirpe.

In this video, I am going to show you how to work with DynamoDB using the AWS Toolkit in Eclipse.

In an earlier video I showed you how to install the AWS Toolkit into Eclipse and associate it with an IAM user I created earlier.

In this video I just want to show you how to use the AWS Toolkit to perform some management tasks in Eclipse. In particular DynamoDB.

I’m not going to look at how we can use the SDK to write code to interact with DynamoDB. Rather simply create tables, add records and delete tables.

Just as a reminder here is the user account that I associated with when I installed the AWS toolkit.

So there is an IAM user called Frank. And this is Frank’s access key and secret key. It is by using these credentials that Eclipse via the AWS toolkit is able to get authenticated by Amazon web services.

If you saw the earlier video, a just point out that I have now updated Frank’s privileges ( or at least a group he’s in) to allow access to DynamoDB.

So let’s pick one task to get us started. That’s creating a DynamoDB table. Let me right click this node and select Create Table.

This is the kind of task that the developer might carry out in Eclipse when they need a table to work against but it’s not actually worth writing the code to create one.

Creating a table via the AWS toolkit is as simple as using the AWS console.

Let me put in a table name of trainers and I’ll use a hash key name of TrainerName.

Many of the features available in the AWS console are available here. For example you could enable a range key.

You can specify the read and write capacity. I’ll enter 1 for each although you would be likely to enter higher values for production databases.

You could specify secondary indexes both local and global.

Let me click the Finish button and now you can see that the Trainers table has been created. A very straightforward process.

Another thing that you are likely to want to do quickly in Eclipse as a developer is to enter some records into your DynamoDB table. So let’s try that will stop

I’ll right click on the Trainers node and select Open Query Editor.

You can see the hash key here and I can start entering values.

So I’ll begin by entering a trainer name of Phil.

I’ll need some more so I’ll go with Mike, Matt and Geraldine.

Nice and simple.

As a developer working in Eclipse, if you needed a DynamoDB table and didn’t have access to the AWS console you could simply do it here using the toolkit.

Let’s do one last thing. Not only is it easy to create a table and add records to it using the toolkit in Eclipse, it’s also very easy to delete a table.

So let me just right click on the Trainers node, select delete and then confirm.

Not an exhaustive demo so just wanted to show you how simple it is to add a table, insert records and then delete a table. All without leaving Eclipse.



There you have it.

In this video, I have shown you how easy it is to work with DynamoDB using the AWS Toolkit in Eclipse.

Thanks for watching and please feel free to comment on my blog (www.philipstirpe.com) and Facebook page (www.facebook.com/philip.stirpe.tutorials). Perhaps you could suggest more video topics? Most of all, don't forget to subscribe to keep up with my videos as I release them.

Bye for now.






Flash Player








See you soon

Phil Stirpé
"I don't do average!"






How to work with S3 using the AWS Toolkit in Visual Studio

This is another in a series of videos that I am producing for my YouTube channel HowDoYouDoStuff.


In this video, I am going to show you how to work with S3 using the AWS Toolkit in Visual Studio


You can read the transcript below.


HTML 5 Player



Transcript

Hi guys. I'm Phil Stirpe.

In this video, I am going to show you how to work with S3 using the AWS Toolkit in Visual Studio.

In an earlier video I showed you how to download and install the AWS Toolkit into Visual Studio.

But this video I just want to focus on how we can use the AWS toolkit to access S3 whilst working away in Visual Studio.

In that video I showed you how to configure visual studio to use an IAM user called Frank to connect to Amazon web services. That involved entering Frank’s access key and secret key.

Will now we know that Visual Studio is configured let’s focus on using S3.

This video I don’t want to focus on how we might use the SDK to interact with S3 programmatically. I just want to look at how we would carry out management tasks such as creating buckets, dragging files into buckets, and deleting buckets.

Some just going to try and create a new bucket by right clicking on the S3 node in the AWS Explorer.

Going to call it demobucket. The thing to be aware of the S3 is that bucket names need to be globally unique stop and I have a strong feeling that demobucket will have gone by now.

Now. That name is not available. So I could try adding in a hyphen to create demo-bucket but am pretty sure that name will have gone also.

All right let me try a prefix of qa to come up with a bucket named of qa-demo-bucket.

Now here we are getting a different error message. What is interesting is that I did create that bucket earlier and then delete it. But when recording and other video I earlier to perform the same task in Eclipse, I created a Pre-signed URL that granted access to that bucket for an hour and because of that, Amazon web services is preventing me from creating a bucket with that same name.

I’m going to have to come up with another bucket name. How about my-demo-bucket?

No. That name has gone also. This is getting a bit tedious.

Okay. Let’s go for aws-toolkit-demo-bucket.

While that’s a relief. There we have the bucket.

So that’s a task you might perform in Visual Studio as a developer. It’s not worth writing code to create a bucket. You just want to go ahead and create one.

Good luck with the naming.

Another task that you might want to perform in Visual Studio is to simply drag a file and drop into a bucket to work with.

Once again it’s not worth writing the code to achieve this, you just want to get the job done.

So let’s say I want to drag a file into my bucket.

What are can’t do, is simply drag a file from Windows Explorer end to a bucket node in AWS Explorer. That will simply open the file in Visual Studio.

What I need to do, is to open or browse the bucket in AWS Explorer by right clicking the bucket name and selecting Browse.

The S3 browse window opens and offers me a number of options that let me manage my folders.

One thing I can do, is drag a file from Windows Explorer into this S3 browse window in Visual Studio.

This results in the upload settings dialog appearing where I am asked a number of questions.

There are a couple of flavours of S3 including standard and reduced redundancy storage. If I wanted to upload my file into reduced redundancy storage then I simply need to check this box. I could also request that my file be encrypted at rest. In other words whilst stored in S3.

I’m also able to specify that the file is publicly readable. I don’t want to do that.

If I click on the Permissions tab you can see that there are no permissions granted on this file

If I chose, I could add permissions in via this window which would result in an access control list or ACL. I would still probably want to create some IAM policies.

I don’t want to manage permissions from here. I would want to do that elsewhere. For example the AWS console.

So I’m just going to go ahead and click OK.

There we go, the file has been uploaded.

I was given an option to define an alternate key, but I’m happy to use the file name.

That’s how simple it is to upload a file into S3 whilst working in Visual Studio.

And if I can upload a file, I can just as easily download or delete a file.

Now although I didn’t want to manage permissions whilst in Visual Studio, I do want to look at how people might access assets in S3.

If I right click the file and copy the URL into the clipboard, I could open up an incognito window and paste it into the address bar. I’m using an incognito window by the way, because I am already logged in to Amazon web services in another browser window.

As you can see, when trying to access the file in S3 using this URL, I receive access denied. Which is to be expected as no permissions are granted.

In fact only the ceiling get that anyone that root account and the IAM user called Frank have access to that bucket and its contents.

A clever thing we can do whilst in Visual Studio, is to right click the file again choose a pre-signed URL.

This allows you to create a time stamped, pre-signed URL. By default I am being offered one hour’s access which I will accept.

I will generate the URL. By the way, note that this is for a GET action but I could also specify a PUT action.

Let me copied this URL and paste it into that same browser window.

Notice that it contains an access key has just been generated and expiry time.

When I press enter, the file and its contents are returned to this unauthenticated window using the signed URL.

So I’ll just pop back into Visual Studio stop using the AWS toolkit with been able to perform some simple management tasks with S3 such as creating a bucket, uploading a file and generate a pre-signed URL.

The last thing I want to do is simply delete the bucket and any objects within it as I want to tidy up after myself.

There is more that I could do with S3 and of course now we have the AWS toolkit installed, we also have access to the SDK and therefore could go ahead and write code to interact with the service. But I just wanted to give you a feel for some of the simple management tasks that you could carry out with S3 whilst using the AWS toolkit in Visual Studio.



There you have it.

In this video, I have shown you how easy it is to work with S3 using the AWS Toolkit in Visual Studio.

Thanks for watching and please feel free to comment on my blog (www.philipstirpe.com) and Facebook page (www.facebook.com/philip.stirpe.tutorials). Perhaps you could suggest more video topics? Most of all, don't forget to subscribe to keep up with my videos as I release them.

Bye for now.






Flash Player








See you soon

Phil Stirpé
"I don't do average!"






How to work with S3 using the AWS Toolkit in Eclipse

This is another in a series of videos that I am producing for my YouTube channel HowDoYouDoStuff.


In this video, I am going to show you how to work with S3 using the AWS Toolkit in Eclipse


You can read the transcript below.


HTML 5 Player



Transcript

Hi guys. I'm Phil Stirpe.

In this video, I am going to show you how to work with S3 using the AWS Toolkit in Eclipse.

In an earlier video I showed you how to install the AWS Toolkit into Eclipse and associate it with an IAM user I created earlier.

In fact if I go into the menu and select preferences, you can see that with already configured Eclipse to identify itself as an IAM user called Frank when connecting to Amazon web services. This involves using the user’s access key and secret key.

In the AWS Explorer window in Eclipse you can see a number of AWS services that you can work with. They are the services it is assumed you might work with when working in Eclipse.

In this video I want to work with S3 so let me just expand that node.

The very fact that I can see some buckets listed, proves that Eclipse has been authenticated by Amazon web services and that the AWS user account has privileges to access S3.

In this video I’m not going to show how to use SDK to interact with S3 using code, rather I want to show how you might use S3 as a developer within Eclipse. For example the creation of buckets and copying of files.

Let me begin by creating a bucket.

A right click the S3 node and select create new bucket.

I want to call this bucket demobucket. Now have to be careful because bucket names must be globally unique as you can see that name is already taken.

Let me try adding a hyphen and calling it demo-bucket. No that’s also in use.

Let me try qa-demo-bucket. That’s okay.

So that’s a thing to remember. This is not an Eclipse thing or and AWS toolkit thing, it’s an S3 thing.

I’ll click the Finish button and now I have a bucket.

It may well be that when you’re working in Eclipse you need an S3 bucket is not worth the effort to write code to create one. As you have seen you can use simple right click to create one.

Now that created a bucket in Eclipse, let’s look at something else I might want to do. I might simply want to upload some files into a bucket whilst I’m working away in Eclipse.

Well I can just do that with a drag and drop.

If I open up Windows Explorer, I can just drag a file onto a bucket in the AWS Explorer window and the AWS toolkit will take care of the upload for me.

The AWS toolkit prompts me for a keyname. I’m actually uploading a file S3 uses a mechanic of a keyname. The keyname can be the same as the filename although doesn’t have to be.

So I’ll just accept the file name as a keyname and click OK to upload the file.

If I want to view the file in the bucket within Eclipse I just need to right click the bucket name and select Open in S3 Bucket Editor.

When that window opens we can see the item in the bucket.

You can see the keyname and also the owner. Interestingly although eclipses connecting to Amazon web services using an IAM user called Frank, this field is actually showing the root account name which happens to be Phil Stirpe.

Window also shows that we using S3 standard storage rather than reduced redundancy storage. The storage class is not something that we can modify in this window.

Another thing I can do in this window is select the key and edit the bucket ACL or access control list.

This is one way of managing permission. I.e. you could use access control lists rather than IAM policies. In fact you could use a combination.

I don’t want to use access control lists so I’ll just cancel that dialog.

As I have assigned any privileges, no one should be able to access this file. Unless is the root account or an IAM user with full privileges to access S3.

Let me just show you this file in the AWS console.

The reason I have come here is so that I can right click the file and select properties. One of the properties is a URL that could publish and share with users in order to locate it. This URL isn’t available within Eclipse.

If I copy that URL and then open and incognito window. By the way I’m doing this because I already have another window open and authenticated with Amazon web services in it.

If I try to navigate using that URL you will see that I get an access denied.

Clearly there is a file up there and we got it there via Eclipse. By default S3 prevents any access.

Here’s something we are able to do in Eclipse. We can right click the file or key and select Generate Pre-signed URL. At the same time you can specify an expiry date and time for the URL. So I’ll try publishing a URL that will expire in an hour’s time.

So I’ll copy the new URL into the clipboard and switch back to the browser and try that in the address bar instead. As you can see the URL includes an expiry time and an access key.

When I press enter, I now retrieve the file from S3.

Now there are lots of things that might want to do with S3 but the I’m just focusing on those simple tasks carry out within Eclipse using the AWS toolkit. What we’ve been able to do with the AWS toolkit is create a bucket, drag a file into the bucket. And if I can drag a file in, I could easily delete it.

I’ve also shown how create a Pre-signed URL to give users temporary access to a file in S3.

As I said start this video, I’m just focusing on those management tasks that you can perform in Eclipse rather than what we might be able to achieve using the SDK programmatically. That would be material for another video.

There you have it.

In this video, I have shown you how easy it is to work with S3 using the AWS Toolkit in Eclipse.

Thanks for watching and please feel free to comment on my blog (www.philipstirpe.com) and Facebook page (www.facebook.com/philip.stirpe.tutorials). Perhaps you could suggest more video topics? Most of all, don't forget to subscribe to keep up with my videos as I release them.

Bye for now.





Flash Player








See you soon

Phil Stirpé
"I don't do average!"






How to install the AWS Toolkit for Eclipse

This is another in a series of videos that I am producing for my YouTube channel HowDoYouDoStuff.


In this video, I am going to show you how to install the AWS Toolkit for Eclipse


You can read the transcript below.


HTML 5 Player



Transcript


Hi guys. I'm Phil Stirpe.

In this video, I am going to show you how to install the AWS Toolkit for Eclipse.

The AWS Toolkit is an extension for Eclipse that makes it easier for developers to develop, debug, and deploy Java applications using Amazon Web Services.

You begin by visiting this page at http://aws.amazon.com/eclipse/

In fact there is nothing that you need to download from this page. You simply need to follow these short instructions.

The 1st stage is to get yourself into Eclipse.

Okay, I’m already in a workspace so I need to go to the Help Menu and select Install New Software.

This 1st box is where I need to put the URL. Rather than type it I’ll just copy it from the address bar.

Now I click the Add button and for a repository name I’m going to enter AWS.

I’ll just wait for it to build up the list.

Now rather than select the whole Toolkit, I’m going to select all except the SDK for Android as I had a problem installing this earlier.

I’ll accept the rest of these defaults and then click Next.

I review all of these items and then accept the license agreement before clicking Finish.

When I receive the security warning, I’ll just click OK to continue.

Once the AWS Toolkit has installed, I just need to restart Eclipse.

Following the restart, I am now prompted for an access key and a secret key.

These are credentials associated with an IAM user.

It is strongly recommended that you don’t use the credentials for your Root account. Instead you should create one or more IAM users.

Now I do have an IAM user created. In fact I created it in an earlier video and downloaded it credentials at that time.

Here is the file for the user called Frank, and here are his access key and secret key.

So I’ll just copy those values and switch back into Eclipse and paste them into this dialog.

We are now giving the AWS Toolkit the credentials for that IAM user named Frank. So whenever I work in Eclipse, I will be connected to Amazon web services as Frank and will be able to carry out any task that Frank has privileges for.

At the bottom of the screen we can see the open AWS Explorer window.

Rather than listing all of the available AWS services, the AWS Explorer is only showing the usual suspects. I.e. those services that the developer is most likely to interact with whilst working in Eclipse.

Perhaps I would want to access to S3 buckets, perhaps I would want to interact with EC2 and view instances?

Let me try to access S3. I’m told the AWS Explorer is unable to connect. However this is actually an access denied result.

The user named Frank does actually have permission to access S3. However this permission only relates to a particular bucket. Let me switch back to the AWS console to show you.

If I connect to the IAM console and find the user named Frank, you can see that he’s in a group called Developers.

If I check out the permissions for the Developers group, you can see that members have access to a bucket named qa-cookbooks.

Unfortunately the AWS Toolkit and therefore Eclipse cannot work at such a low level. If you want to access a service using the Toolkit menu going to have to have access to the service and not part of the service.

Now do have another group called S3Developers and if we examine it policy we can see that it has full access to the S3 service regardless of bucket. That will be more than enough for the AWS Toolkit.

So I’ll just add Frank to the S3Developers group.

Those changes should take effect straightaway and so I shouldn’t need to restart Eclipse.

Back in Eclipse, I’ll just refresh the AWS Explorer window.

As you can see, when the Toolkit attempted to reconnect to Amazon Web Services as Frank, it was granted these additional privileges and so the AWS Explorer was able to retrieve the bucket names.

However it would be able to access any other services for example EC2 to view instances and AMIs.




There you have it.

In this video, I have shown you how easy it is to install the AWS Toolkit for Eclipse.

Thanks for watching and please feel free to comment on my blog (www.philipstirpe.com) and Facebook page (www.facebook.com/philip.stirpe.tutorials). Perhaps you could suggest more video topics? Most of all, don't forget to subscribe to keep up with my videos as I release them.

Bye for now.





Flash Player








See you soon

Phil Stirpé
"I don't do average!"






How to download and install the AWS Toolkit for Visual Studio

This is another in a series of videos that I am producing for my YouTube channel HowDoYouDoStuff.


In this video, I am going to show you how to download and install the AWS Toolkit for Visual Studio


You can read the transcript below.


HTML 5 Player



Transcript

Hi guys. I'm Phil Stirpe.

In this video, I am going to show you how to download and install the AWS Toolkit for Visual Studio.

The AWS Toolkit is an extension for Visual Studio that makes it easier for developers to develop, debug, and deploy .NET applications using Amazon Web Services.

So the 1st step is to visit this page at http://aws.amazon.com/visualstudio/ and there you’ll find a button that allows you to download the AWS Toolkit.

Okay so that’s downloaded and it took just under a minute.

So here is the installer. An MSI file. Let me go ahead and install and work my way through the wizard.

I’ll accept the license terms.

As you can see the installer is going to install SDKs for a variety of frameworks including .NET 4.5 and Windows RT. It’s also going to install some samples.

I’ll accept the defaults and click Next.

Now I click the Install button.

And after a minute or so the wizard is ready.

Okay let me launch Visual Studio.

As you can see we’ve been offered a short video on using the AWS Toolkit for Visual Studio.

Let me click on the View Menu and select AWS Explorer.

In order for Visual Studio to work with my account, I need to configure it with some account information. As you can see I have the option to add in a user.

Let me click on Add an Account.

In this dialog I’m able to specify the credentials for user. In an earlier video I created an IAM user called Frank who is a member of the Developers group. Let me put Frank’s name in the Display Name box.

What I now need to do is supply credentials. When you create an IAM user account, you are given a once only opportunity to store the credentials.

If I switch to my downloads folder, I’ll be able to open up this credentials file.

He we can see the user’s access key and secret key which I can copy into Visual Studio.

When you create an account with Amazon web services this is known as the route account and has a couple of credentials including an email address for the ID and password. Each route account is also assigned an account number. It is that account number that can be entered here to be associated with this IAM user.

Note that the account number is actually optional in this case.

To locate your account number you have to visit your account in the AWS console and then click on the My Account link.

There is quite a lot of information on this page but the information that we need is this account number here.

There are a number of locations that you can get this number from. For example, if you go into the IAM console, you can find it in the IAM user sign-in URL.

Now that I have the account number I can jump back into Visual Studio and paste it in.

So this is creating an identity in visual studio is associated with an IAM user.

Let me just switchback to the AWS console to show you that user. I created this user in an earlier video.

In fact when recording that video I did forget to add the user called Frank to the Developers group so I’ll do that now.

Back in Visual Studio, these credentials are Frank’s access key and secret key. It makes sense for the Display Name to be the same.

And the account number is the root account to which the IAM user belongs.

As you can see now in visual studio I have access to a variety of services associated with that account.

For example S3. If Franks attempts to access to S3, he gets Access Denied.

Now Frank is a member of a group called Developers that has access to S3. However the developers group doesn’t have access to all of S3.

Let me switch back to the AWS console. If we examine the permissions for the developers group, we will see that it only has permissions for bucket named qa-cookbooks. This is far too granular for Visual Studio to cope with.

So let me create another group. I’m going to call this group S3Developers. My intention here is that this group gets full access to S3.

So if I scroll down this policy template list, I’ll choose S3 Full Access. This is more than I would like but it will allow me to work in Visual Studio.

I’ll click on Continue and then Create Group.

I can then switch to the Users section and then add Frank to this new group.

Now these privileges should be available to Frank immediately.

So if I switch back to Visual Studio and then refresh the AWS Explorer, you will see that all of the buckets are now listed.

Although it’s ideal to have specific policies for particular users or groups, the AWS Toolkit isn’t that granular.

So if you want to be able to access S3 from within the AWS Explorer, you’re going to have to use a user account that has privileges for the whole S3 service rather than individual buckets.

If you weren’t using Explorer and were simply writing code, you could come up with a better, more restrictive set of privileges.

Before I go let’s just take a look at some of these other services.

This isn’t an exhaustive list of all the services available in Amazon Web Services. Rather these are considered the usual suspects. In other words, services that you are more likely to want to work with from within Visual Studio.

You would want to be able to see the buckets, AMIs and EC2 instances.


There you have it.

In this video, I have shown you how easy it is to download and install the AWS Toolkit for Visual Studio.

I’ll also be producing a video shown you how to download and install the AWS Toolkit for Eclipse.

Thanks for watching and please feel free to comment on my blog (www.philipstirpe.com) and Facebook page (www.facebook.com/philip.stirpe.tutorials). Perhaps you could suggest more video topics? Most of all, don't forget to subscribe to keep up with my videos as I release them.

Bye for now.





Flash Player








See you soon

Phil Stirpé
"I don't do average!"