1 Answer
- Newest
- Most votes
- Most comments
0
Hi,
Without explicitly declaring the content type of a resource, the client may
attempt to automatically detect the type, but the result may not be accurate.
This is why it's important to explicitly declare it.
On 2., you can manage the domain name by another DNS provider to have the one that you exactly want as long as you do proper remapping via CNAMES
See https://support.dnsimple.com/articles/differences-between-a-cname-alias-url/ and https://ie.godaddy.com/help/edit-a-cname-record-19237 (for Godaddy but similar for other DNS providers)
Relevant content
- asked 3 months ago
- Accepted Answerasked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 9 months ago
Regarding using managing a domain name elsewhere - the codebase to spit out the REST API also resides elsewhere, and not on AWS EC2 or Lambda. Is it possible to have the code be as is (say on DigitalOcean etc) and use only AWS Management API to handle the API management? Migrating code from elswhere to AWS is another task for a future date.