I work with Amazon S3, and indeed many of the Amazon’s cloud services, and one of the things that is often frustrating in my day-to-day workflow is the need to keep jumping out of the IDE, find the files I’m looking for in a S3 explorer, grab the key to the file and then go back to the IDE and write code against the AWS SDK to read the data from S3 and do something with that data.
This inefficiency in my development process is magnified when working against buckets with large number of keys and/or buckets which has versioning turned on.
With these in mind, I wanted to create a type provider which is:
- able to interactively navigate buckets, folders and files in S3
- able to retrieve data easily in either binary of simple text format
- able to search for files easily
plus all the usual goodness that comes with F# type providers, such as:
- not having to leave the IDE and let the provider do all the hard work for me
- have static type safety with regards to the file structure in S3 (if someone deletes/renames a file or folder I will be informed via a compile time error rather than a runtime exception!)
After a few nights of work I finally have something that’s of usable shape, here is a quick demo video I’ve prepared of the type provider in action:
Go on, give it a play and let me know if you have any feedbacks!
I specialise in rapidly transitioning teams to serverless and building production-ready services on AWS.
Are you struggling with serverless or need guidance on best practices? Do you want someone to review your architecture and help you avoid costly mistakes down the line? Whatever the case, I’m here to help.
Check out my new course, Complete Guide to AWS Step Functions. In this course, we’ll cover everything you need to know to use AWS Step Functions service effectively. Including basic concepts, HTTP and event triggers, activities, callbacks, nested workflows, design patterns and best practices.
Here is a complete list of all my posts on serverless and AWS Lambda. In the meantime, here are a few of my most popular blog posts.
- Lambda optimization tip – enable HTTP keep-alive
- You are thinking about serverless costs all wrong
- Many faced threats to Serverless security
- We can do better than percentile latencies
- I’m afraid you’re thinking about AWS Lambda cold starts all wrong
- Yubl’s road to Serverless
- AWS Lambda – should you have few monolithic functions or many single-purposed functions?
- AWS Lambda – compare coldstart time with different languages, memory and code sizes
- Guys, we’re doing pagination wrong