Tag Info

New answers tagged

2

Nah you can't, there's nothing to refer to anyway (e.g. logical ID). Just create your own main table ;-). This is probably one of the reason it can't be used: One way to protect your VPC is to leave the main route table in its original default state (with only the local route), and explicitly associate each new subnet you create with one of the custom ...


1

Of course you can edit it. What makes you think you can't? In any case, it's trivial to create a new routing table if need be.


0

Because you're using S3 and Cloudfront, this is possible. You can setup multiple behaviours, each with a path pattern that then fetches content from different origins, as well as use S3 redirects. So to do this: Setup a redirect, using instructions at http://docs.aws.amazon.com/AmazonS3/latest/dev/how-to-page-redirect.html so the S3 bucket redirects from ...


2

Let me ask - why do you care? I understand the logical reasoning, but it would not be something I would expect AWS to do - I would do those blocks in my application level. There are a lot of thigns that may go wrong and I would want full control over those blocks. So, for me it would be irrelevatn whether AWS does it - I would run my own decision logic.


1

The A-record alias you create has to be the same as the name of the bucket, because virtual hosting of buckets in S3 requires that the Host: header sent by the browser match the bucket name. There's not really another practical way in which virtual hosting of buckets could be accomplished... the bucket has to be identified by some mechanism, and that ...


2

Recommendation Start learning to use, and using the AWS Command-line, combined with your own homegrown solution to manage your DNS entries. I personally have a solution which rounds up multiple text files (each with customer identification and comments contained) into one file, which then ships off to my authoritative DNS whenever there is an update. More ...


0

I don't know of any off-the-shelf solution to do this. That said, homebrewing a Route53 management system should be fairly simple - a couple mysql tables and a sync script in a language of your choice is really all it would take.



Top 50 recent answers are included