Does anyone else finds AWS and other Amazon services overly complicated?
11–20 of 148 posts
Re: Does anyone else finds AWS and other Amazon services overly complicated?
#12Most people don't build their signatures by themselves - they use the SDK provided.
Re: Does anyone else finds AWS and other Amazon services overly complicated?
#13Ah that's nothing. Simple problem from a high level: static web site on apex domain. What you should be able to do: Click click done. Upload files to S3. Point CNAME at AWS. What you have to do: Create an S3 bucket and stick the files in it. Create a zone in Route 53 and import your old zone file. Change your nameservers at the registrar. Wait a bit. Go to ACM in the correct region and create a cert. Tell it to add t…
>Go to ACM in the correct region and create a cert Glad you included the "correct region" qualifier. The number of times I've mistakenly created the certificate in my local region, rather than the one designated for CloudFront...
Really these days I want to solve the problem and go home, not remember where the poo I stepped in last time I had to solve it was.
Re: Does anyone else finds AWS and other Amazon services overly complicated?
#14I though its just me who find it overly complicated. With people who use AWS SDK its all abstracted out. But there is time I just want to send a damn `curl` to download a S3 file and yes, doing the dance in bash isn't easy. There is time I wrote a Lua plugin for openresty to fetch s3 and. I have to trial and error with lot of debugging. The ordering. the timestamp format...all of that...
Re: Does anyone else finds AWS and other Amazon services overly complicated?
#15Re: Does anyone else finds AWS and other Amazon services overly complicated?
#16Ah that's nothing. Simple problem from a high level: static web site on apex domain. What you should be able to do: Click click done. Upload files to S3. Point CNAME at AWS. What you have to do: Create an S3 bucket and stick the files in it. Create a zone in Route 53 and import your old zone file. Change your nameservers at the registrar. Wait a bit. Go to ACM in the correct region and create a cert. Tell it to add t…
Ok I missed: point DNS to Hostgator name servers. Click the button to install lets encrypt.
Re: Does anyone else finds AWS and other Amazon services overly complicated?
#17Earlier quoted context omitted.
>Go to ACM in the correct region and create a cert Glad you included the "correct region" qualifier. The number of times I've mistakenly created the certificate in my local region, rather than the one designated for CloudFront...
Yep. Really these days I want to solve the problem and go home, not remember where the poo I stepped in last time I had to solve it was.
Re: Does anyone else finds AWS and other Amazon services overly complicated?
#18AWS documentation isn't consistently good, and there are lots of decoys. So, if you wound up in some local minima that made it look like you had to implement the signing and such yourself, try a Web search that includes the name of your chosen programming language.
(A long time ago, I had to implement the AWS client API from scratch, but that's because I was using a fringe language that didn't have such libraries.)
Re: Does anyone else finds AWS and other Amazon services overly complicated?
#19Re: Does anyone else finds AWS and other Amazon services overly complicated?
#20I though its just me who find it overly complicated. With people who use AWS SDK its all abstracted out. But there is time I just want to send a damn `curl` to download a S3 file and yes, doing the dance in bash isn't easy. There is time I wrote a Lua plugin for openresty to fetch s3 and. I have to trial and error with lot of debugging. The ordering. the timestamp format...all of that...
It's even worse. We use presigned URLs (from the SDK) and S3 for file uploads. That's one fresh hell you don't want to get involved with. One of those seemed like a good idea at the time things...