il-central-1: Israel (Tel Aviv)
il-central-1 is the code for the Israel (Tel Aviv) region. It is an opt-in region that must be enabled per account, and it serves Israeli users and organisations that need data and processing to stay in Israel.
Who uses the Tel Aviv region
Israel has a large technology sector, and many of its companies historically ran in Frankfurt, Ireland or us-east-1. The local region changes the picture for three groups:
- Public sector and regulated industries, such as government bodies, defence suppliers, banks and health providers, which may need data hosted in Israel.
- Israeli consumer services where shorter round trips help payments, streaming, gaming or real-time communication.
- Global SaaS vendors with Israeli customers who want to offer an in-country hosting option.
Companies that sell globally from Israel often keep their main platform in a large region near their customers and use il-central-1 only for Israeli tenants.
Enabling il-central-1
aws account get-region-opt-status --region-name il-central-1
aws account enable-region --region-name il-central-1
# after a while, confirm the region is visible
aws ec2 describe-regions --region-names il-central-1 \
--query 'Regions[].OptInStatus' --output textUntil it is enabled, the console doesn't let you select the region and API calls fail with credential-style errors. If your organisation restricts regions with SCPs, add il-central-1 to the allowed list as part of the same change.
Targeting il-central-1
Use --region il-central-1, AWS_REGION=il-central-1 or region = il-central-1 in a profile. Endpoints follow <service>.il-central-1.amazonaws.com, for example lambda.il-central-1.amazonaws.com. Note the prefix: Israel uses il-, not me-, so scripts that loop over "Middle East" regions by prefix will miss it.
Credentials obtained from the global STS endpoint aren't valid in opt-in regions by default. If a tool works in eu-central-1 but fails here with an invalid token, point it at regional STS or change the token setting in IAM account settings.
Service coverage and resilience
As a newer region, Tel Aviv offers a subset of what Frankfurt or us-east-1 do. Check the AWS Regional Services List for each managed service in your design, and confirm instance families with describe-instance-type-offerings. If data must stay in Israel, plan resilience around multiple Availability Zones inside il-central-1 and keep backups in a separate account, since there is only one AWS region in the country.
Nearest alternative regions
For recovery or for workloads without residency rules, the usual choices are eu-central-1 (Frankfurt), eu-south-1 (Milan) and the Gulf regions me-central-1 and me-south-1. Routing from Israel doesn't always follow geography, so measure round-trip times from your users before deciding which is nearest in practice.
Operating across time zones
Scheduled maintenance settings in AWS, such as RDS maintenance and backup windows or Auto Scaling scheduled actions, are written in UTC unless you specify a time zone where the service supports it. Teams in Israel moving from a European region should recheck these windows after migrating, because a window chosen to be quiet in Frankfurt may fall in the middle of the Israeli working day.
Questions
Where is il-central-1?
In Israel; AWS names it Israel (Tel Aviv).
Is il-central-1 opt-in?
Yes. Enable it per account before creating resources there.
Why isn't il-central-1 in my region list?
It's an opt-in region; it appears in the console selector once enabled. Check its status with aws account get-region-opt-status --region-name il-central-1.
Teams in Israel often run across several regions and time zones. CloudConsole, a phone app for AWS, is built to show alarms, logs and resources across regions on your phone.
About the app → · Download on the App Store