Python Boto3 AWS Route53/Llamda/CloudFront Automated Deployment
Budget: $750 – $1,500 USD
The Project is an automation project to automate the process of checking availability/purchasing a domain through AWS Route53, setting up SSL , DNS, and placing the domain behind CloudFront's CDN Service, pointing that to a AWS Lambda function. Developer will have to write the Lamda Function as well.
- Incoming Request will parsed by AWS Lambda function which checks if the incoming request has a url path, if the visitor is visiting the root url , they should be redirected to a globally set url.
- Deployed Domain - https://deployedDomain.com - > Redirects to Blacklist.com
Visitors who visit - https://deployedDomain.com/uniqueid - > The unique id will be parsed out and an API request will be made to an API endpoint( this will be provided) with the unique id parsed out from the path, visitor's ip address, and vistor's user_agent.
The endpoint will provide one of two responses.
- The first response is a url that looks something like "https://redirecturl.com/?s1={uniqueid}", at that point, script should replace the {uniqueid} macro with the unique id extracted after the domain and redirect the user <--- - The second response is blacklisted=true, url = none. The script should redirect the user to the same url as the visitors who visited the root domain.
- AWS resources and serviced created should be tracked and persisted, as the script should allow us to delete domains, at which point all the AWS services and resources associated with that domain should automatically be deleted. Persistant for auto-deployed domains, CloudFront resources, and Llamda functions can be done through Sqlite, Mongodb, or Mysql.
End result can be a CLI script or a simple library.
- Incoming Request will parsed by AWS Lambda function which checks if the incoming request has a url path, if the visitor is visiting the root url , they should be redirected to a globally set url.
- Deployed Domain - https://deployedDomain.com - > Redirects to Blacklist.com
Visitors who visit - https://deployedDomain.com/uniqueid - > The unique id will be parsed out and an API request will be made to an API endpoint( this will be provided) with the unique id parsed out from the path, visitor's ip address, and vistor's user_agent.
The endpoint will provide one of two responses.
- The first response is a url that looks something like "https://redirecturl.com/?s1={uniqueid}", at that point, script should replace the {uniqueid} macro with the unique id extracted after the domain and redirect the user <--- - The second response is blacklisted=true, url = none. The script should redirect the user to the same url as the visitors who visited the root domain.
- AWS resources and serviced created should be tracked and persisted, as the script should allow us to delete domains, at which point all the AWS services and resources associated with that domain should automatically be deleted. Persistant for auto-deployed domains, CloudFront resources, and Llamda functions can be done through Sqlite, Mongodb, or Mysql.
End result can be a CLI script or a simple library.