Elastic Beanstalk is a handy dandy service to quickly deploy your applications up to the AWS cloud. One thing I’ve noticed tho is when you delete your application from AWS, it leaves behind a bucket that I cannot seem to delete.
Here’s how I was able to get around that. I’ve seen others post this question out on the internet so I thought I’d share it here. Thanks for watching. Hope this helps someone 🙂
Elastic Beanstalk is one way to do this fairly easy. Another way is using Cloudformation templates (there are several Cloudformation tutorials out there).
I share my experience in two youtube videos demonstrating how I was able to create a test .NET Core 2.0 web app and deploy it to AWS. The cloudformation template provisions a windows server 2016 EC2 instance and installs the CodePipeline/CodeDeploy agent to it. Part1 ended abruptly for reasons I explain in the beginning of Part2.
I hope this helps someone out there as there really is not much out there in the way of documentation that brings this particular task together for a .NET Core 2.0 web app deployed to an Windows 2016 AWS instance in the cloud utilizing CodePipeline/CodeDeploy. I attempted to do that here.
I played around with ElasticSearch. There’s all kind of tutorials out there that you can take on youtube and other online video subscription libraries. The purpose of this post was to document how I got ElasticSearch up and running on my Windows 10 machine as well as to show some queries.
If you need to do the same thing, please view the following video I made showing how to do it along with a demo on how it works.
Source code (and helpful links) are available on my github page at
I had to look into ElasticCache. We have a .NET Core 1.1 and 2.0 apps. In the process of exploring options to migrate them into the cloud, it was determined that we can take advantage of distributed caching. AWS has ElasticCache which is a distributed caching service that allows you to create cache clusters for optimal performance. The caching engines supported are the very popular Redis (“Re”mote “Di”ctionary “S”tore) and Memcached.
There are differences between the two (Redis supports complex objects as values and Memcached just strings as values). Redis allows up to 512mb per key. Memcached 1mb. A particular course I took on it said to go with Redis 99% of the time as it’s become the defacto.
A disclaimerI wanted to make. I tossed the demos together super quick in the interest of time.
If you’re interested in learning Redis and need to support Redis in your .net core 1.1 or 2.0 app, I made the following video which includes links to the github repo as well as a demo.
To see how to deploy the application to AWS, you can refer to this video.