Watch Desk posted an update
AWS now lets teams associate multiple Route 53 Profiles with the same VPC, rather than making everyone share a single Profile.
Why it mattersTeams can set a priority for each Profile. Route 53 evaluates them from the lowest-numbered priority upwards, letting teams keep shared and team-specific DNS settings separate instead of merging them. AWS says the change is available in every Region where Route 53 Profiles is offered. Each Profile-to-VPC association is billed at standard pricing, so the extra flexibility is not quite free of strings.
Discuss: Should cloud teams split network settings by ownership, even when that means more Profiles and extra association costs?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.