Introduction

In the following article, I described how to set up Cantaloupe on EC2.

This time, I will configure a custom domain and enable HTTPS.

Custom Domain Configuration

This time, I will assign the domain cantaloupe.aws.ldas.jp to 54.172.71.20. When using Route 53, it can be configured as follows.

Obtaining an SSL Certificate

sacupedtrotbsiountstcaelrltocnelrytbo-tstandalone-dcantaloupe.aws.ldas.jp
rSEPha(WspdE(ARSCKTTCIoan(ltgYohaeFYceueehhefovtEetr)uarvF)cqcryiertienapeelrteeouctsstyDD@nrtssesdenlnsueeiieboooigee:/eoe/nssfscounnper/i(yyrpw(ttsieftaa-dmr/nNoossNifcsriltt1ea'el)uuo,)rnuaatlhiii7bicaeoorfCoegltvieaknn2ul'dtr:bec:gleefssegg-gsdeetraiaydi3atteeYmhtmYsicwsCtt1ldohnrwaebptcrsaaieeoo-odeciioaeeettltr6grcrtllLtirrcs:eltIE2eaTyole?geteaubSF-tsnepiatndiivebpoRF6oscrtrnd'Ws.fvexetG:1em.egdse,iedpa,:(lsog,r'cdiu/vu)rieEdaaarpsphas:ogsosnntctedclLoref/tnscldee:saheem/dxdecrirteatelxSorewykwft//oeds'/ofxecipeaoieenduesug@ruwyttyrfttlbrgvmiohtsicc2wecEulmietupocc//0hdonneuacnhrtrtaall2encttriethosontee3ntsrusglstfejetett-aiy#ee.a/hiensa.ss1tsdpnnctLerEcdulee2hketcctoEsltponn-er:erm-Ateypucc1tryrSCcaooprr9costpeAMctnureyy.eubtn-Eerdt.ppraphho/evroeatttuptttlw1stntmdw//itottea.eiihaisllforppctl3rfceig.iiimtsses-vililvvcai::reaSecFntdeeatn/tnneraroaaa//tig/ocdp.tonblscceclenrten-o.aaaoeflyseDtpufjnnrlutfypemoiirtrpttelrs.tcbseoeaanyeo.ueyrfoellewnr-lrrosiudoowrocgsoi-uuFtrouuserr/tgt2compp.nkyday1acuow.eeepon-genro..wbtndn2rsdgraay.aao0esaakwwt:otlt2eftnsshreoi2?uiie..ig-nc.loznlls/leeplnacdddesdy,traaco-)fiyssend.iaop..rasntjjttcYsfippieaouotn//fnueuhgfpitdnaurcam,dttlialuihlvtostneckeutoghepwayieei.n.bnpa,.etwpmhsee.mlbdaacsk.gjrpound.

Web Server Configuration: Installing Nginx

avpit/ientsct/anlglinnxg/isnixtes-available/cantaloupe.aws.ldas.jp

Configuration:

s}s}eerrvvelsrelsssl}rieeriessosrtsrllc{tvu{tv__aeereecctpppppnrnnreeirrrrr__rroooooo8n34nttnxxxxx0a04aiiyyyyy;m13mff/_____eeiipsssshscc{aeeeectscaasttttatlatts____np;neehhhhtst_heeeea:a/ktaaaalleetdddd/otypeeeeu$uc:rrrrphp///eoele/HXXX.s.etlo---atatcosRFFw$ws/cteoosrselaarr.e.nel$lwwlqlcthh-aadudrsooIrraeayessPddssspnttee.t.tc:;$ddj_j/r8r--puply1eFP;r;ip8morivt2oro;e;ttle$oci#_pavar$nedost/dxcacryhlac;_eonaamutndepatd;ela_.olxauo_wpufsepo..erlawdwaasrs.d.lejddpa_/sff.oujrlp;l/cphraiivnk.epye.mp;em;

Create a symbolic link and restart.

rrnnrooggoooiiottnnt@@xx@ii::ippp--tc-11ho177en722f2--ci-33og311nu1--fr-66ia622gt2--ui-66ro611an1::t://if/hhoihoonlommemeefe//i//uuleubbetbuucunn//nttentuutgu##ci#/nlnnxsngg/yiins-nngtsxxie/nm/-nxcetg.tticlcno/xnrn.fegcsiottnneaxfsr/ttssiyintnsgetisasn-xuxacvicaseislosakfbulle/cantaloupe.aws.ldas.jp/etc/nginx/sites-enabled/cantaloupe.aws.ldas.jp

As a result, Cantaloupe became accessible at the following URL.

https://cantaloupe.aws.ldas.jp/

Summary

I hope this is helpful for setting up Cantaloupe.

Note that while I used Let’s Encrypt this time, it is also possible to use AWS certificates.